User talk:AntiCompositeNumber

1. Richard Q. Ricardo (talk · contribs)
2. Packers kill Texans (talk · contribs)
3. Knile Davis is my hero (talk · contribs)
4. Jefferson9000 (talk · contribs)
5. DoRD can't stop me (talk · contribs)
6. Packers lose, unleash the takes (talk · contribs)

These accounts above are socks of mine who haven’t been locked globally yet. I will never use them again. I tried to recover passwords for them but it didn’t work. So therefore, I need you to globally lock them so I never use them again. If you globally lock them, I promise I will never sock again.

If I understood correctly you said in phab:T283083 [Session] RFC: Re-evaluate librsvg as SVG renderer on Wikimedia wikis , that phab:T40010 RFC: Re-evaluate librsvg as SVG renderer on Wikimedia wikis is stuck by phab:T216815 Upgrade Thumbor to Buster, which is planed for this summer and might delay depending on the thumbor-responsible person User:GDubuc_(WMF), who is very busy because he is also in the Wikimedia Performance Team. (However I do not understand how postponing reduces work?)

However regarding my memory about your statement I have two questions:

1. According to the Debian-release-table, the end of Security-support ended June2018 (3years ago), and the end of long-term-supports will end June2022 (one year ahead). Is there a different Wikipedia-update-circle?
2. Why does phab:T40010 RFC: Re-evaluate librsvg as SVG renderer on Wikimedia wikis depend on phab:T216815 Upgrade Thumbor to Buster? resvg is portable, so it is independent on the thumbor-server-version, so I see no reason to wait on the thumbor-update.

The rough guideline is wikitech:Operating_system_upgrade_policy. That document hasn't been fully implemented, but my understanding is that most teams were working toward the June 2021 target (progress tracked in phab:T247045). Changing the SVG renderer isn't blocked on the OS upgrade in the traditional sense, rather it is a question of development priorities. Potentially changing the SVG renderer is a lower priority than the OS upgrade. Changing the Thumbor dependencies while someone else is working on OS upgrades could complicate the upgrade process and duplicate work. Because I don't have good visibility into how the upgrade work is proceeding, I would be reluctant to make changes to Thumbor to implement an SVG renderer change at this time.

Is it possible to generate a list of all the active editors, at all the wikis, that have the same error?

I've settled on sending error-specific messages, and I've written one at m:User:Whatamidoing (WMF)/Custom signature that is being translated. If we can make a list in MassMessage format later this month, then one of my teammates will use Tech/News' magic multilingual script to send the translated messages to everyone.

Could you generate that list (for just the one error – I'm starting with mismatched usernames), or do we need to go through each wiki separately and add them all up?

Unfortunately, doing it in the tool would require more development time than I have at the moment.

Okay. I'll just get the lists separately. It should be as easy as copying and pasting, but if I run into any trouble, I'll let you know.

It looks like it was as easy as expected, and once I got past the large wikis, it was even pretty quick. Thanks again for writing this tool.

I was looking for your custom sig-checking script today, and I get a 404 error. Do I have the wrong link, or has it been deleted?

It's still at https://signatures.toolforge.org. What URL were you looking at?

Something on Github, I think; it was probably an earlier version.

https://signatures.toolforge.org/check seems to have two radio buttons with the same label. "Obsolete font tag" can be removed, as the devs decided not to enforce that in this version.

I'm thinking about putting a link to the check-your-own-sig page in Tech/News (i.e., adding this a week from now, so it gets posted in about 10 days). People may want to see more about their wikis. Could you please add reports for Commons, Wikidata, and as many of the bigger wikis as you feel like?

Eventually, I'm going to need lists of usernames that need to be fixed, split by the problem that needs to be fixed. (I'd like to be able to send people a message that is specific to their own problem, rather than "Something's wrong; it's probably one of the things in this long list".)

https://signatures.toolforge.org/reports now has up-to-date reports for those and a few other large wikis. I finally set up a cron job to update them Obsolete font tag is removed from the default set, so it won't show up in the reports. I fixed the translation message issue causing the duplicate label. https://signatures.toolforge.org/api/ should be able to provide the lists you're looking for.

https://signatures.toolforge.org/api/ isn't working for me. I wanted to get a list of mismatched usernames at enwiki.

https://signatures.toolforge.org/api/v1/reports/en.wikipedia.org/error/link-username-mismatch should do it.

Who is User talk:\u661f\u661f ?

JSON doesn't support Unicode characters, so that's the escaped form of @星星. https://signatures.toolforge.org/api/v1/reports/en.wikipedia.org/error/link-username-mismatch?format=plain has the unescaped version.

I think that we have false positives on & and ' characters.

It was an issue with HTML entities. I've fixed it.