Link: https://www.theregister.com/2026/02/28/open_source_opinion/

note to mods: this is an opinion article, but it contains a lot of newsworthy statistics and prose on Maven (Java ecosystem package repository) being used as a CDN

Throttling efforts led to "brownouts" via 429 errors

Does this mean for the (ab)users, or for the repo? If it's for the bandwidth hogs, then the brownouts are properly a good thing, as it'll force people to pay attention to these otherwise unmonitored systems.

Also, if it makes the upstream service seem flaky and unreliable, it could convince users to set up the proper caching proxy just for self-interested availability reasons.

I can see some companies happily paying for access, as they'll think it's easier than paying someone internally to manage a proxy/mirror, especially as on-prem is unfashionable lately.

i'd guess it's for everyone

for context, the full sentence is "Throttling efforts led to “brownouts” via 429 errors, but patterns mutated, forcing a "Whack-a-Mole" game, especially since most consumption is headless and unnoticed." so they tried to use brownouts to control it but it couldn' t stop them

Yeah ok, I guess that's what's meant.

I'd be interested to know how the patterns changed - perhaps requests moved to IPv6 which made grouping request origins harder, or maybe too many unconnected users were coming from a single IP and getting false positives (leading to bad UX and support requests).