This is a text automatically translated from Italian. If you appreciate our work and if you like reading it in your language, consider a donation to allow us to continue doing it and improving it.
With a post (on X 😅) Firefox lets us know that they have solved the problem. There is no need for any updates, everything should work now.
As of this morning it seems that twitter.com no longer exists and everything is automatically redirected to x.com. This change, however, is not entirely painless and had already been tried, with several problems, already a month ago.
This time it seems to have more or less worked but anyone who is using Firefox with the Anti-tracking protection activated in advanced mode, that is, the one recommended by us, he will have noticed that Twitter is broken and no longer works!
Twitter redirect to x.com broke Firefox
In fact, if you have Firefox and try to go up twitter.com or up x.com where however you are necessarily redirected you will see an error message: "Firefox's Enhanced Tracking Protection (Strict Mode) is known to cause issues on x.com“.
The positive news is that the Mozilla team is already working to understand what happened and to try to resolve the problem. Ironically the only message from Mozilla that we found about this problem is on x.com so if you use Firefox you can't see it 😂. On Mozilla's Mastodon accountAt the moment, nothing appears.
Waiting for the bux fixing
In the meantime, if you have Mozilla and need to use Twitter/X, the only method for now is disable advanced protection.
You can therefore decide whether to deactivate advanced protection everywhere and only put normal protection (we do not recommend doing this, however) or Temporarily disable protection entirely on Twitter only. To do this you can go to x.com, press on the shield next to the URL and disable advanced protection only on that site.
If you followed our suggestions you will still have too uBlock Origin installed so you will not be completely discovered, then when the problem is fixed you can reactivate it.
When we know that the bug will be fixed we will report it to you in this article.
Currently the problem is present both on Firefox 126 and on older ones, in fact we have also been able to see it on LibreWolf version 125.
What can I say, it's probably an excellent opportunity to try Mastodon if you haven't already done so!
•This tag @loyal alternatives is used to automatically send this post to Feddit and allow anyone on the fediverse to comment on it.
Join communities
If you have found errors in the article you can report them by clicking here, Thank you!