from what I heard, it won’t me easy, but it would be one real stress test for federation. hopefully, we don’t have to block them out while they’re migrating. I wonder if perhaps it would be better for them to just start over with a clean slate.
from what I heard, it won’t me easy, but it would be one real stress test for federation. hopefully, we don’t have to block them out while they’re migrating. I wonder if perhaps it would be better for them to just start over with a clean slate.
@cendawanita not all is well with firefish.
I really hope we do not see a repeat of that phoenix ➡️ firebird ➡️ firefox saga that mozilla had.
>If a server moved their domain they had to have a way to broadcast the name change to all the other instances.
even if lemmy had a way to do this, doing it for all the users at lemmy.ml would create a large load of federated network traffic between instances, and at the level of a single instance it would cause a lot of database changes (I’ve heard that the sql schema for lemmy isn’t very optimized).
also, as activitypub doesn’t prioritize synchronization (unlike git and matrix), there could be a lot of desynchronized state, with the name change of users reaching some instance but not others.
it would be interesting if lemmy.ml really went the clean slate way (and I think the original intention of the devs in running that instance was just to test their code, not to have it become a “flagship” instance), it would sure showcase a valuable lesson in the fediverse…that you shouldn’t rely too much on big instances (there is no huge facebook/twitter/reddit-like thing here).