Sunday 05:33, 14 June 2026 UTC

1:33 am 06/14/26 EDT

05:33 06/14/26 UTC

Temporary account IP viewer granted

edit
The temporary account IP viewer logo, composed of the Wikipedia globe with a user and an IP address

Hello, Cosmic840. Per your request, your account has been granted temporary-account-viewer rights. You are now able to reveal the IP addresses of individuals using temporary accounts that are not visible to the general public. This is very sensitive information that is only to be used to aid in anti-abuse workflows. Please take a moment to review Wikipedia:Temporary account IP viewer for more information on this user right. It is important to remember:

  • You must not share IP address data with someone who does not have the same access permissions unless disclosure is permissible as per guidelines listed at Foundation:Policy:Wikimedia Access to Temporary Account IP Addresses Policy.
  • Access must not be used for political control, to apply pressure on editors, or as a threat against another editor in a content dispute. There must be a valid reason to investigate a temporary user. Note that using multiple temporary accounts is not forbidden, so long as they are not used in violation of policies (for example, block or ban evasion).

It is also important to note that the following actions are logged for others to see:

  • When a user accepts the preference that enables or disables IP reveal for their account.
  • Revealing an IP address of a temporary account.
  • Listing the temporary accounts that are associated with one or more IP addresses (using the CIDR notation format).

Remember, even if a user is violating policy, avoid revealing personal information if possible. Use temporary account usernames rather than disclosing IP addresses directly, or give information such as same network/not same network or similar. If you do not want the user right anymore then please ask me or another administrator and it will be removed for you. You may also voluntarily give up access at any time by visiting Special:Preferences. Happy editing!  rsjaffe 🗣️ 22:24, 23 April 2026 (UTC)Reply

Rollback granted

edit

Hi Cosmic840. After reviewing your request, I have enabled rollback on your account. Please keep the following things in mind while using rollback:

  • Being granted rollback is no more momentous than installing Twinkle or Ultraviolet. It just adds a [rollback] button next to a page's latest live revision. It does not grant you any additional "status" on Wikipedia, nor does it change how Wikipedia policies apply to you.
  • Rollback should be used to revert clear and unambiguous cases of vandalism only. Never use rollback to revert good faith edits. For more information about when rollback is appropriate, see Wikipedia:Rollback § When to use rollback.
  • Rollback should never be used to edit war, and it should never be used in a content-related dispute to restore the page to your preferred revision. If rollback is abused or used for this purpose or any other inappropriate purpose, the permission will be revoked.
  • Use common sense. If you're not sure about something, ask!

I'm sure you'll do great with rollback, and feel free to leave me a message on my talk page if you run into trouble or have any questions about appropriate use of rollback. If you no longer want rollback, contact me and I'll remove it. For information on rollback, see Wikipedia:Administrators' guide/Rollback (even though you're not an admin) and Wikipedia:Rollback. Good luck and thanks! HJ Mitchell | Penny for your thoughts? 17:22, 5 May 2026 (UTC)Reply

Pending changes reviewer granted

edit

Hello. Your account has been granted the "pending changes reviewer" userright, allowing you to review other users' edits on pages protected by pending changes. The list of articles awaiting review is located at Special:PendingChanges, while the list of articles that have pending changes protection turned on is located at Special:StablePages.

Being granted reviewer rights neither grants you status nor changes how you can edit articles. If you do not want this user right, you may ask any administrator to remove it for you at any time.

See also:

* Pppery * in solidarity 05:33, 27 May 2026 (UTC)Reply

Relisting of Independent music RM

edit

Hi, just curious why you relisted Talk:Independent_music#Requested_move_27_May_2026. It has only been open for four days, so it is not elapsed. Vpab15 (talk) 16:39, 31 May 2026 (UTC)Reply

Since there's no consensus, it has been relisted because it had no voting since the requested move started. This is done using Move+. ~ŤheŴubṂachine-840✒️ 16:46, 31 May 2026 (UTC)Reply
WP:RELIST says a relist can be done after seven days. I don't think you should relist before that. Vpab15 (talk) 17:43, 31 May 2026 (UTC)Reply
Thanks for the advice, i didnt know that there was a WP:RELIST page, and since I'm new to voting on requested moves. ~ŤheŴubṂachine-840✒️ 17:50, 31 May 2026 (UTC)Reply

This week's article for improvement (week 23, 2026)

edit


Hello, Cosmic840. The article for improvement of the week is:

Articulated bus

Please be bold and help improve it!


Previous selections: Partnership for Peace  Harbor


Get involved with the AFI project: Nominate an article  Review nominations


Posted by: MusikBot talk 00:05, 1 June 2026 (UTC) using MediaWiki message delivery (talk) on behalf of WikiProject AFI • Opt-out instructionsReply

Administrators' newsletter – June 2026

edit

News and updates for administrators from the past month (May 2026).

Administrator changes

added
readded
removed

Bureaucrat changes

removed

Guideline and policy news

Technical news

  • Mandatory 2FA for bureaucrats: Bureaucrats without two-factor authentication (2FA) enabled have already lost access to their advanced rights on 26 May. Those who do not enable 2FA may be automatically removed from the groups in mid-June 2026, and from that point onward, new members must have 2FA enabled before they can be added. (T423119, T423120)

Arbitration

  • The arbitration case SchroCat has been closed.
  • The arbitration case Michael Jackson has opened. Evidence submissions in this case closes on 1 June.

Miscellaneous


Good Article Gazette, Issue 15

edit
Logo: Good Article Gazette - the official GAN newsletter
Logo: Good Article Gazette - the official GAN newsletter
Issue 15, 1 June 2026
Ongoing discussionsNewsCurrent statistics
  • Number of GAs: 43,915 (+32)
  • Number of nominations: 1033 (+53)
  • GAs for reassessment: 42 (–32)

MediaWiki message delivery (talk) 15:03, 1 June 2026 (UTC)Reply

Wikidata weekly summary #734

edit

This Month in Education: May 2026

edit

End of the 2026 Core Contest!

edit

The Core Contest has now ended! Thank you for your interest and efforts. Make sure that you include both a "start" and "improvement diff" on the entries page. The judges will begin delibertaing shortly and annouce the winners within the next few weeks. Cheers from the judges, Femke, Casliber, Aza24. – Aza24 (talk) 18:27, 1 June 2026 (UTC)Reply

If you wish to start or stop receiving news about The Core Contest, please add or remove yourself from the delivery list.

Tech News: 2026-23

edit

MediaWiki message delivery 21:06, 1 June 2026 (UTC)Reply

Books & Bytes – Issue 74

edit
The Wikipedia Library: Books & Bytes
Issue 74, March–April 2026
  • New partnership: Swissdox
  • User survey results
Read the full newsletter

Sent by MediaWiki message delivery on behalf of The Wikipedia Library team – 10:34, 2 June 2026 (UTC)Reply

WikiProject Yorkshire Newsletter - June 2026

edit
Delivered June 2026 by MediaWiki message delivery.
If you do not wish to receive the newsletter, please add an N to the column against your username on the Project Mainpage.

12:52, 3 June 2026 (UTC)

Alexis Boon

edit

You recently added a notability concern template to the new stub article on Alexis Boon. However, there's no explanation as to what the notability concern is on the talk page for the article. Might I ask that you either explain the concern or, ideally, remove the template. Many thanks. Greenshed (talk) 08:12, 6 June 2026 (UTC)Reply

This week's article for improvement (week 24, 2026)

edit


Hello, Cosmic840. The article for improvement of the week is:

Drinking water

Please be bold and help improve it!


Previous selections: Articulated bus  Partnership for Peace


Get involved with the AFI project: Nominate an article  Review nominations


Posted by: MusikBot talk 00:05, 8 June 2026 (UTC) using MediaWiki message delivery (talk) on behalf of WikiProject AFI • Opt-out instructionsReply

Wikidata Platform Newsletter - June 2026

edit

This is the 7th issue of our monthly newsletter! The next issue will be published in July 2026.

  • QLever as the New Backend System for WDQS: After reviewing feedback from the community on our architectural proposals shared last month (see Backend Replacement and WDQS Architecture Re-Design), we have decided to migrate to QLever as the new backend for the Wikidata Query Service. This decision has been aligned upon across partners in WMF, WMDE, and the QLever team. We are very excited about the improvements to performance and sustainability that this choice unlocks for WDQS users. We will continue to share details on the user-facing impacts of this decision, in future newsletters and on our migration project page, as the work progresses.
We encourage all members of the community to continue helping us identify higher-risk areas by reporting use cases on our high-impact use cases and tools page. This page is not intended to catalogue all WDQS usage, but to highlight complex or critical cases that may require additional attention.
  • Migration Timeline: Following the decision to use QLever, we would like to share some key milestones for our migration. More details will be shared as we approach full implementation. Please note that all dates are targets and may change in the event of unforeseen challenges. Refer to the migration project page for up to date information.
    1. Exploration: (COMPLETED) From September through March, the team conducted traffic and benchmarking analyses to understand the needs of WDQS users and alternatives to our current system. This culminated in our final recommendations for a new backend and platform architecture, which have been reviewed and aligned upon across stakeholders.
    2. Installation: (IN-PROGRESS) In April, the team began building. The development of new QLever endpoints (ie. WDQS v2) is underway, as is the refactoring of our platform architecture. This includes work on indexing, update pipelines, and rewriting observed production traffic into the SPARQL 1.1 standard. We are on track to complete our build of the new endpoints by July 1st and transition into initial implementation. The query service will continue to be available in its current state through implementation phases.
    3. Initial Implementation: (NOT STARTED) WDQS v2, a new endpoint built on QLever, will be first available to a small number of pilot users. The team will work closely with this group to learn where improvements are needed and how we can best support users in independently migrating their use cases. A self-service hub will be published by October 1st. This will include learnings from our pilot group, guidance on how all users of WDQS can migrate their work flows, and documentation on best practices for adapting all Blazegraph dependencies to our new system or alternative endpoints where needed.
    4. Full Implementation: (NOT STARTED) The new endpoints will be scaled to meet the needs of the broader community and will be generally accessible to all. The original Blazegraph endpoints will still be available, but may experience service degradation beginning in February, 2027 as we reallocate resources to the new infrastructure and begin slowly winding down the legacy service. We aim to have all WDQS traffic migrated by June 30, 2027, at which time the Blazegraph endpoint will be decommissioned.
  • Query Categorization and Testing: We have begun evaluating WDQS queries to identify Blazegraph-specific features and functionality. All bespoke query aspects need to be rewritten into the SPARQL 1.1 standard in order to work with the new QLever backend. We have documented our process for this work in two Wikitech publications on SPARQL Query Characterization and Test Architecture for QLever. These documents provide more detail on methodology and testing used to validate the correctness and performance across the new and old backends. They are intended as supporting technical references for contributors interested in the migration validation and benchmarking approach.
  • 2026-05-08 incident report: On May 7, 2026, aggressive web scrapers began overwhelming the Wikidata Query Service (WDQS), triggering a multi-day service degradation that impacted both availability and lag SLOs. The excessive load caused Blazegraph to timeout for over half of users at peak, while also throttling the streaming updater, which blocked index updates and cascaded into edit throttling on wikidata.org itself. Initial mitigation on May 7-8 included depooling the eqiad datacenter WDQS deployment and applying rate limits based on sampled request data, but the outage persisted through the weekend. Full resolution came on Monday, May 11, when deeper analysis of WDQS logs revealed a scraper that had evaded sampled webrequest data used for initial rate limiting. Once a targeted rate limiting rule was applied to the scraper's signatures, timeout rates returned to normal. See the full incident report
  • Blazegraph Migration Office Hour (June session): Our next Blazegraph Migration Office Hour will take place on Tuesday, 9 June 2026 (Tomorrow) at . This session is focused on supporting the migration away from Blazegraph as the backend of WDQS. Whether you have questions, need clarification, or want to discuss how your use case may be affected. You can register for the session via the event page.
In preparation, we encourage you to add questions, feedback, or migration-related support needs to this etherpad. This helps us shape the agenda and focus on the most relevant topics during the session.

Udehb-WMF (talk) 11:10, 8 June 2026 (UTC)Reply

thank you!

edit

Thank you for setting up the iOS 27 pages! Enjoy WWDC! CharlieRidesRollerCoasters (talk) 12:44, 8 June 2026 (UTC)Reply

Wikidata weekly summary #735

edit

Tech News: 2026-24

edit

MediaWiki message delivery 21:28, 8 June 2026 (UTC)Reply

DYK nomination of MacOS Golden Gate

edit

Hello! Your submission of MacOS Golden Gate at the Did You Know nominations page has been reviewed, and some issues with it may need to be clarified. Please review the comment(s) at your nomination's entry and respond there at your earliest convenience. Thank you for contributing to Did You Know! Dclemens1971 (talk) 16:39, 9 June 2026 (UTC)Reply

Wikimedia Foundation Bulletin 2026 Issue 10

edit

MediaWiki message delivery 22:31, 9 June 2026 (UTC)Reply

Saturday, July 18, 2026 Minnesota User Group Wiknic!

edit
In the area? You're invited to the Minnesota User Group Wiknic July 2026
Saturday July 18, 2026 the Wikimedians of Minnesota User Group is having a Wiknic at the Minnesota State Capitol! We will be picnicing in the shade near the Minnesota Woman Suffrage Memorial, so bring a picnic blanket, lawn chairs and a hot dish for the picnic if you like! We'll also be providing sandwiches for everyone but we encourage you to bring your own favorite dishes to share. All Minnesota Wikipedia editors and wanna-be editors are welcome! Learn more »

When: Saturday, July 18, 2026
Time: 10 to 1:30 pm
Place: Minnesota State Capitol Mall, St. Paul, MN

  If you don't wish to receive these invitations anymore, please remove your username from our invitation list. Thanks.

MediaWiki message delivery (talk) 20:44, 11 June 2026 (UTC)Reply

Speedy deletion declined: Draft:John Hakim, MD

edit

Hello Cosmic840. I am just letting you know that I declined the speedy deletion of Draft:John Hakim, MD, a page you tagged for speedy deletion, because of the following concern: G12 declined - the copied material is a list of publications. There is no creativity in this list to generate a copyright. Thank you. Whpq (talk) 21:14, 11 June 2026 (UTC)Reply

Guild of Copy Editors – June 2026 Newsletter

edit
Guild of Copy Editors June 2026 Newsletter

Hello and welcome to the June 2026 newsletter, a quarterly-ish digest of Guild activities since April.

Election news: Nominations for the mid-year coordinator election ends at 23:59 on 15 June. Voting will last from 00:00 on 16 June to 23:59 on 30 June. Results will be announced on the election page.

April Blitz: 18 of the 21 editors who signed up for the April 2026 Copy Editing Blitz copy edited 122,993 words in 56 articles. Barnstars awarded are here.

May Drive: 34 of the 66 editors who signed up for the May 2026 Backlog Elimination Drive copy edited 543,972 words in 211 articles. Barnstars awarded are here.

June Blitz: Our June 2026 Copy Editing Blitz will start on 14 June and finish on 30 June. Barnstars awarded will be posted here.

Progress report: As of 22:40, 11 June 2025 (UTC), GOCE copyeditors have completed 132 requests since 1 January, and the backlog stands at 1,691 articles.

Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators.

To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

MediaWiki message delivery (talk) 22:57, 11 June 2026 (UTC)Reply

This Month in GLAM: May 2026

edit




Headlines
Read this edition in full Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.