5 ms·

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

Twitter has started changing over its URLs to X.com as the default URL now. However, this has left Firefox unable to access the site by default. You will instead get a message about "Something went wrong, but don’t fret — let’s give it another shot." This seems to be due to the manual allowlists FF has as part of the "Enhanced Tracking Protection" feature. It doesn't know that X.com should have access to the Twitter image distribution URLs and other non X.com URLs, so the page load fails. X access can be restored by turning off Enhanced Tracking Protection. The Twitter engineering lead is asking for anyone who has a direct line to FF staff: https://x.com/cambridgemike/status/1790615764736913557

raverbashing 2y ago
I'm using it on FF right now. I don't see the issue with any url (X or twitter)
pestatije 2y ago
if it aint broke...
deleted 2y ago
[deleted]
postingawayonhn 2y ago
I'm getting the same error in Edge.
tux2bsd 2y ago
Thank you for the work around. I'm one of those affected, it has been busted about 24 hours too...
yareal 2y ago
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.
- litzaghitzalau 2y ago
  [flagged]
  - yareal 2y ago
    Do you work on Twitter? I'm confused why you would react so strongly and angrily out the gate.
    - tux2bsd 2y ago
      [dead]
  - gamer191 2y ago
    It doesn't say anything about CORS in the networking tab: https://i.imgur.com/yeH6bGi.png 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)
solardev 2y ago
> The Twitter engineering lead is asking for anyone who has a direct line to FF staff lol "Hey browser vendor, our owner woke up one day and decided to change our name for the lulz and then fired most of the company... now we don't know what to do. Halp?"
slimebot80 2y ago
This is a test of your browsers protections, and FF is shining.

raverbashing 2y ago

I'm using it on FF right now. I don't see the issue with any url (X or twitter)

pestatije 2y ago

if it aint broke...

deleted 2y ago

[deleted]

postingawayonhn 2y ago

I'm getting the same error in Edge.

tux2bsd 2y ago

Thank you for the work around. I'm one of those affected, it has been busted about 24 hours too...

yareal 2y ago

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.

litzaghitzalau 2y ago
[flagged]
- yareal 2y ago
  Do you work on Twitter? I'm confused why you would react so strongly and angrily out the gate.
  - tux2bsd 2y ago
    [dead]
- gamer191 2y ago
  It doesn't say anything about CORS in the networking tab: https://i.imgur.com/yeH6bGi.png 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)

solardev 2y ago

> The Twitter engineering lead is asking for anyone who has a direct line to FF staff lol "Hey browser vendor, our owner woke up one day and decided to change our name for the lulz and then fired most of the company... now we don't know what to do. Halp?"

slimebot80 2y ago

This is a test of your browsers protections, and FF is shining.