Tell HN: Twitter/X is inaccessible to all Firefox users by default

Re:Tell HN: Twitter/X is inaccessible to all Firefox users b... by yareal on Wednesday May 15, 2024 @10:18AM (#40367287)

This seems to be working as designed, a website is loading cross origin material and not setting up the proper systems in advance. Twitter shouldn't get a pass on doing something unusual and suspicious just because.

Serve the images from the same domain.

I know Twitter probably fired the people who knew this entirely predictable outcome was likely, but like, they should have seen this coming.

[ Parent | on HN ]

Re:Tell HN: Twitter/X is inaccessible to all Firefox users b... by litzaghitzalau on Wednesday May 15, 2024 @05:41PM (#40372737)

You're all just a bunch of pathetic haters. If you look carefully, you'll see that abs.twimg is responding with "access-control-allow-origin: *".

The reason you see CORS errors in the Network tab in Firefox when Enhanced Tracking is enabled, is because Firefox sux and can't render a correct error message. They simply have manual hardcoded lists for blacklisting, just because they have it (and probably they implement it by faking a CORS failure).

[ Parent | on HN ]

Re:Tell HN: Twitter/X is inaccessible to all Firefox users b... by yareal on Wednesday May 15, 2024 @07:37PM (#40373635)

Do you work on Twitter? I'm confused why you would react so strongly and angrily out the gate.

[ Parent | on HN ]

Re:Tell HN: Twitter/X is inaccessible to all Firefox users b... by gamer191 on Thursday May 16, 2024 @02:38AM (#40375793)

It doesn't say anything about CORS in the networking tab: https://i.imgur.com/yeH6bGi.png

It correctly identifies that Twitter is trying to load a tracking site, which Firefox blocks by default (with an allowlist). Instead of hating on Firefox, hate on Chrome and other browser vendors that don't go to the effort of maintaining a blocklist to protect their customers privacy (or implementing support for an existing blocklist, in the case of Brave)

[ Parent | on HN ]