• fuckwit_mcbumcrumble@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      9 months ago

      I thought it already happened when I first saw that post. I’m surprised they didn’t try to figure something else out and kill it sooner.

      • TheEntity@kbin.social
        link
        fedilink
        arrow-up
        0
        ·
        9 months ago

        I don’t think they could do anything about it. As far as I know, Mastodon doesn’t support any kind of instance renaming, so the hostname is one thing you cannot change. You can only spin up a completely new instance.

    • 🇰 🌀 🇱 🇦 🇳 🇦 🇰 ℹ️@yiffit.net
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      9 months ago

      Who’s bright idea was it to integrate the domain name itself directly into the software such that changing the domain name totally fucks up the whole thing? Is there actually a good reason for this to not work like any other website where the domain name is just an address and changing it doesn’t actually have any effect other than requiring users to type in or bookmark a different URL?

      • TheEntity@kbin.social
        link
        fedilink
        arrow-up
        0
        ·
        9 months ago

        Federation combined with keeping the historical federated data consistent is certainly a bitch. We can’t have it all. It could be like email that only handles delivery at any point in time and history is purely local, but Mastodon specifically keeps the federated data public. Propagating the change on the historical data to the federated instances would be nearly impossible. I don’t see how it could have been done better without sacrificing something else.