Administrator and checkuser on enwiki. Mostly here to complain. User has not been awarded any badgers. Profile picture attribution: Gunnar Creutz via Wikimedia Commons (https://commons.wikimedia.org/wiki/File:Tam_gr%C3%A4vling_i_Plantis_2298.jpg).
May 31 2023
I agree that setting tenure limits for data collection is a bad idea; "aged" sock accounts, including ones with high edit counts, are quite common, and implementing thresholds like this would essentially be inviting people to stay under the radar for exactly X edits over Y timespan, by which point they can more or less engage in whatever socking shenanigans they want as long as they do it with Chrome.
May 1 2023
I'm not sure who (if anyone) at the WMF is currently responsible for handling this task, but given the time-sensitivity and level of concern among CUs here I'd be grateful if we could get some sort of acknowledgement that UA deprecation mitigation is still being pursued, and ideally establish a timeline for when a fix might be available.
Apr 30 2023
I'm not sure we actually have grounds to dismiss this as a potential (partial) solution. https://www.chromium.org/updates/ua-reduction/#alternative-high-entropy-client-hints indicates that Sec-CH-UA-* should indeed continue to send us at least some of what we need, albeit potentially incomplete or deliberately unhelpful (see https://wicg.github.io/ua-client-hints/#grease). I just grabbed the latest Chrome dev version and tested this with https://user-agent-client-hints.glitch.me/headers , and it would seem that we can indeed use these headers to grab substantially more information (aside from the "not a brand" stuff, the information appears to be accurate):
I'll also add that I'm a bit surprised that this task, which exists because functionaries have been widely concerned about UA fingerprint reduction for several years (see e.g. T242825#6316133) seems to have been more or less scrapped without any additional functionary consultation on the basis of assumptions about CU workflows and political desirability perceptions. Having to collect potentially-sensitive data from users is not ideal, and might not "look great" in light of the foundations privacy-conscious messaging, but in light of the fact that we simply have no working alternative to CheckUser, making an already-blunt tool even less functional does not seem like a good way forward.
Mar 15 2022
Of course you could also take a slightly wider view and say that a list of global blocks on Wikimedia wikis provides a list of valid proxies to vandalize non-Wikimedia wikis. I'm not sure this is a reasonable concern.
This is not a concern with the type of proxy we're blocking and the way we're blocking it -- that's the best I can say publicly. And more broadly speaking, publicised lists of proxy exit IPs are likely to be substantially more useful to defenders than to attackers anyway.
Feb 10 2022
It's intermittent for me, but I can reproduce.
Oct 25 2021
One of my primary communication concerns is the way that layered blocks are currently handled. We want to be able to block individual exits with highly informative block messages. We can do that (and are doing that), the issue is that if they are on an underlying range that is already blocked for one reason or another, (enwiki) users see the following, which is a transclusion of https://en.wikipedia.org/wiki/MediaWiki:Blockedtext-composite.
Aug 2 2021
Jul 30 2021
Feb 22 2021
@Srdjan and I did some testing (see https://bs.wikipedia.org/wiki/Posebno:Doprinos/Blablubbs) -- I can move pages fine both with and without the autoreview flag, so assigned user groups don't seem to be the cause.
Feb 21 2021
@ppelberg I've given it a couple days to see that it's working reliably, and indeed it is. I think this can be closed -- thanks for the fix :).
Feb 3 2021
Well, sorry for the spam but it's broken again. I'll just report back once it's been working consistently for a couple days.
Feb 2 2021
Update 2: Has since dropped in and out a couple times, but has been functioning consistently today -- I assume the fix was pushed and is working. @ppelberg Thanks for fixing this so quickly, I think the issue can be closed.
Jan 29 2021
Update: Now started working again.
Jan 28 2021
Will do @ppelberg; thanks for the quick response!
Jan 27 2021
Indeed, that was the edit -- I had enabled enterprisey's reply-link for a while and just uncommented the line so I could just wait and see when it would start working again. Some time after uncommenting, it actually worked for a bit -- see e.g. the tags here https://en.wikipedia.org/w/index.php?title=User_talk:Blablubbs&diff=prev&oldid=1002953117. I'll keep you up to date in case it unbreaks again.
The patch appears to have fixed the issue for a short while, but it looks like it broke again - at least for me.