I tested it.
I had left some past code in my User:Yug/Common.js . When Lingualibre came back in April 2021 the effect of that code was visible, and i had to remove it.
So this works on the ground for js, yes.

I don't have the skills to understand your whole proposal.
Wouldn't this solution ask the user to live its webbrowser tab open for a long duration (1000 audios = 5000 secs = 1h30mins ?) and creates an higher risk to lose the work of contributors ?
We currently don't have the development capability to lead such project.
(Our historic dev left 6 months ago for a sabatical year. We gathered ~4 juniors devs who slowly took back the project. We rose to +15% growth in the month of February alone. On March 9th OVH's data center in Europe had a massive fire, 150,000 websites have been affected or destroyed. We lost some data, code, wikipages, documentations. Our dev and wikimedian capability are centered on restoring those assets rights now, then onboarding, events and restoring trust for the next 4 months, afterwhat we will likely need a break. We are in situation similar to the Suez Canal today : digging to restore the flow :D )
But thanks for proposing assistance, it stays a major priority for us and we will come back to it later this year.

Received. Thanks for the alternatives.

This tag is far less visible than a column. Tickets wont get done, and new developers won't onboard. This project direly need new, active developers.

This seems pretty easy to fix.

Merci Poslovitch !

Won't a PR or commit conflict with Wikivalley's work at the moment ?

Is there a reason the tool isn't batching the uploads and doing it slowly in the background? then the user shouldn't need to wait around in their session?

Thanks for these avenues.

Try :lingualibre:Special:RecordWizard (a recording studio). the tool allows an human to record 1,000 audio per hour, or one every 3 sec. It's the service Wikimedia's Lingualibre provides : make rapid audio recording possible and easy. The ratelimit prevent us from delivering the target added value to most Wikimedia contributors. We need a work around. Any idea ? Any whitelisting procedure to follow ?

Merge accepted.

It's not a but. Emails are willfully disabled. We also don't have the "Email this user" link, because our account details are on Commons I assume.

My idea was to both create the language Qid and add a referencial lists on the go.
Could be a separate gadget, true, to separate concerns.
The two should be closely co-occuring tho.

Maybe rename Download or Downloads ? Datasets sounds ambiguous to me. Maybe Indians/native speakers could help. Anyway, so happy this datasets page is back !

@Seb35 : thank you for notifying us of your take over. I can redirect my energy elsewhere.

Thank for that info ! PS: is there a way to signal I read your comment without creating a comment myself ?

I see. thank.

@Poslovitch : your PR on operation repository, do you think it's safe (won't crash the code ?). If indeed safe, why not merge it right now.

@Poslovitch, please check comment above (I have no way to know if you seen or missed it). Also, in rare cases, I seen users having other rights such as image-reviewer which also grant the 999/sec, and not autopatroller. See here:

Commons user-rights assessment: that is exactly what I do by hand so far. See:

• User:Poemat's userrights - user recently granted autopatrol rights.
• User:Natschoba's userrights - new user with minimal user-rights but more than 4 days old.

To create the new property, I think @Pamputt is the man. Or VIGNERON.

@VIGNERON : Thank you ! exactly the kind of thing we ignore but need to know.
I do have a 3000 Chinese lexem datasets with hans, hant, pinyin (toned), pos, french translations.

Such feature request are good to document but seems a sloppy slop to me. We have to make decisions to keep the UX clear and cannot integrate all requested features/options, which each adds UX/UI complexity.
Lili values is to make mass recording rapid AND simple.

First, the limit parameter should follow local wiktionaries practices. On fr:wikt, it's large, let set it to 10~15 as of now.

See also : https://lingualibre.org/index.php?title=Special%3APrefixIndex&prefix=Property%3A&namespace=0 Special:PrefixIndex > Properties:

Thank you @MichaelSchoenitzer ! 🌻 😎

Deal. 👍🏼

@WikiLucas00, @Pamputt : this task title is "Start a new discussion in Chat room (and any link in any header) not working". Lingualibre.org website does not presents the bug anymore : the mentioned bug has been fixed and resolved. This task title has been answered.

Before to ask someone to code this...
IS THIS PROPERTY REALLY NEEDED SINCE ITS AN EXACT DERIVATIVE OF P-13 ?