[eqvinox]

> […] you can see it all without needing to be logged in.

No, you can't, Twitter is degenerating further:

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

  [Try Again]

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

(Weird how no other website has issues like this…)

[joveian]

This just means that there are exceptions for twitter.com that haven't been switched to x.com. I use uBlock Origin with all scripts and third party resources blocked by default and got this page when they switched to x.com, but it works once you unblock the same stuff on x.com that was unblocked on twitter.com.

The exception is that some accounts still require login to read. I'm not sure why but I'm guessing that it might be a per account setting that won't be set by accounts that haven't logged in for a long time (I don't have an acount to check). Actually, worble and ploum's comments below would explain what I see, I usually don't try to check the same content twice (or anything all that often) so I wouldn't notice if it sometimes works and sometimes doesn't.

[VancouverMan]

> (Weird how no other website has issues like this…)

The Firefox 126 preferences UI for the "Strict" setting shows this warning:

"Stronger protection, but may cause some sites or content to break."

When the panel for that setting is expanded, it shows an additional warning:

"Heads up! This setting may cause some websites to not display content or work correctly. If a site seems broken, you may want to turn off tracking protection for that site to load all content."

Presumably such problems are not unexpected or unheard of if two warnings are deemed necessary for that setting.

[eqvinox]

Slight problem: you're assuming I use Firefox and have that setting on "Strict". Only half of that assumption is correct: I use Firefox. But the setting is on "Standard"…

(I'm not a web person, so I'll save my speculation on what is breaking there, but Twitter is the only webpage I experience as broken. It is absolutely possible I mucked around with some setting 5 years ago and completely forgot about it. Or Twitter is doing weird things. Probably a combination of both.)

[timeon]

There is also mention why those specific sites are broken:

> Firefox blocks the following:

> Social media trackers

> Cross-site cookies in all windows

> Tracking content in all windows

> Cryptominers

> Known and suspected fingerprinters

[hakanderyal]

So that's why I couldn't access Twitter while using FF. Interesting. That notice wasn't there before.