“All core systems are now at X.com”, so why opening x.com links in private window redirects to https://twitter.com/x/migrate?tok=, then again to x.com? I just cannot describe how stupid this is.
As others have noticed, it drops an error: “Firefox’s Enhanced Tracking Protection (Strict Mode) is known to cause issues on x.com”. The link has ?mx=2 parameter. I removed it and the page loaded correctly (but half of the viewport was clumped with banners). I tried again in a new private window, but never saw this error again, so this is a bug due to the aforementioned redirect.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
“All core systems are now at X.com”, so why opening
x.comlinks in private window redirects tohttps://twitter.com/x/migrate?tok=, then again tox.com? I just cannot describe how stupid this is.As others have noticed, it drops an error: “Firefox’s Enhanced Tracking Protection (Strict Mode) is known to cause issues on x.com”. The link has
?mx=2parameter. I removed it and the page loaded correctly (but half of the viewport was clumped with banners). I tried again in a new private window, but never saw this error again, so this is a bug due to the aforementioned redirect.