Perhaps the easiest solution is to load the commons one on other wikis?

There isn't anything magical here.

@zhuyifei1999: ah, oops I'm not sure how I overlooked that :-)

So maybe it could benefit from a server-side generation of the admin list (and perhaps a localstorage cache of the same?).

Use the XTools API! https://xtools.wmflabs.org/api/project/admins_groups/commons.wikimedia.org (documentation). It caches for 10 minutes, but that particular endpoint is very fast even without caching.

No really, don't use it in the extension. You could, and that'd be really cool, but you probably shouldn't.

:-) XTools will never be far from our minds (even if we don't use it...).

Also, possibly markblocked could be part of the same extension. @TBolliger is that something you might know about (adding indicators to blocked users)?

In T180555#3761745, @Samwilson wrote:

Also, possibly markblocked could be part of the same extension. @TBolliger is that something you might know about (adding indicators to blocked users)?

See T172554: Links to blocked/locked user accounts should be visually distinctive

In T180555#3763151, @JJMC89 wrote:

In T180555#3761745, @Samwilson wrote:

Also, possibly markblocked could be part of the same extension. @TBolliger is that something you might know about (adding indicators to blocked users)?

See T172554: Links to blocked/locked user accounts should be visually distinctive

We're helping code review some work by @Huji on T172348: Links to blocked/locked user accounts should have a class indicating so but do not think T172554: Links to blocked/locked user accounts should be visually distinctive should be made the default behavior for users without a larger on-wiki consultation. It's not an active priority for us at the moment, but we're happy to help where appropriate.

I would support this. I've also local a rewritten fork from the Commons version for DeWiki. But there seems not really competent active tech admin anymore. The Commons version is indeed more modern and performant.