Wikipedia

User talk:DreamRimmer

This user assumes good faith.
This user tries to do the right thing. If he makes a mistake, please let him know.


Bot request

[edit]

Hello, dear, DreamRimmer,

You do so much work to help the editors and admins on Wikipedia and, for that, I, and other editors, are incredily grateful. But if it is possible, could you program User:DreamRimmer bot II to issue the G13 eligible drafts report at the same time every hour? Before the past few weeks, the bot regularly published the report at X:25 UTC or X:26 UTC every hour. But recently, the time of publishing has varied a bit and is irregular. Can you program a specific time for the report to be issued? The time isn't that important (though the X:25 UTC time was convenient), it's more important that the timing is consistent.

If this is a big ask and more complicated than I know, then nevermind. But if it's not a big deal and it's something you can write in then this change would be very convenient for those of us who rely upon its reports. Thanks again for all that you do here on the project. And I hope you consider running in the next Admin elections or do your own RFA because I think you could really use access to the other admin tools. Liz Read! Talk! 03:45, 12 September 2025 (UTC)[reply]

The job is set to run on the 22nd minute of every hour. I chose this timing so it could complete the query, tag drafts, notify users, and update the final report page by the 25th minute. However, because there are many drafts and some complex queries, merging results, tagging, and notifying can take several minutes, so the actual completion time depends on when the database query finishes. I have adjusted the throttle so that tagging, and notifications happen as soon as the query is complete, which is the best I can do.
I also went for an RfA about a year and a half ago, which ended in a 50-50 result, so I will see if I can get a good article and re-run it in the future. – DreamRimmer ■ 15:46, 12 September 2025 (UTC)[reply]
Hello, DR,
Sorry to bring up an old RFA, I don't keep up with admin elections or RFAs so I was unaware you had tried before. I'm very surprised that you didn't pass as your skills seem obvious to me but I guess we still have some editors who require superb and abundant content creation. My own RFA was a bit of a trainwreck and my lack of lots of GA or FA articles that I created was one of the sore points but I did squeak through after a crat chat. I would expect at this point for that unwritten expectation would have faded away now the our need for new admins is high, at it seems that way to me, but I guess it hasn't. Maybe being part of the admin elections would be a better choice but it's up to you.
As for the original subject, I greatly appreciate the explanation you provided but right now, the G13 report came out at 5:39 pm so I don't know how that those results fit in here. The other day the report came out at 6:00 pm so maybe perhaps there is a clogged choke point where there are a lot of activity for the server to process. All I can see is that there isn't a way to write an extra line of code asking for a report to be produced at X:24 UTC each hour. So, that's the answer to my first question. Thanks again. Liz Read! Talk! 01:17, 14 September 2025 (UTC)[reply]
And the 6:24 pm report came out at 7:00 pm (my time). Liz Read! Talk! 02:09, 14 September 2025 (UTC)[reply]
I will try to adjust the timing when I get on my computer later today. – DreamRimmer ■ 02:12, 14 September 2025 (UTC)[reply]
Hello, DreamRimmer,
I was initally concerned about the G13 eligible drafts report being off by 10 or 15 minutes late in publishing but over the past few days we sometimes can go for one or two hours without DreamRimmer bot II updating a new G13 report. If it helps, there seems to be some server changes over the past 6 weeks that has impacted a number of different bots that rely on regular operation of the server for their reports. For example, look at what happened with DumbBOT! But there have been other issues, too. Thanks for checking on things. I know you likely have plenty of off-Wikipedia responsibilities that need your attention more so you'll get to us when you can. Liz Read! Talk! 01:47, 16 September 2025 (UTC)[reply]
This happens sometimes with my bot on Toolforge, where it is scheduled to run at 00:00 UTC, but recently it didn't execute till 00:55 UTC. Tenshi! (Talk page) 21:49, 16 September 2025 (UTC)[reply]
I also thought something might be wrong with Toolforge, as my jobs that should have completed within seconds were running for hours. – DreamRimmer ■ 06:01, 17 September 2025 (UTC)[reply]
I asked Liz if she knew anyone who could lighten her admin work, as she mentioned you. As someone who voted WP:NOTNOW during the last RfA, I see quite a bit growth, and I'm curious how that translates to the good article process. I'm not of the opinion that admins need to have a GA, but I do want to know they could learn to write one if they set their mind to it and review others. Are you able to critically review other articles, including for WP:TSI? And write a completely clean one yourself? Given the contentiousness of the previous RfA, you'll probably need to find strong nominators who opposed last time, and I'd say leave at least 2 years, maybe 3, between the runs. And probably most importantly, honest reflections on what went wrong last time, for instance with Q9. —Femke 🐦 (talk) 07:33, 18 September 2025 (UTC)[reply]
@Femke: Apologies for the delayed response; I missed your message. I really appreciate you taking the time to write to me. I feel bad for not meeting expectations in my first RfA and for disappointing many users, but I have taken your advice to heart. I will make sure to focus on achieving a GA before attempting another RfA. I have noted all your guidance and hope I will not let you down next time. I think 2026 or 2027 would be the best time for my next RfA, if I decide to run again. – DreamRimmer ■ 15:58, 22 September 2025 (UTC)[reply]

September thanks

[edit]
story · music · places

Thank you for improving article quality in September! - Today is the birthday of the 16th Thomaskantor after Bach, remembered. -- Gerda Arendt (talk) 13:05, 20 September 2025 (UTC)[reply]

My 100th biography to the Main page in 2025 is Siegmund Nimsgern. --Gerda Arendt (talk) 16:51, 22 September 2025 (UTC)[reply]

User:DreamRimmer bot II

[edit]

Hello, DreamRimmer,

You might need to restart this bot, the last G13 eligible drafts report was 5 hours ago. Now that is a biiiiiggg lag! Thank you and have a great weekend. Liz Read! Talk! 04:42, 21 September 2025 (UTC)[reply]

Restarted. Thanks:) – DreamRimmer ■ 05:12, 21 September 2025 (UTC)[reply]
Any idea why there are still problems generating User:DreamRimmer bot II/Reports/G13 eligible drafts? Going by my own time zone, the last report was 4:30 pm and now it's 8 pm and there have been no reports in the last 3 1/2 hours. I'm not going to pester you about this any more but it's no longer a matter of being 10 minutes late but hours late. Maybe this is a server issue, not a bot issue. Thanks for looking into this whenever you can. Liz Read! Talk! 03:05, 23 September 2025 (UTC)[reply]
Apologies for the issues over the past few days. Toolforge appears to be experiencing technical problems that are affecting all of my bots. I have observed that other users are encountering the same issue, and I will gather further details and submit a Phabricator ticket. Thank you for your understanding. – DreamRimmer ■ 03:38, 23 September 2025 (UTC)[reply]
It should be back to normal now. – DreamRimmer ■ 04:10, 25 September 2025 (UTC)[reply]

Tech News: 2025-39

[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

  • On September 24th at 15:00 UTC, all Wikimedia sites users will experience a brief read-only period due to a scheduled datacenter server switchover. The Wikimedia Foundation's Site Reliability Engineering (SRE) team will redirect all traffic from one primary server to its backup. You can listen to the switchover using the "Listen to Wikipedia" tool, where you will hear edits stop for a few minutes during the read-only phase, then resume. This twice-yearly datacenter server switchover ensures reliability by testing the backup datacenter, so that our sites can stay online even if the primary datacenter fails. You can read more about the process on the Diff blog.

Updates for editors

  • Editors of 60 more Wiktionaries will soon be able to call functions from Wikifunctions and integrate them into their pages. A function takes one or more inputs and transforms them into a desired output, like adding numbers, converting miles to meters, calculating elapsed time, or declining a word into a case. They will join the other 65 Wiktionary language editions, which already have access to embedded Wikifunctions calls. Later this year, plans are in place to expand to more Wiktionaries and the Incubator.
  • A new parser function has been added: {{#contentmodel}}. Template editors and admins can use it to get the localized or canonical name of the content model of a specific page. The function makes it easier to create and edit system messages, such as MediaWiki:editinginterface, even when you switch types of pages, like wiki, JavaScript, CSS or JSON page. [1]
  • Adding or editing a DISPLAYTITLE for an article using VisualEditor will no longer be broken. Editors who use VisualEditor mode to modify the {{DISPLAYTITLE}} would no longer have the literal text "DISPLAYTITLE" or its localized variant added to their articles. A list of pages that may have been affected and might need cleanup is documented in this ticket.
  • Beta users of the Wikipedia Android app can now try the redesigned Activity tab, which replaces the Edits tab. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging.
  • Recurrent item View all 12 community-submitted tasks that were resolved last week.

Updates for technical contributors

  • Recurrent item Detailed code updates later this week: MediaWiki

In depth

  • Wikifunctions users can now import many essential facts involving geo-coordinates, quantities and time values from Wikidata. This is made possible by the creation of Wikifunctions types for these values, which makes them available for use by functions in Wikifunctions. Learn more about how this works in this video and Wikifunctions' August 1 newsletter (for quantities) and August 22 newsletter (for geo-coordinates).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:51, 22 September 2025 (UTC)[reply]

"Unusual cases"

[edit]

On the BRFA, you said It would also be useful to log all unusual cases in the bot's userspace so that human editors can review and correct them. What specifically do you mean by this? Like details about where the bot is instructed to avoid, or an entire page with issues that the bot encountered issues, resulting in it avoiding making part/an entire edit? — Tenshi! (Talk page) 16:16, 27 September 2025 (UTC)[reply]

That was just a suggestion, as the bot has encountered some GIGO. If there are pages the bot skips because the current functions do not cover them, or edits it makes that still need human review, it would be helpful to log them on a subpage so you or others can fix them. There will not be many such pages, but since the bot operates automatically and you cannot review every edit, having a log would be useful. It’s entirely up to you. – DreamRimmer ■ 16:50, 27 September 2025 (UTC)[reply]

DR Editor

[edit]

Hi. Your DR Editor is currently seems to having problem in the Minerva skin. It's tampering with the delete logs, making the [change visibility] and other user link disappears, see before and after. The history page is also affected, see before and after (talk and contribs link is disappeared). Do you have a plan to fix that? This issues happened to me some days ago but I don't know which script causing this problem. I had to disable all my script and enable each one to see which one caused the bug, and the results is your DR Editor. Nvdtn19 (talk) 04:38, 29 September 2025 (UTC)[reply]

Tech News: 2025-40

[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

  • A major software upgrade has been made to Phabricator. The update introduces performance improvements, a refreshed search interface, enhancements to Maniphest task search, updates to user profile pages and project workboards, new Herald automation features, as well as general text input, mobile experience improvements and more. [2]

Updates for editors

  • The Community Tech team will release the new Community Wishlist extension on October 1, that will improve the way wishes will be submitted. The new extension will allow users to add tags to their wishes to better categorise them, and (in a future iteration) to filter them by status, tags and focus areas. It will also be possible to support individual wishes again, as requested by the community in many instances. The old system will be retired. There will be a brief period of downtime while the extension is deployed and wishes are migrated to the new system. You can read more about this in the latest update or you can consult the current documentation on MediaWiki.
  • As announced on Diff blog, the production trial of the hCaptcha service for bot detection has begun. The trial is currently using hCaptcha to protect account creation on Chinese, Persian, Portuguese, Indonesian, Japanese, and Turkish Wikipedias, where it will replace our existing CAPTCHA (FancyCaptcha). The goal with the trial is to better block bots while also improving usability and accessibility for users who encounter CAPTCHA challenges.
  • The CampaignEvents extension has been deployed to Wikimedia Commons. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. On Commons, anyone who is a registered user can use it as an event participant. To use it as an organizer, someone needs to have the event organizer right.
  • Sub-referencing, a new feature to re-use references with different details has been released to German Wikipedia. You can test the feature on testwiki or on betawiki as well. Please share your thoughts on using templates in sub-references or volunteer to become a pilot wiki.
  • On wikis using the Mentorship system, communities can now opt experienced editors out of Mentorship through Special:CommunityConfiguration/Mentorship. Within this setting, communities may define thresholds, based on edit count and account age, to decide when an editor is considered experienced enough to no longer receive Mentorship. [3]
  • The Editing Team and the Machine Learning Team are working on a new check for newcomers: Tone check. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Tone language model for the following languages: Arabic, Czech, German, Hebrew, Indonesian, Dutch, Polish, Russian, Turkish, Chinese, Farsi, Italian, Norwegian, Romanian and Latvian. Users from these wikis interested in reviewing this model are invited to sign up at MediaWiki.org. The deadline to sign up is on October 3, which will be the start date of the test.
  • The rollout of multiblocks had the side effect that non-active block logs may have been shown on Special:Contributions and on blocked users' user and user_talk pages. This issue will be fully resolved in a few days. As part of the fix, messages prefixed with sp-contributions-blocked-notice will be removed and replaced with those prefixed with blocked-notice-logextract in a few weeks. Please help translate the new messages and update any local overrides if needed.
  • There was a bug with links added using visual editor if they included characters such as [ ] | after the fragment identifier (#). They were not encoded properly creating an incorrect link. This has been fixed. [4]
  • One new wiki has been created: a Wikiquote in Malay (q:ms:) [5]
  • Recurrent item View all 21 community-submitted tasks that were resolved last week. For example, the User Info Card now displays currently active global lock/blocks. [6]

Updates for technical contributors

  • Later this week, editors using Lua modules will be able to use the mw.title.newBatch function to look up the existence of up to 25 pages at once, in a way that only increases the expensive function count once.
  • A new Unsupported Tools Working Group has been formed as part of ongoing efforts to collectively determine technical work priorities, similar to the Product & Technology Advisory Council (PTAC). The working group will help prioritize and review requests for support of unmaintained extensions, gadgets, bots, and tools. For the first cycle, the group will be prioritizing an unsupported Wikimedia Commons tool.
  • Recurrent item Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 20:48, 29 September 2025 (UTC)[reply]

[edit]

Hallo, I've just fixed the link you added at Wikipedia talk:New pages patrol/Reviewers#Concern about Agent VII's reviews, because you'd used a curly quote and it wasn't getting to the target. PamD 11:42, 1 October 2025 (UTC)[reply]

Thanks :) – DreamRimmer ■ 11:48, 1 October 2025 (UTC)[reply]

The Signpost: 2 October 2025

[edit]
This time "not merely negative".
Wickedpedia wrangles post-truth politics.
Unexpected news!
Fifty hot topics from fourteen noticeboards.
Policy, politics, icons, captchas, and LLMs.
And other recent publications.
When to walk away.
Rest in peace.
Celebrities, deaths and software.
All invited!
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 06:49, 2 October 2025 (UTC)[reply]

Left a message for you on meta

[edit]

...On your user talk page there. Need an admin with global rights to look into an attack page. ~Anachronist (who / me) (talk) 18:39, 2 October 2025 (UTC)[reply]

New Page Review training program

[edit]

I want to be trained as a New Page Reviewer and you are the trainer who lives very close to the timezone of my residency. I contribute to Wikipedia back and forth for quite a long time. My contributions since last year has been religions in East Asia (China, Japan, and Korea) and some composers of music. I like to use the citation templates very attentively.

I prefer other people to review my articles that I created. I plan to use my page-reviewing skills to resolve unreviewed articles relating to entities in East Asia as long as they are not related to South Korean politics (I'm absoluely loyal to the Japanese and North Korean political establishments) due to multiple encounters of harrassment by South Korean and Korean-American contributors over a decade ago. Komitsuki (talk) 07:45, 6 October 2025 (UTC)[reply]

Tech News: 2025-41

[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

  • Paste Check is a new Edit Check feature to help avoid and fight copyright violations. When editors paste text into an article, Paste Check prompts them to confirm the origin and licensing of the content. Starting Wednesday, 8 October, 22 wikis will test Paste Check. Paste Check will help new volunteers understand and follow the policies and guidelines necessary to make constructive contributions to Wikipedia projects.

Updates for editors

  • Mobile devices will receive mobile articles directly on the standard domain (like en.wikipedia.org), instead of via a redirect to an "m" domain (like en.m.wikipedia.org). This change improves performance. This week it will be enabled on Wikipedias. The existing mobile URLs and the "Desktop view" opt-out remain available. Learn more. [7]
  • New date filters, creationdate: and lasteditdate:, are now available in the wiki search engine. This allows users to filter search results by a page's first or last revision date. The filters support comparison operators (e.g. >2024) and relative dates (e.g. today-1d), making it easier to find recently updated content or pages within specific age ranges. [8]
  • Wikifunctions now supports rich text in embedded calls across the 150 wikis where it's enabled. To showcase this, the team created a Latin declination table that Wiktionary editors can use to automatically generate noun forms, producing clear, formatted results — see an example output. If you need any help or have any feedback, please contact the Wikifunctions Team. [9]
  • An edit link will now appear inside the categories box on article pages for logged in users, which will directly launch the VisualEditor category dialog. [10]
  • Recurrent item View all 34 community-submitted tasks that were resolved last week. For example, there was a problem downloading pdf files last week and that has been resolved. [11]

Updates for technical contributors

  • The field rev_sha1 in the revision database table is being removed in favor of content_sha1 in the content database table. See the announcement for more information.
  • The Reader Experience team will roll out Dark Mode user interface on all Wikimedia sites on October 29, 2025. All anonymous users of Wikimedia sites will have the option to activate a color scheme that features light-colored text on a dark background. This is designed to provide a more comfortable reading experience, especially in low-light situations. Template authors and technical contributors are encouraged to learn how to make pages ready for Dark mode and address any compatibility issues found in templates in their wiki before the enablement. Please contact the Web team for questions or any support on this talk page before the enablement. [12]
  • Starting on Monday, October 6, API endpoints under the rest.php path will be rerouted through a new internal API Gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the Service Ops team board. [13]
  • Recurrent item Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 17:19, 6 October 2025 (UTC)[reply]

September 2025 NPP backlog drive – Points award

[edit]
The Working Man's Barnstar
This award is given in recognition to DreamRimmer for accumulating at least 10 points the September 2025 NPP backlog drive. Your contributions played a part in the 19,000+ articles reviewed during the drive. Thank you so much for taking part and contributing to help reduce the backlog! Utopes (talk / cont) 03:44, 8 October 2025 (UTC)[reply]
Thanks! – DreamRimmer ■ 04:42, 8 October 2025 (UTC)[reply]

Administrators' newsletter – October 2025

[edit]

News and updates for administrators from the past month (September 2025).

Administrator changes

removed

CheckUser changes

removed Vanamonde93

Arbitration

  • After a motion, arbitration enforcement page protections no longer need to be logged in the AELOG. A bot now automatically posts protections at WP:AELOG/P. To facilitate this bot, protection summaries must include a link to the relevant CT page (e.g. [[WP:CT/BLP]]), and you will receive talk page reminders if you forget to specify the contentious topic but otherwise indicate it is an AE action.
Sent by MediaWiki message delivery (talk) 15:56, 8 October 2025 (UTC)[reply]