Archives

1, 2

This page has archives. Sections older than 28 days may be automatically archived by Lowercase sigmabot III when more than 8 sections are present.

I noticed that the NPP backlog chart isn't being updated, and I believe that the issue may be with your database. I downloaded the .tsv file from the link provided at User_talk:Nettrom/Archive_2#NPP_Queue_Count and its last entry is from 9 February. Thanks for all your work on this very useful tool. (t · c) buidhe 07:08, 12 March 2022 (UTC)[reply]

Hi @Buidhe, thanks for letting me know about this! I looked into this and can confirm that we don't have data past 9 February, just as you mention. I'll make some updates to things to make this work again. Cheers, Nettrom (talk) 16:03, 12 March 2022 (UTC)[reply]

I've put in a temporary fix to get the updates going again, and the database is now updated every six hours as it used to be. I'll do some more maintenance in the near future as well to make sure this is good to go for another few years. Thanks again for reporting this, @Buidhe! Cheers, Nettrom (talk) 16:40, 13 March 2022 (UTC)[reply]

Thanks for fixing it! (t · c) buidhe 16:41, 13 March 2022 (UTC)[reply]

Greetings. I was replying to User:SilverMatsu, who has received tons of suggestbot entries (4 archives worth). Is there a way to suppress excess messaging? That is a lot of work to lay on an editor. --Ancheta Wis   (talk | contribs) 01:00, 23 May 2022 (UTC)[reply]

I'm watching this space; it's fine to reply here. --Ancheta Wis   (talk | contribs) 09:43, 23 May 2022 (UTC)[reply]

Hi @Ancheta Wis, thanks for reaching out and asking about this! There are different ways to use SuggestBot with different options and possibilities. SilverMatsu is using the template to request a single set of suggestions, a feature that hasn't been designed to be used extensively. There's also the option to subscribe and get them periodically, where one can tell the bot to replace any existing set of suggestions so there's only a single set on the page at a given time. For both subscribers and users who request a single set, we allow the template to be put on any subpage in user space in case they don't want the suggestions on their talk page. Apart from that, we leave it to the user to maintain their pages in the way they see fit, e.g. to use an archiving bot like SilverMatsu also does, but we do have some safeguards in place for subscribers: the bot doesn't post if the page is large, and it'll stop trying to post if the user has stopped editing for a while. For single requests, we treat them as the user really wanting suggestions, meaning that those safeguards are not in place. I hope this helps, happy to hear feedback or additional questions about any of this! Cheers, Nettrom (talk) 13:45, 24 May 2022 (UTC)[reply]

The NPP backlog chart currently shows the backlog. I think it would be quite useful to also know the number of articles added and removed. Right now, the chart doesn't tell you anything about why the backlog is increasing or decreasing. I'm guessing that the number of new articles is fairly constant and the number of reviews performed is mostly what causes the backlog to grow and recede. Since you are involved in providing the data for the existing chart, I thought I would start by asking you about the feasibility of this enhancement. Thanks. MB 21:55, 28 May 2022 (UTC)[reply]

Hi, still looking for some indication how to get this implemented. MB 21:45, 24 December 2022 (UTC)[reply]

Hi @MB, thanks for the ping on this and your patience while I completely overlooked this! I want to make sure I understand the ask correctly. What you’d like is to have three data point for each update: the number of articles in the queue (this is what we currently have), as well as the number of articles added and removed since the last update (and by “articles” we mean non-redirect pages in the Main namespace, just like we currently have)?

I think the easiest way to do this would be to make a copy of the backlog on every update so we can compare with the previous update. Then we can add the two data points, number of articles added and removed, and rotate the backlog copy so we only keep the latest one. There might be other ways to do this (e.g. by reading the log tables), but I think those might be more complicated.

One challenge with charting this, and something @MusikAnimal might need to consider, is that if for some reason the update doesn’t run and we skip one or more, then the number of articles added/removed will be “artificially increased” when the next update runs because the time difference is larger. We might therefore want to chart “average number of articles added/removed per hour” (or some other timeframe that works for the chart) instead of the raw counts, because that’ll be time-agnostic.

I should have some time to work on this before the new year comes around, but it’ll have to be later this week. Let me know if I’ve understood your ask correctly or not, and any other questions you might have! Cheers, Nettrom (talk) 09:43, 27 December 2022 (UTC)[reply]

Yes, this chart represents only articles, so just non-redirect pages in mainspace. (I believe @MPGuy2824 has asked for a similar chart to be produced just for redirects also somewhere, so it would be nice to have this feature extended to the redirect chart if/when that is available).

I'm not sure I follow your proposal. This chart shows the backlog. If you save the previous update and make a comparison, you have the net change in the backlog from one update to the next. But that doesn't tell you the two additional data points (articles added and removed). If you mean you will do the comparison get the net change so you can then calculate the number of articles added by utilizing the number of articles removed/reviewed (as shown here), then that sounds like it would work.

Regardless of the implementation, I think you do understand the request. MB 14:38, 27 December 2022 (UTC)[reply]

Yes, please collect the same datapoints for redirects as well. If you want to backfill some data, then i have backlog and reviewed data, for both redirects and articles in the s55221__nppstats_p database on toolforge (npp_stats table), starting from 20th November. -MPGuy2824 (talk) 05:01, 28 December 2022 (UTC)[reply]

شما کاربر خوب ویکی پدیا هستید از طرف meidano در وپ فارسی — Preceding unsigned comment added by Meidano (talk • contribs) 04:43, 14 June 2022 (UTC)[reply]

Thank you for editing that page. I realized that I literally could not read that correctly. Now I am a bit ashamed. 0xDeadbeef 15:55, 6 August 2022 (UTC)[reply]

@0xDeadbeef: Oh, no worries! That sentence was confusing me too, I’m glad our editing resulted in something that’s easier to read. Cheers, Nettrom (talk) 17:20, 7 August 2022 (UTC)[reply]

Hi!

The Translate and cleanup category on the community portal isn't being populated by your bot. I also noticed the Rough translation template failed to add rough translations to the main tracking category, which I've fixed. The bot's source code seems to be relying on the wrong category (that one can't contain any articles); may I suggest it be changed to this one? DFlhb (talk) 07:22, 8 November 2022 (UTC)[reply]

Hi @DFlhb, thanks for reporting this, and for your patience while I worked on finding time to fix it! Your suggestion is spot on, and I’ve updated the bot’s code (which is now here) as well as the linked category from the open tasks page (in this diff). Cheers, Nettrom (talk) 18:03, 4 December 2022 (UTC)[reply]

Nice work; many thanks. DFlhb (talk) 19:02, 4 December 2022 (UTC)[reply]

Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add ((NoACEMM)) to your user talk page. MediaWiki message delivery (talk) 00:45, 29 November 2022 (UTC)[reply]

Hello, Nettrom. I am a user of Uzbek Wikipedia. I would like to ask your permission to use SuggestBot on UzWiki as well. If possible, could you also help with usage? Laziz Baxtiyorov (talk) 14:04, 1 March 2023 (UTC)[reply]

01967666580 2400:C600:4614:6F44:1:0:DE8A:45C9 (talk) 13:04, 16 July 2023 (UTC)[reply]

Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add ((NoACEMM)) to your user talk page. MediaWiki message delivery (talk) 00:34, 28 November 2023 (UTC)[reply]

To 51.39.228.215 (talk) 00:03, 4 February 2024 (UTC)[reply]

You can find this message translated into additional languages on Meta-wiki. Please help translate to other languages.

Dear Wikimedian,

You are receiving this message because you previously participated in the UCoC process.

This is a reminder that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) ends on May 9, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.

The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.

Please share this message with members of your community so they can participate as well.

On behalf of the UCoC project team,

RamzyM (WMF) 23:09, 2 May 2024 (UTC)[reply]