• Simon Müller
    link
    fedilink
    arrow-up
    205
    arrow-down
    1
    ·
    6 months ago

    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.

    • Lucidlethargy@sh.itjust.works
      link
      fedilink
      arrow-up
      47
      arrow-down
      1
      ·
      edit-2
      6 months ago

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

        • EnderMB@lemmy.world
          link
          fedilink
          arrow-up
          8
          ·
          6 months ago

          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.

        • AeonFelis@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          6 months ago

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

    • Hadriscus@lemm.ee
      link
      fedilink
      arrow-up
      5
      ·
      6 months ago

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