• andyburke
      link
      fedilink
      281 year ago

      honestly the lamest and funniest bit.

      Perfectly ties the whole thing up in a bow: can’t even technically manage a domain name change.

      • @[email protected]
        link
        fedilink
        English
        201 year ago

        Willing to bet some motherfucker has hardcoded twitter domain on the backend in one (or many) link generation process(es) on the basis “it’s not like they’re going to change the name” and now it borks occasionally if they use x.com

        • @[email protected]
          link
          fedilink
          111 year ago

          For some reason I’m now thinking about a video game called x.com where you have to fight aliens who have infiltrated and taken over a major social media site and are trying to TAKE OVER THE WORLD Wide Web.
          (Actually, that kinda sounds like a sequal to x-bill.)

          • andyburke
            link
            fedilink
            81 year ago

            of course, switching it back might not be so easy… 😂

            • @[email protected]
              link
              fedilink
              English
              71 year ago

              Oh god. You’ve probably hit the nail on the head both directions all the same, how many methods/classes/variables are going to have twitter in the name somewhere. Or random bash scripts that pass an arg to something else from a job scheduler. This shit gives me the heebeejeebees just thinking about it.

    • Balthazar
      link
      fedilink
      1
      edit-2
      1 year ago

      Oh, shit. x.com = twitter, it’s not Xcom (the game series) xD | That took me waaay to long to realise lol