[ayewo]

On a related note, starting today, I noticed that x.com (fka Twitter.com) is no longer working in Firefox.

I get the following error:

> Something went wrong, but don’t fret — let’s give it another shot.

> Firefox’s Enhanced Tracking Protection (Strict Mode) is known to cause issues on x.com

[jraph]

Only very remotely related if you squint hard enough though, no?

(sorry for sounding a bit rude, not my intention, I would like to read friendly but I can't find a nice way to point this out and still want to do it - it's just that I wouldn't find it very enjoyable if all HNers started commenting about general / random issues they encountered on some product P in a submission about a specific/historical issue in P - I'm sure we all encountered some issue while using Firefox / any browser at least once, especially with Twitter which screams buggy to me as a distant observer, I remember consistently having to try and refresh pages several times a few years ago to display a 140 character tweet - awful experience)

[ayewo]

Well, x.com was working completely fine on my version of Firefox until yesterday so it’s an intentional breakage for Firefox users.

My comment was more of a PSA to other Firefox users who are likely the ones also reading about the bug fix here, so it’s definitely on-topic. I guess you disagree which is fine.

If they don’t fix it, I have to either switch to a different browser or device (mobile) to visit x.com.

The good news is I’ll spend less time there.

[pyb]

Same here.

This also happened about a week ago, but was reverted/fixed within a few hours. So, I'm hoping Twitter will fix this.