They might be thinking of the problem where you can’t change the domain of an instance, you have to start a whole new one under the new domain. And if you lose a domain, someone else can start an instance and receive your federation traffic.
But changing away from domain names entirely doesn’t solve those problems.
I think this could be solved with a migration window though, and a proper migration path in code. You spin up a new instance, clone your data. Then on old instance it sends a .well-known redirect message, or 301s for everything. Then receiving servers whenthey get that know to update all of their references. You keep it up for however long you think you should for all of the other severs to update.
I think even then that’s a solvable problem though. A unique hash of your server so if you move and start refederating the same process could happen. It’d require more work on the individual instance admin, but could be done
What problem would be solved by doing that?
They might be thinking of the problem where you can’t change the domain of an instance, you have to start a whole new one under the new domain. And if you lose a domain, someone else can start an instance and receive your federation traffic.
But changing away from domain names entirely doesn’t solve those problems.
I think this could be solved with a migration window though, and a proper migration path in code. You spin up a new instance, clone your data. Then on old instance it sends a .well-known redirect message, or 301s for everything. Then receiving servers whenthey get that know to update all of their references. You keep it up for however long you think you should for all of the other severs to update.
For moves, yes. If you lose the domain you can’t do that.
I think even then that’s a solvable problem though. A unique hash of your server so if you move and start refederating the same process could happen. It’d require more work on the individual instance admin, but could be done