[03:14:36] Do I understand it correctly that this solution relies on manually whitelisting individual people to bypass the rate limit? (re @wmtelegram_bot: sees both on the Telegram side and does a happy dance) [03:15:34] I.e. would it still be desirable for the bridge bot to be able to retry sending a message if it gets the rate limit error? [03:17:36] The rate limit is on the Telegram side where the known user is @wmtelegram_bot. I think this means irc messages will come across the bridge as fast as irc sends now without loss. 🤞 (re @waldyrious: Do I understand it correctly that this solution relies on manually whitelisting individual people to bypass the rate limit?) [03:19:28] Got it, nice. But, follow-up question: does the same trick you used need to be set up for all the other bridged channels separately? Could this behavior be upstramed to the matterbridge software, or should it at least be mentioned in its docs? [03:23:58] It will be needed in any channels where the admins have set a rate limit. I have reported the issue upstream and would certainly welcome a general purpose solution. [03:25:04] https://github.com/42wim/matterbridge/issues/2020 [03:25:18] Nice! I'll follow that issue :) [08:31:46] Do we have a way of figuring out what programming languages our community of (volunteer) Wikimedia developers master in general? I'd be specifically interested to know which (and how many) people are proficient in Java, but it would be interesting to gauge the same thing for e.g. ... Python? Other programming languages... [08:35:34] https://en.wikipedia.org/wiki/Category:Wikipedians_by_programming_language [08:35:35] A bit flawed, since users who have been inactive for many many years are still listed, of course [08:37:18] the ones with 1,000+ users: [08:37:19] * BASIC [08:37:20] * C [08:37:22] * C++ [08:37:23] * Java [08:37:25] * Javascript [08:37:26] * PHP [08:37:28] * Python [08:44:33] Thanks much. We are quick to add things to lists, and slow to remove them. :) I think we need to curate this list better, which still has the two sites I mentioned in prominent positions. [08:44:34] [08:44:35] https://meta.wikimedia.org/wiki/Gender_gap/Resources (re @envlh: You can use https://humaniki.wmcloud.org/ for Humaniki. WHGI and Denelezh are no longer maintained for years.) [08:50:34] The annual survey has something about that I think ? (re @trnstlntk: Do we have a way of figuring out what programming languages our community of (volunteer) Wikimedia developers master in general?...) [08:52:42] https://meta.wikimedia.org/w/index.php?title=Gender_gap%2FResources&diff=24729881&oldid=24340451&diffmode=source (re @envlh: You can use https://humaniki.wmcloud.org/ for Humaniki. WHGI and Denelezh are no longer maintained for years.) [08:54:47] There's also [[*Denelezh*]] (re @fuzheado: https://meta.wikimedia.org/w/index.php?title=Gender_gap%2FResources&diff=24729881&oldid=24340451&diffmode=source) [08:55:18] /delete@wikilinksbot [16:34:45] @trnstlntk: https://meta.wikimedia.org/wiki/Research:Cloud_Services_Annual_Survey/2021#programming-languages is the 2021 survey response on Toolforge language use. The 2022 data is not published yet, but I think is planned to be out before the upcoming hackathon. [16:36:17] The report at https://k8s-status.toolforge.org/images/ is potentially useful information for language choice as well. Sorting that by "active pods" will give a kind of popularity ranking of programming languages and versions based on what is currently running in the Toolforge Kubernetes cluster. [16:37:40] The top 5 there are php 7.3, python 3.7, python 3.9, php 5, php 7.4. [16:38:34] * bd808 notices that the python 3.9 in the top 5 is actually python jobs rather than python webservices which also seems interesting [16:41:35] so many php5 pods D: [17:06:36] Super interesting! Thanks so much [17:31:59] @lucaswerkmeister: as you may remember, php5 was the default webservice backend for a long time. I would expect that most of those folks running php5 really aren't actively changing their tools. Wrote a thing N years ago and it has just kept working (or not, but still running) since. [17:32:15] *nod* [17:32:43] I suppose a decent number of them might be static websites too [17:53:47] 12:36:17 The report at https://k8s-status.toolforge.org/images/ is potentially useful information for language choice as well. <-- keep in mind that the majority of golang111-web tools are actually written in Rust :-)