• P03 Locke@lemmy.dbzer0.comEnglish
    57·
    1 year ago

    That seems like an ActivityPub problem, not a problem with the admin who lost the domain. Perhaps somebody should fix dumbass design flaws to the protocol.

    Federations won’t survive with obvious flaws like that. It needs resilienacy.

    • Max-P@lemmy.max-p.meEnglish
      17·
      1 year ago

      You’ll have to go complain directly to the W3C for that. The situation is Lemmy may fix it with some custom protocol extensions, but then it’ll still break every other piece of software that follows the spec like Mastodon, Kbin and others.

      It’s like adding a 6xx status to HTTP. You technically can, but expect every standard compliant clients to be confused and bail on it.

      You can’t just change domains with emails either and have everything seemlessly migrate over. Not losing a domain is not a completely unreasonable assumption to make.

      Thankfully the users and communities aren’t lost, it’s just that people outside of fmhy will have to resubscribe to the communities on the new domain.

      • Zetaphor@zemmy.ccEnglish
        6·
        1 year ago

        A lot of armchair developers in here who think there is an easy solution to distributed identity

        • Max-P@lemmy.max-p.meEnglish
          4·
          1 year ago

          There’s definitely better ways to handle this, like, the ID could be a public key or something. Chances of RSA/EC key conflicts is basically nonexistent or we wouldn’t use them.

          But it’s the W3C, of course they assume URLs can and will be permanent. Your domain being seized is not something typical companies and organizations face. It’s something you expect to happen to a site hosting piracy and other illegal content, which FMHY is somewhat borderline with its piracy guides.

          ActivityPub is not designed to be any sort of censorship resistant for sites that move addresses and servers frequently.