keenmaster486 wrote on 2026-08-25, 19:58:
But I'm just using Chromium on Linux. Why would that user agent be blocked?
I suspect a heuristic match: Either a confirmed bot is using the same user agent string as Chromium on Linux, or they share a common substring.
Many years ago I recall Trillian (a network independent chat client) using a re-engineered "OSCAR" AOL messenger protocol. Trillian argued they were not changing the relationship between AOL customer and AOL service. AOL argued Trillian was providing unauthorised access. CNET noted Trillian enabled customers to circumvent curated banner adverts or some such. Trillian countered with evidence that AOL had a free basic "TOC" protocol so customers could chat without adverts so no loss. AOL pushed back suggesting that OSCAR provided customers with extra protection and Trillian hacks into their system. Trillian denied hacking, insisted AOL customers retained full control of their own usernames and passwords, and Trillian was was protecting AOL customers by adding end-to-end Blowfish encryption. The two sides went to war with each few hours AOL modifying the protocol to break Trillian connections, Trillian modifying their version to reactivate connections. CNET provided coverage of what was an amusing cat-and-mouse act, with occasionally both sides making mistakes such as releasing an update that knocked their customers offline.
And, it feels relevant here today because we are witnessing another cat-and-mouse act where one side is trying to gain access and another side is trying to block access - and the ordinary users are the ones bruised in the crossfire. Some sites block the IP range of my ISP, and maybe that is because some other ISP customer is running bots - who knows but it makes me seek out lesser known VPNs as the big ones are blocked also.
I think the eventual outcome may have already been explored in the Matrix or other soon-to-be non-fiction.
Desktop timeline [ MOS 7501 → 68030 → x86(P5/MMX) → x86(K6-2) → x86(K7*) → PPC(G3*) → x86-64(K8) → x86-64(Xeon) → x86-64(i7) ] * lost