বিষয়বস্তুতে চলুন

ব্যবহারকারী আলাপ:Redmin

পাতাটির বিষয়বস্তু অন্যান্য ভাষায় নেই।
আলোচনা যোগ করুন
উইকিঅভিধান, মুক্ত অভিধান থেকে
সাম্প্রতিক মন্তব্য: MediaWiki message delivery কর্তৃক ২ দিন আগে "Tech News: 2026-25" অনুচ্ছেদে

I seen your RedminBot Tamil entries Creations

[সম্পাদনা]

I seen your RedminBot Tamil entries Creations . That's was really nice. I hope you are interested in Tamil entries creations. Thanks for your continuous support! i created a spreadsheet file for Creating Tamil entries in bnwikt See this. This maybe useful for your bot Tamil entries. Thanks Again. Sriveenkat (আলাপ) ০৭:৩৩, ৫ অক্টোবর ২০২৩ (ইউটিসি)উত্তর দিন

Thank you for this! I will make entries manually as this is too complex for the bot but this really helps. :D Redmin (আলাপ) ০৯:৩৭, ৫ অক্টোবর ২০২৩ (ইউটিসি)উত্তর দিন
Ok Redmin Thanks. We will do manually Thanks Again. Sriveenkat (আলাপ) ০৯:৫৭, ৫ অক্টোবর ২০২৩ (ইউটিসি)উত্তর দিন

পর্যালোচনা

[সম্পাদনা]

နာမ် এর বিশেষ্যের জন্য মডিউল তৈরি করেছি: মডিউল:my-headword

ইংরেজিতে [Module:my-headword]

কিন্তু কাজ হচ্ছে না কেন? 哈立德 ১৮:২৩, ২৮ ডিসেম্বর ২০২৩ (ইউটিসি)উত্তর দিন

@খালিদ জে. হোসেইন, এখনও কি একই অবস্থা? Redmin (আলাপ) ১৪:০৪, ৩ জানুয়ারি ২০২৪ (ইউটিসি)উত্তর দিন
জ্বি, এখন ঠিক আছে। ধন্যবাদ। 哈立德 ০১:৩১, ৫ জানুয়ারি ২০২৪ (ইউটিসি)উত্তর দিন

Reminder to vote now to select members of the first U4C

[সম্পাদনা]

You can find this message translated into additional languages on Meta-wiki. দয়া করে আপনার ভাষায় অনুবাদ করতে সাহায্য করুন

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) ২৩:১৬, ২ মে ২০২৪ (ইউটিসি)উত্তর দিন

Tech News: 2026-09

[সম্পাদনা]

MediaWiki message delivery ১৯:০৪, ২৩ ফেব্রুয়ারি ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-10

[সম্পাদনা]

MediaWiki message delivery ১৭:৫২, ২ মার্চ ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-11

[সম্পাদনা]

MediaWiki message delivery ১৮:৫৩, ৯ মার্চ ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-12

[সম্পাদনা]

MediaWiki message delivery ১৯:৩৬, ১৬ মার্চ ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-13

[সম্পাদনা]

MediaWiki message delivery ১৬:৫১, ২৩ মার্চ ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-14

[সম্পাদনা]

MediaWiki message delivery ১৯:২৬, ৩০ মার্চ ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-15

[সম্পাদনা]

MediaWiki message delivery ১৬:১৯, ৬ এপ্রিল ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-16

[সম্পাদনা]

MediaWiki message delivery ১৫:১৯, ১৩ এপ্রিল ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-17

[সম্পাদনা]

MediaWiki message delivery ১৫:০১, ২০ এপ্রিল ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-18

[সম্পাদনা]

MediaWiki message delivery ১৮:০৬, ২৭ এপ্রিল ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-19

[সম্পাদনা]

MediaWiki message delivery ২০:৪৩, ৪ মে ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-20

[সম্পাদনা]

MediaWiki message delivery ১৯:২০, ১১ মে ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-21

[সম্পাদনা]

MediaWiki message delivery ২০:২২, ১৮ মে ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-22

[সম্পাদনা]

MediaWiki message delivery ২১:৫২, ২৫ মে ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-23

[সম্পাদনা]

MediaWiki message delivery ২১:০৯, ১ জুন ২০২৬ (ইউটিসি)উত্তর দিন

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 টেমপ্লেট:zonestamp. 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 (আলোচনা) ১১:১০, ৮ জুন ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-24

[সম্পাদনা]

MediaWiki message delivery ২১:৩০, ৮ জুন ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-25

[সম্পাদনা]

MediaWiki message delivery ১৬:৪৯, ১৫ জুন ২০২৬ (ইউটিসি)উত্তর দিন