At this time, not yet. IPv6 used to work for my ISP at my area months ago (still CGNAT IPv4, but with a proper public IPv6 address), so I got less CAPTCHAs at that time. However, I can't seem to get IPv6 working again after a mass outage happened for my ISP, even with (somewhat) relevant IPv6 settings enabled on my router.
Yes, I think that's a better title (that I failed to think of when thinking about posting the statement here on HN). Unfortunately, I missed the submission editing time window.
- Censorship bypass tools triggering destination server's firewall (suspicious TLS fingerprint or connection characteristics, or bad proxy IP)
- Bad ISP (e.g. one ISP IP address or range of addresses shared by so many users that could create collateral damage if one or more user gone rogue)
- Actual botnet/hidden residential proxy exit node on the same IP/local network (e.g. TV boxes or SDKs embedded inside apps that users are not aware of)
- Strict privacy settings (unlikely to cause 403 straight away), or obscure browsers (also unlikely, but can trigger firewall because of connection fingerprint/characteristics)
Your 4th hypothesis is equivalent, not "other," to mine. But I agree that it could be anything you mentioned, as all of them have crossed my mind as possible reasons why I experience "verifying you are human" and "find the motorcycles / busses / traffic lights" more often on my residential ISP than on my cellular or work ISPs, and the unknown botnet/exit node seems most probable (by far) when considering my own traffic. I never have the 403 problem discussed here, luckily.
Okay, I've figured it out, thanks to the "test distros online" thingy to test version 145 and 148 as I previously mentioned.[0]
From Firefox 148 release notes for developers:[1]
> The overflow, overflow-x, and overflow-y CSS properties can now be used on replaced elements such as images, in the same way that they are used with other elements. Prior to this, replaced elements were always clipped to their bounding container. (Firefox bug 1999100).
reply