User talk:Acebarry

Welcome!

Hello, Acebarry, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are a few links to pages you might find helpful:

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or click here to ask for help here on your talk page and a volunteer will visit you here shortly. Again, welcome! RJFJR (talk) 16:41, 10 October 2014 (UTC)[reply]

Category:Suckless

Category:Suckless, which you created, has been nominated for possible deletion, merging, or renaming. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the Categories for discussion page. Thank you. Dennis Brown - 2¢ 18:20, 12 March 2015 (UTC)[reply]

Disambiguation link notification for August 31

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited I2P, you added a link pointing to the disambiguation page Android. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 09:27, 31 August 2015 (UTC)[reply]

ArbCom 2017 election voter message

Hello, Acebarry. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible 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 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 3 December 2017 (UTC)[reply]

File:Sen Thomas Kean.jpg

See my comment on the talk page. I suggest you remove the speedy tag. MB298 (talk) 04:18, 27 February 2018 (UTC)[reply]

Your submission at Articles for creation: PeerTube (June 19)

Your recent article submission to Articles for Creation has been reviewed! Unfortunately, it has not been accepted at this time. The reason left by Robert McClenon was:

This submission's references do not adequately show the subject's notability. Wikipedia requires significant coverage (not just mere mentions) about the subject in published, reliable, secondary sources that are independent of the subject—see the general guideline on notability, the golden rule and learn about mistakes to avoid when addressing this issue. Please improve the submission's referencing (see Wikipedia:Referencing for beginners and Help:Introduction to referencing/1), so that the information is verifiable, and there is clear evidence of why the subject is notable and worthy of inclusion in an encyclopedia. If additional reliable sources cannot be found for the subject, then it may not be suitable for Wikipedia at this time.

The comment the reviewer left was:

This draft does not make a credible claim of significance for the social network (other than that it exists). It does not satisfy product notability or software notability.

Please check the submission for any additional comments left by the reviewer. You are encouraged to edit the submission to address the issues raised and resubmit when they have been resolved.

If you would like to continue working on the submission, go to Draft:PeerTube and click on the "Edit" tab at the top of the window.
If you now believe the draft cannot meet Wikipedia's standards or do not wish to progress it further, you may request deletion. Please go to Draft:PeerTube, click on the "Edit" tab at the top of the window, add "{{db-self}}" at the top of the draft text and click the blue "publish changes" button to save this edit.
If you need any assistance, you can ask for help at the Articles for creation help desk or on the reviewer's talk page.
You can also use Wikipedia's real-time chat help from experienced editors.

Robert McClenon (talk) 21:57, 19 June 2018 (UTC)[reply]

Hello, Acebarry! Having an article declined at Articles for Creation can be disappointing. If you are wondering why your article submission was declined, please post a question at the Articles for creation help desk. If you have any other questions about your editing experience, we'd love to help you at the Teahouse, a friendly space on Wikipedia where experienced editors lend a hand to help new editors like yourself! See you there! Robert McClenon (talk) 21:57, 19 June 2018 (UTC)[reply]

Interactive map

Hey there, good work on the interactive map for List of New Jersey state parks. Is there any chance you could add the state forests to the map? You show a lot of the green shading on the Google map, and a lot of that just represents state forests. If it's a crazy amount of work, then nevermind, but it was worth asking. ♫ Hurricanehink (talk) 22:11, 5 August 2018 (UTC)[reply]

As I get some time I hope to. That will be a much longer project Acebarry (talk) 13:01, 6 August 2018 (UTC)[reply]

Cool, well you have one user who will be very appreciative once that project is done! ♫ Hurricanehink (talk) 15:29, 6 August 2018 (UTC)[reply]

5/11 are already completed (thanks to other people). Maybe you'll be able to see the full map sooner than I thought! Acebarry (talk) 23:31, 6 August 2018 (UTC)[reply]

Hi, I would be interested in adding a shape for Tall Pines State Preserve, a 2015 addition to the state park system. I have a private Google Map of the park boundaries, which could probably be wrangled into a KML file. Does this data need to get onto GeoNames somehow? Would you prefer to do that yourself? I have no experience with that site, but am willing to learn. Atomsmith (talk) 21:22, 26 April 2020 (UTC)[reply]

Hi, first off thanks for the interest! Secondly, it looks like someone had added the preserve to OpenStreetMap (osm) already. I don't mind doing it, but if you want to as a learning experience here's what you have to do: 1. Verify the area on osm https://www.openstreetmap.org/way/40387475 . 2. Create a relation for the area in osm, if it doesn't already exist. 3. Tag the preserve in osm with the proper WikiData key https://wiki.openstreetmap.org/wiki/Key:wikidata 4. Make sure WikiData has an entry pointing to the relation you made 4. Update the query on List of New Jersey state parks to include the WikiData entry 12:41, 27 April 2020 (UTC)

ArbCom 2018 election voter message

Hello, Acebarry. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 2 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible 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 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 19 November 2018 (UTC)[reply]

ArbCom 2018 election voter message

Hello, Acebarry. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible 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 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 19 November 2018 (UTC)[reply]

File:Drbronners-logo-vert.png

Hi, I'm RonBot, a script that checks new non-free file uploads. I have found that the subject image that you recently uploaded was more than 5% in excess of the Non-free content guideline size of 100,000 pixels. I have tagged the image for a standard reduction, which (for jpg/gif/png/svg files) normally happens within a day. Please check the reduced image, and make sure that the image is not excessively corrupted. Other files will be added to Category:Wikipedia non-free file size reduction requests for manual processing. There is a full seven-day period before the original oversized image will be hidden; during that time you might want to consider editing the original image yourself (perhaps an initial crop to allow a smaller reduction or none at all). A formula for the calculation of the desired size can be found at WP:Image resolution, along with instructions on how to tag the image in the rare cases that it requires an oversized image (typically about 0.2% of non-free uploads are tagged as necessarily oversized). Please contact the bot owner if you have any questions, or you can ask them at Wikipedia talk:Non-free content. See User:RonBot for info on how to not get these messages. RonBot (talk) 17:06, 4 April 2019 (UTC)[reply]

Disambiguation link notification for July 7

Hi. Thank you for your recent edits. An automated process has detected that when you recently edited Weehawken Cove, you added a link pointing to the disambiguation page Hoboken (check to confirm | fix with Dab solver). Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 18:26, 7 July 2019 (UTC)[reply]

ArbCom 2019 election voter message

Hello! Voting in the 2019 Arbitration Committee elections is now open until 23:59 on Monday, 2 December 2019. 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 2019 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:16, 19 November 2019 (UTC)[reply]

Google Code-In 2019 is coming - please mentor some documentation tasks!

Hello,

Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at the English Wikipedia.

I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!

From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.

If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.

Thank you!

--User:Martin Urbanec (talk) 21:58, 23 November 2019 (UTC)[reply]

Nomination for deletion of Template:PD-NJGov

Template:PD-NJGov has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Wikiacc (¶) 23:04, 24 November 2019 (UTC)[reply]

ArbCom 2020 Elections voter message

Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. 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 2020 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) 02:35, 24 November 2020 (UTC)[reply]

ArbCom 2021 Elections voter message

Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. 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 2021 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:35, 23 November 2021 (UTC)[reply]

Orphaned non-free image File:Drbronners-logo-vert.png

⚠

Thanks for uploading File:Drbronners-logo-vert.png. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 17:05, 16 October 2022 (UTC)[reply]

ArbCom 2022 Elections voter message

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) 01:26, 29 November 2022 (UTC)[reply]

Monmouth County municipalities map

Hi! I saw that you made (or at least edited) the interactive map of municipalities in Monmouth County. Do you perhaps have a shapefile of any sort of the municipalities? I would like to use it for my own use in making a map (not for Wikipedia). Thanks! William on Tires (talk) 13:37, 24 May 2023 (UTC)[reply]

Unfortunately I don't have a shapefile. The map is generated by a SPARQL query that fetches the OpenStreetMap IDs, then draws the map. You may be able to use this link, https://maps.wikimedia.org/geoline?getgeojson=1&ids=Q502424 , and chain together all the geojson files to get some sort of structured data. It's also possible there's an even easier way but I don't know it right now Acebarry (talk) 17:34, 29 May 2023 (UTC)[reply]

CfD nomination at Wikipedia:Categories for discussion/Log/2024 September 13 § By-state law citation templates

A category or categories you have created have been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at Wikipedia:Categories for discussion/Log/2024 September 13 § By-state law citation templates on the categories for discussion page. Thank you. House Blaster (talk • he/they) 17:01, 13 September 2024 (UTC)[reply]

ArbCom 2024 Elections voter message

Hello! Voting in the 2024 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 2 December 2024. 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 2024 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:28, 19 November 2024 (UTC)[reply]

Wikidata Platform Newsletter - March 2026

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

Team communication update: Since November, our small and newly formed team has been developing our approach to sharing our work with the community and incorporating feedback. Migrating Wikidata Query Service’s infrastructure is a large and complex undertaking that serves many different audiences. Our goal has been to find the right mix of channels, engagement levels, and response times that allows us to reach the broadest possible audience with the resources we have.

Now that we have more of this structure in place, we are sharing project updates through regular newsletters and publishing reports and learnings on-wiki, where discussion pages are open for questions and comments. Our Phabricator board is available for flagging bugs or engaging in ongoing tasks. We also host regular office hours as a shared space for community members to raise questions and topics that may be relevant to others as well (next is in April). Questions added to the Etherpad will be addressed during those sessions.

The team reviews feedback shared through these channels and incorporates it where it helps advance our migration goals. While we aim to respond to questions within about a week when possible, we may not be able to reply to every individual point.

Label and MWApi service migration : We’ve completed an analysis of the wikibase:label and wikibase:mwapi services. One or both of these services are used in more than half of the requests sent to the Wikidata main graph. Preserving the functionality of these features is a core requirement of our backend migration away from Blazegraph. Full results of this investigation can be found on Wikitech.
Rate limits: Global rate limits for Wikimedia Foundation APIs were announced on March 2 and will be rolled out over the next month. These limits do not currently apply to WDQS, as we are still evaluating appropriate rate limits for our platform as part of our backend migration (ETA: July ‘26). In the interim, to protect against service interruptions like the ones observed during the week of February 23 following an increase in request volume and complexity, we have rate-limited a handful of identified users whose requests gridlocked our system. While details regarding specific actors have not been publicly disclosed (PII is involved) Wikimedia SRE deployed a workaround to a known Blazegraph bug that manifests under traffic spikes (T242453). While this does not solve the root cause of the problem, we expect it to increase WDQS reliability in the short term. We will continue to implement these spot fixes as needed until a more scalable solution is determined.
Work in progress: traffic analytics and operations: In the February sprint, we dedicated time to improving analytics on traffic and query behavior, with a particular focus on query latency classes and volumes by user-agent. This work provides two main benefits: 1) it informs different access patterns and latency-bound quality-of-service considerations, and 2) it led to short-term improvements in the real-time metrics we use to operate WDQS. We introduced new panels in Grafana, as well as internal-facing analytics tools, to report error rates and latency buckets, as well as new alerts that trigger on trends indicating timeouts. This approach allows us, on one hand, to proactively react to traffic spikes before an outage impacts end users, and on the other hand, to define the observability requirements that our new target backend will need to meet.
Work in progress: development and test infrastructure: In our previous newsletter, we published exploratory benchmarking that identified two candidate systems for Blazegraph replacement that met minimum requirements. The purpose was to gain experience with open source triple store implementations as we embark on the migration. Building on these learnings, one of our goals this quarter is to deploy test instances of Virtuoso and QLever on internal eqiad infrastructure, to gain experience operating both systems and supporting internal development efforts (T414443). We have now 4 hosts that serve main and scholarly data via QLever and Virtuoso (respectively). This work informed improvement ideas for our data infrastructure, and allowed us to refine our understanding of indexing times on graph splits. As part of this work, we modified the real-time index updater code base to remove hard dependencies on Blazegraph. While this is a work in progress, we can now update both QLever and Virtuoso indexes in real-time while reusing existing WDQS infrastructure (T414447). This allows us to experiment and load test traffic on infrastructure similar to Blazegraph-based WDQS, and is a milestone towards exposing a new backend to public traffic later this year. If you have experience operating Wikidata triple stores at scale, we would like to get in touch and exchange learnings.

Udehb-WMF (talk) 17:07, 12 March 2026 (UTC)[reply]

Wikidata Platform Newsletter - April 2026

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

Q3 Wrap-up: We closed out the month of March by completing all of our team goals for the quarter. This work included setting up test environments for production-replay traffic testing using on-premises hardware, the next step from last quarter’s benchmarking analyses, defining data access guidelines for our platform, and solidifying details of our migration plan such as release schedule and target use cases. The results of our Q3 efforts are currently being reviewed with internal stakeholders and will be shared with the community soon as part of our broader communication on the upcoming Blazegraph migration.
Q4 Plans: In Q4, the Wikidata Platform team is shifting from planning to execution readiness. We are focused on finalizing our migration plan, building out automated query validation to ensure correctness of the new service, developing a communications plan to smooth the transition, and beginning the technical build of our new architecture. In parallel, we are continuing work on platform access and Quality of Service (QoS) guidelines, including rate limiting and user authentication policies aimed at reducing system abuse, improving telemetry, and aligning with broader WMF standards. We will share more details and updates throughout the quarter.
Upcoming Feedback Cycles: Within this month of April, we will share artifacts outlining our recommendation for a Blazegraph replacement and our proposed technical architecture for the Wikidata platform. We welcome community feedback on our plans-your input will help us smooth the transition and develop mitigations for impacted use cases. We will share more details about the upcoming migration once we’ve collected and incorporated community feedback, including a timeline of changes, query rewriting best practices, and migration support documentation for the soon-to-be launched endpoints.
Team is Growing: Our team is growing! At the beginning of March, we welcomed Andrea Westerinen to the team as a contractor. In the coming months, Andrea will assist with the upcoming Blazegraph migration by creating technical documentation, providing query rewrite support, and advising on SPARQL requirements.
Rate Limiting Updates: As announced in last month’s update, we are working closely with site reliability engineers (SREs) to protect against WDQS service interruptions caused by increased request volume and complexity. While we work towards migrating to a more scalable backend that’s more resilient than Blazegraph, we are selectively rate-limiting users when we observe a correlation between their activity and performance incidents. Additionally, we have deployed and fine-tuned auto-remediation measures to restart servers that have been gridlocked. The intention of these changes is to stabilize the WDQS experience for the community, which we have observed to be effective. If you believe you’ve been negatively impacted by these changes, please let us know.
Runbooks for Common WDQS Issues:
- Data reconciliation: Some WDQS users reported an issue where items deleted from Wikidata were still queryable (T407702). Here’s some background to explain the issue: WDQS is continually synced against Wikidata via a streaming-update data flow with automatic retrying in case of failure, but it can happen that an update is missed and never gets picked up by the streaming updater. This can cause Blazegraph’s state to drift from Wikidata’s. In this case, we determined that the Wikidata deletion events were indeed missed by the streaming updater, and we resolved the issue by manually running a tool that rereads the source of truth for a specific entity (or list of entities) and updates Blazegraph accordingly. We also added a Wikitech runbook to document this fix. After the migration we will have more options available for keeping WDQS’s data up to date, including regular bulk data syncing and reindexing pipelines.
- High Lag troubleshooting: Over the last two quarters the Wikidata Platform team has been working with SRE teams to troubleshoot and proactively address queries and actors that are putting a strain on WDQS infrastructure. We reviewed existing metrics, alerts and Grafana panels, and tuned our instrumentation to emerging traffic patterns. We authored and shared a new runbook that guides Wikidata Platform engineers in troubleshooting and escalation, during periods of elevated WDQS load and user-facing query failures. This work is part of a broader operational excellence effort in which we are partnering with SRE and other teams at the Foundation to streamline cross-team collaboration and protect our infrastructure.
Wikidata through Wikimedia Enterprise: On March 31st, Wikimedia Enterprise announced the launch of Wikidata APIs as part of the suite of Enterprise offerings. These endpoints are built to support high-volume access needs by commercial reusers. This new resource will provide right-sized solutions for some of the largest consumers of Wikidata and users of our platform, supporting our vision for stable and sustainable access to Wikidata for everyone. More details can be found in WME’s full announcement.

Udehb-WMF (talk) 17:20, 13 April 2026 (UTC)[reply]

Wikidata Platform Newsletter - May 2026

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

Backend replacement and architectural design proposals: For the past few months, we've shared learnings from our investigations into backend replacement, and today we are sharing our recommendations for a new RDF database to replace and accompanying technical architecture for the migration away from Blazegraph as the backend of the Wikidata Query Service (WDQS). These documents outline the selected direction and how the new architecture is designed to improve scalability while making future backend changes easier.

We are inviting feedback from the Wikidata community and other WDQS users until 25th May 2026, particularly on:

Any important considerations we may have missed
How your WDQS use cases, tools, or workflows may be affected

We encourage you to share feedback on the migration discussion page. You can also join our upcoming office hour (Next tomorrow, May 12th) to ask questions and discuss your use cases.

To help identify higher-risk areas, we have created a page to track high-impact use cases and tools. This page is not intended to catalogue all WDQS usage, but to highlight complex or critical cases that may require additional attention.

Blazegraph Migration Office Hour (May session): Our next Blazegraph Migration Office Hour will take place on Tuesday, 12 May 2026 (Tomorrow) at 16:00 UTC. 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) 14:34, 11 May 2026 (UTC)[reply]

Wikidata Platform Newsletter - June 2026

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 16:00 UTC. 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]