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

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

পাতাটির বিষয়বস্তু অন্যান্য ভাষায় নেই।
আলোচনা যোগ করুন
উইকিঅভিধান, মুক্ত অভিধান থেকে
(ব্যবহারকারী আলাপ:RedminBot থেকে পুনর্নির্দেশিত)
সাম্প্রতিক মন্তব্য: MediaWiki message delivery কর্তৃক ২৩ ঘণ্টা আগে "Tech News: 2026-33" অনুচ্ছেদে

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 ১৬:৪৯, ১৫ জুন ২০২৬ (ইউটিসি)উত্তর দিন

Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question

[সম্পাদনা]

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

Enjoy the reading! -- User:Sannita (WMF) (talk) ১২:৩৪, ১৯ জুন ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-26

[সম্পাদনা]

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

Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together

[সম্পাদনা]

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

Also, we remind you that if you have questions or ideas to discuss, the next Volunteers' Corner will be held on July 6, at 17:30 UTC (link to the meeting).

Enjoy the reading! -- User:Sannita (WMF) (talk) ০৯:৫৮, ২৭ জুন ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-27

[সম্পাদনা]

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

Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan

[সম্পাদনা]

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

Also, we remind you that if you have questions or ideas to discuss, the next Volunteers' Corner will be held on July 6, at 17:30 UTC (link to the meeting).

Enjoy the reading! -- User:Sannita (WMF) (talk) ০৮:২২, ২ জুলাই ২০২৬ (ইউটিসি)উত্তর দিন

Wikidata Platform Newsletter - July 2026

[সম্পাদনা]

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

  • Documentation on Query Rewrites: As WDQS continues its migration off Blazegraph, queries that rely on Blazegraph-specific extensions will need to be updated to comply with the SPARQL 1.1 and GeoSPARQL standards. To support this, we are publishing documentation to help you identify affected queries and rewrite them, so your queries keep working through the migration and beyond.
This transition to standard SPARQL reduces vendor lock-in, improves interoperability with other triplestores, and ensures our codebase remains robust. Importantly, the specifics of these rewrites are doing more than just guiding manual code updates. The details define the processing logic for an upcoming tool designed to automatically convert Blazegraph queries into standard SPARQL for the QLever engine.
The query rewrite details are focused on four key areas:
  1. Graph Analytic Services (GAS): See Blazegraph_Migration:_Rewrite_of_GAS
  2. MediaWiki API (MWAPI) Service: See Blazegraph_Migration:_Rewrite_of_MWAPI
  3. Label and Utility Services: See Blazegraph_Migration:_Rewrite_of_Label_and_Utility_Services_and_Functions
  4. Geospatial Functions: See Blazegraph_Migration:_Rewrite_of_Geospatial_Services_and_Functions
We Want Your Feedback!
As we map out these transition rules and develop the automated QLever conversion program, your input is critical. Please review the Wikitech pages linked above and let us know whether:
  • The rewrite rules cover your use cases
  • There are edge cases or specific Blazegraph quirks that are not accounted for
Please share your thoughts, concerns, or examples of queries on the related Discussion pages of the links above, so we can ensure the automated converter works seamlessly for everyone.
The system architecture from the WDQS v2 design doc has been implemented and deployed on Kubernetes. We ran a successful end-to end-test and validated that the QLever deployment can pick up a newly built index, start to backfill it with real-time events, and once ready the database can be queried. The service returns valid results, metrics are properly reported and available in Grafana, and logs are shipped to Wikimedia’s Observability Platform. Upcoming work will be focused on performance optimization and improvements to the indexing and real-time update pipelines supporting the service.
  • Timeline Update: As mentioned in our June newsletter, we are kicking off the Initial Implementation phase of the Blazegraph migration in July. After a few short weeks of final testing and iteration on the new endpoints, the first round of WDQS v2 users will be given access to the new endpoints so they can begin their migration. The QLever endpoints will become accessible to the broader community by October 1st, when we kick off Full Implementation, along with documentation on query rewriting.
  • Reminder to Report Use Cases: We encourage all members of the community to continue helping us identify higher-risk areas, namely SPARQL queries that are highly complex, by reporting use cases on our high-impact use cases and tools page. As a reminder, any use case can be reported through this mechanism. The purpose of this page is to give the WDP team visibility into user-level migration needs.
  • Blazegraph Migration Office Hour (July session): Our next Blazegraph Migration Office Hour will take place, Tuesday, 7 July 2026. 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-28

[সম্পাদনা]

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

Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone

[সম্পাদনা]

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

Enjoy the reading! -- User:Sannita (WMF) (talk) ০৯:৪৩, ৯ জুলাই ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-29

[সম্পাদনা]

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

Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables

[সম্পাদনা]

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August.

Enjoy the reading! -- User:Sannita (WMF) (talk) ১০:৫৫, ১৭ জুলাই ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-30

[সম্পাদনা]

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

Tech News: 2026-31

[সম্পাদনা]

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

Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania

[সম্পাদনা]
There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions.

Want to catch up with the previous updates? Check our archive!

Enjoy the reading! Quiddity (WMF) ১৯:০৫, ৩০ জুলাই ২০২৬ (ইউটিসি)উত্তর দিন

Wikidata Platform Newsletter - August 2026

[সম্পাদনা]

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

  • WDQSv2 Scaling: Work in Progress: The new QLever public endpoints are serving live traffic and are generally available to pilot cohort clients for testing. Our partner team at WMDE started porting the Query UI to https://query-next.wikidata.org and https://query-scholarly-next.wikidata.org. We have also rolled out a number of improvements to support federation and increase availability of the service. We have stood up a new staging environment on Kubernetes. Lastly, we are experimenting with a bleeding edge version of QLever that significantly improves memory footprint and update performance, and supports index rebuilds without needing service restarts.
  • SPARQL Query Re-Writing Tool: We have begun work on a tool that will rewrite Blazegraph-specific SPARQL queries into a format that is compatible with our new QLever implementation. This tool will apply the rewrite guidance we have published on WikiTech, offering an easier path for users to migrate to WDQS v2. The purpose of this tool is not to fully adapt all queries to the new endpoint, but to support users through their migration efforts. Development on the test infrastructure is underway and expected to be complete by August 14th. An evaluation of rewrite performance will be complete by September 4th, when we will share our results. We will iterate throughout the month of September and provide access to the tool by the first week of October.
  • Reminder to Report Use Cases: We encourage all members of the community to continue helping us identify higher-risk areas, namely SPARQL queries that are highly complex, by reporting use cases on our high-impact use cases and tools page. As a reminder, any use case can be reported through this mechanism. The purpose of this page is to give the WDP team visibility into user-level migration needs.
  • Blazegraph Migration Office Hour (August session): Our next Blazegraph Migration Office Hour will take place tomorrow, Tuesday, 4th August 2026. 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-32

[সম্পাদনা]

MediaWiki message delivery ১৯:৪৭, ৩ আগস্ট ২০২৬ (ইউটিসি)উত্তর দিন

ভুল কাজ করবেন না

[সম্পাদনা]

আমি রাতের বেলায় অনেক চেষ্টা করে মডিউল:names এবং টেমপ্লেট:surname ঠিক করেছি। আগে এগুলো ভুল ছিল। কিন্তু আপনি সব বাতিল করে আমার তৈরি পাতা গুলি নষ্ট করে দিয়েছেন। পাতা গুলিতে বড় করে লাল অক্ষরে লুয়া ত্রুটি করেছেন আপনি। এভাবে ভুল কাজ করে আমার পাতা গুলি নষ্ট করবেন না। আমি আবার ঠিক করেছি। আবার নষ্ট করবেন না। Dr. Mosaddek Khondoker (আলাপ) ০৯:৩২, ৯ আগস্ট ২০২৬ (ইউটিসি)উত্তর দিন

@Dr. Mosaddek Khondoker, আপনার সম্পাদনাগুলোর ফলে দুই হাজারের অধিক নতুন লুয়া ত্রুটি তৈরি হয়েছিল। আর সম্পাদনাগুলো দেখেও এআই দ্বারা করা করা হয়েছে বলে মনে হয়েছিল। (বলছি না আপনি আসলেই তা করেছেন তবে দেখে তেমনি মনে হয়েছে।) আপনি ‘names’ মডিউলের এর জন্য যেই নতুন ফাংশন লিখেছেন তার দরকার ছিল না, বরং তা দীর্ঘ মেয়াদে আমাদের নিয়মিত উইকিঅভিধান সম্পাদকদের কাজ বাড়িয়ে দিবে, ইংরেজি উইকিঅভিধানের মডিউল থেকে বেশি ডিভিয়েট করার কারণে। আপনি কি সমস্যার সম্মুখীন হয়েছিলেন যার জন্য মডিউলটা সম্পাদনা করতে হল? Redmin (আলাপ) ১০:২৯, ৯ আগস্ট ২০২৬ (ইউটিসি)উত্তর দিন
@Redmin আমি AI দিয়ে মডিউল ঠিক করেছি। কিন্তু আমার পাতাগুলো ঠিক হয়েছিল। আগে হতো, a পদবি from বাংলা। এরকম হতো। তাই আমি অনেক চেষ্টা করে AI কে দিয়ে ঠিক করেছিলাম। বারবার বলার পরেও AI ঠিক করতে পারছিল না। অনেক চেষ্টা করার পর ঠিক করতে পেরেছিল। এখন হয়েছে "বাংলা উৎসের পদবি।" Manna পাতায় দেখেন।
আমি ঠিক করার আগে ইংরেজি বাংলার মিক্সচার ছিল। কিন্তু আপনি করার পর আমার পাতাগুলো নষ্ট হয়েছিল। আমার পাতাগুলোতে বড় লাল অক্ষরে লুয়া ত্রুটি এসেছিল। Dr. Mosaddek Khondoker (আলাপ) ১৮:৩৫, ৯ আগস্ট ২০২৬ (ইউটিসি)উত্তর দিন

Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit

[সম্পাদনা]

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August.

Enjoy the reading! -- User:Sannita (WMF) (talk) ১৩:১৯, ১০ আগস্ট ২০২৬ (ইউটিসি)উত্তর দিন

Tech News: 2026-33

[সম্পাদনা]

MediaWiki message delivery ২০:৪৬, ১০ আগস্ট ২০২৬ (ইউটিসি)উত্তর দিন