Hi there,

I went through the documentation of GoToSocial and there are some pieces of information which confuse me. For example on the Deployment considerations, they state, that once you hosted a particular Fediverse service on your domain, you cannot switch to another technology. Further down in this article in the “Domain name” section it even gives me the impression that if you switch technologies on the same domain, this will in fact cause issues in the whole Fediverse.

Two questions came up when reading through this:

  • Is the ActivityPub protocol and the technologies that depend on it that fragile? Switching technologies on the same Domain would be something I would have just done without a further thought until I find the technology I want to use for years (and which I might still switch out to another one many years in the future).
  • It is not clear from the documentation if you can get around this by hosting the service I want to try under service1.example.com instead of example.com. The documentation states, that you can host your users under user@service1.example.com, but the API services still under example.com. This will not solve the root issue, right?

Getting a new domain for each Activitypub service I might try to implement and test / use does not really sound great to me. Maybe I just did not understand all of that properly and there is no issue?

  • tofu
    link
    fedilink
    English
    arrow-up
    20
    ·
    1 day ago

    Yes it is, and as the other comment mentioned, using subdomains works perfectly fine.

    Theoretically, a migration can work, but it’s just not implemented. I think there’s keys for each account on your instance and they would be other keys on your new software but remote instances would not accept those new keys so you would need to migrate your old keys and there’s no feature to do that.

    E.g. you can switch from mastodon to a fork and keep your database and I’ve heard PieFed is working on a migration feature from Lemmy.