Seems like @mozilla is doing something right

100rabh™@mastodon.social to Firefox@lemmy.ml – 614 points –

Seems like @firefox @mozilla is doing something right

27

This issue comes from the fact that even though the domain is now changed to x.com, it still tries to load content from twitter.com which Firefox thinks is social media tracking because it's coming from a different domain than the one you're on.

It's a hilarious and dumb oversight with this change.

Web developer here: This is 100% sloppy code on the part of Twitter. Like... I can't believe the amount of incompetence required.

I can, didn’t all the better developers leave when Elon took over?

One of the managers in my org used to work there, and lost his job post-takeover. Apparently most that were left were on L1B visas, so had no opportunity to move elsewhere. His theory was that Elon knew exactly what he was doing, because he now has a team of engineers in their late twenties and early thirties that'll basically do whatever he wants, or risk uprooting their families back to their home country.

They're probably still great engineers, but when you're doing the job of multiple teams, or things have zero coverage, shit is going to slip.

My headcanon is that they are still there, forced to watch as Musk personally "improves" their code.

Totally. I got the error message yesterday and didn't try once to circumvent it. Twitter is that important to me

1 more...

I saw this today. A big red “we see there’s a problem with our site but fuck you we’re not fixing it”

Classic feature not a bug

For real. No longer compatible with whatever bullshit Elon is pulling today.

@the100rabh @firefox @mozilla I get the same screen only when I enter X. The solution is not to enter X 😎

Looks like Elon finally forces x down everyone's throat and every twitter.com link redirects to x.com. (Funny enough I tried Firefox Nighty and there is no redirect so maybe this is random based on UA) Also I'm not 100% sure but enhanced tracking protection probably breaks x.com because there are still API calls to twitter.com under the hood, since those are different domains it just gets blocked. Solution is either twitter fixes their shitty code or Mozilla adds exception.

Well my Nitter redirect on Android Mull Browser still works, which is all I barely care about.

Something on Firefox keeps blocking x embeds as well, asking me if I want to load them instead. I love it!

That's the Privacy Badger. I love using it aswell.

I know those issues, I like those issues, let me browse your shit site with those issues