Federation Design Plan

(#1093) Feature Under consideration federation

Thread

Comment by @Haplo164
RexSystem 1 vote originally by @Haplo164 on GitHub 1 reply
Pretty good write up, I think it's important to clearly know where chat data is stored and having it on the Guild Instance is probably best. I also think there should be a method to signal a domain change. Matrix doesn't have a way to change a servers domain so you basically have to start a new server, and that really sucks. With encryption keys you should be able to signal that a name change has taken place and update all records to reflect that. edit: it would also be nice to allow user transfers, it might be best to limit transfers to 2 online instances where the users current Home Instance initiates the transfer and the destination Instance confirms, this would move all private chats to the new Home Instance and updates the messages associated with the transferred user to point the the new Home Instance. The old Home Instance should maintain the old username as unusable for a time and respond to any requests involving the old user with a "Transferred" status and redirect to the user on their new Home Instance.
Comment by @Haplo164
RexSystem 1 vote edited originally by @Haplo164 on GitHub
I've been self hosting a Nextcloud instance since it was Owncloud, and I've recently redeployed a few web apps so I have really started thinking about long term maintenance. Federation is a pretty good vector to fix issues that can build up over time, especially if you need to change domains, or shut down. It can ensure that a community can live on with minimal fuss and is a direct counter to vendor lock in, which is probably why large SaaS providers don't implement it. I know @DamitusThyYeetus123 was also mentioning Federation so maybe we can really start building a discussion around Federation since it's clearly on our minds. ref #1080