I have a script for writing to the Wikidata API that respects the rate limit of 50 edits per minute for bots without a bot flag. However, when that script was used by somebody else, she received the error "As an anti-abuse measure, you are limited from performing this action too many times in a short space of time, and you have exceeded this limit.\nPlease try again in a few minutes". I think it is because she is a "newbie" who is subjected to a slower rate (i.e. as in https://www.mediawiki.org/wiki/Manual:$wgRateLimits).
Questions:
1. Is there a newbie rate limit that is slower than the rate for "normal" registered users?
2. If so, what is that limit?
3. How many edits must a newbie user make before they are no longer considered a "newbie" (or is number of edits not the criterion for being considered a newbie)?
Thanks!
Steve Baskauf
--
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Office: Eskind Biomedical Library, EMB 111
Phone: (615) 343-4582
https://my.vanderbilt.edu/baskauf/
This email is a summary of the Wikimedia production deployment of
1.37.0-wmf.16.
Mukunda Modell was the train conductor last week. Antoine Musso (hashar)
was the backup conductor.
Blocker task: https://phabricator.wikimedia.org/T281157
The new version is live on all sites: https://versions.toolforge.org/
== 📊 Stats ==
* 365 patches ↑
* 1 risky patch ↑
* 1 rollback (for ~2hours) ↑
* 0 days of delay ↓
* 2 blockers added, 0 resolved, 2 removed — same as last week
** OPEN: https://phabricator.wikimedia.org/T287704 by @mmodell
** RESOLVED: https://phabricator.wikimedia.org/T286490 by @dancy
== 🚂🌈 ==
A couple of tasks were mentioned but not added as blockers:
* OPEN: https://phabricator.wikimedia.org/T287642 by @brennen
* RESOLVED: https://phabricator.wikimedia.org/T287649 by @IKhitron
* RESOLVED: https://phabricator.wikimedia.org/T191021 by @Trizek-WMF
Thank you to everyone who filed tasks, triaged bugs, talked publicly, added
risky patch notifications, and braved yet another production deployment. To
quote Winnie the Pooh: "You are braver than you believe, stronger than you
seem, and smarter than you think"
Much thanks goes to:
* Addshore
* alexhollender
* daniel
* DannyS712
* Etonkovidova
* IKhitron
* Jdlrobson
* Krinkle
* Ladsgroup
* Legoktm
* Majavah
* ovasileva
* Pchelolo
* Zabe
– The Trainbow Bunch
Hi all,
With excitement we're sharing today that Vue.js is Wikimedia
Foundation's official choice for adoption as future JavaScript
framework for use with MediaWiki.
The evaluation of front-end frameworks officially started mid 2019, as
part of the Platform Evolution program’s goal to evolve our technology
platform and development processes to empower the Wikimedia
Movement[0].
The corresponding Technical RFC was successfully resolved in March
2020[1]. As this framework selection is a wide-ranging, long-term
decision, a dedicated group, the Front-end Architecture Working
Group[2], was established to drive the technology comparison and the
final recommendation. Besides the resolved RFC the outcome was to
build and test developer experience in a pilot project[3].
The selected pilot was within the Desktop Improvements project[4] with
its new Vue.js-based TypeaheadSearch feature that allows for providing
additional context while searching. Since its introduction in March
2021[5] the new TypeaheadSearch component has been the default across
15 wikis of varying sizes and has received positive user feedback[6].
A final developer satisfaction survey was completed to gain further
information on the developer experience. The survey results emphasized
“a positive light on the future of working with Vue.js”. And “[t]he
engineers felt optimistic about the future and confident in
recommending it for adoption across all our teams.”
The pilot gave us confidence in the recommendation to adopt Vue.js and
we are moving into further implementation of Vue.js tooling and
product migration planning.
To support further efforts, the Wikimedia Foundation has established
the Wikimedia Design System team[7], which I'm proudly part of. Our
continued work and upcoming priorities include:
- Preparing a shared Vue.js user-interface components library
- Deciding on Vue 2 or Vue 3 including transition path
- Figuring out how the components library will be built and
distributed in and beyond MediaWiki
You can find more of the ongoing work on Phabricator[8].
For full transparency, we've carried that knowledge with us for some
time already, but were prioritizing progressing integration, annual
planning and our internal All-hands conference to finally arrive at
this announcement today.
I'd like to thank a number of folks involved in leading to this, all
Front-end Architecture Working Group members, especially colleagues
Eric Gardner & Roan Kattouw for driving the RFC, the Readers Web team
for undergoing as pilot implementers and especially our former
colleague Stephen Niedzielski who was central to making it a success,
Wikimedia Deutschland for numerous insights through their Vue.js
experience, current Design System team members responsible for further
progress, all Movement volunteers involved in both providing feedback
to the pilot and contributing to development and Product & Tech
department leadership for their strong support of this wide-reaching
change.
Best regards,
Volker
References
[0] https://www.mediawiki.org/wiki/Platform_Evolution/Recommendations#1._Develo…
[1] https://phabricator.wikimedia.org/T241180
[2] https://www.mediawiki.org/wiki/Frontend_Architecture_Working_Group
[3] https://www.mediawiki.org/w/index.php?title=File:FAWG_Demo.pdf&page=26
[4] https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements
[5] https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Updates#Mar…
[6] https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements#List_of_ear…
[7] https://www.mediawiki.org/wiki/Design_Systems_Team
[8] https://phabricator.wikimedia.org/T286946
---
Volker Eckl
Design Lead
Wikimedia Design System
Wikimedia Foundation
1 Montgomery Street
Suite 1600
San Francisco, CA 94104
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2021-07): 257
Active Maniphest users (any activity) in (2021-07): 988
Task authors in (2021-07): 495
Users who have closed tasks in (2021-07): 265
Projects which had at least one task moved from one column to another on
their workboard in (2021-07): 296
Tasks created in (2021-07): 1911
Tasks closed in (2021-07): 1731
Open and stalled tasks in total: 47797
* Only open tasks in total: 46883
* Only stalled tasks in total: 914
Median age in days of open tasks by priority:
Unbreak now: 45
Needs Triage: 678
High: 940
Normal: 1467
Low: 2085
Lowest: 2145
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2021-07): 5
To see the names of the most active task authors:
* Go to https://wikimedia.biterg.io/
* Choose "Phabricator > Overview" from the top bar
* Adjust the time frame in the upper right corner to your needs
* See the author names in the "Submitters" panel
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on phab1001 at Sun 01 Aug 2021 12:00:19 AM UTC)