Edit history

I can't move my existing community to Fluxer today without knowing whether I will be able to move it to a self-hosted server in the future if I choose to. This being uncertain makes Fluxer no different from Stoat or Discord for all practical purposes to me today. If this is confirmed to work as expected, I would be more likely to migrate a community to the Fluxer.app instance today, knowing there is an off-ramp in the future if necessary.

I think it would be good to confirm:

1. That community migrations between servers will be possible.
2. That such migrations will be 100% seamless for the users of a community.

I don't know how many federation details are confirmed yet, but my hope is that:

1. Fluxer has a unified view with all communities in the sidebar,
2. Communities in the sidebar have a little indicator/icon next to the community picture that shows which server they're hosted on, and
3. When a server migration occurs, literally the only difference users should ideally notice is that icon changing (and also, perhaps their limits in that community being changed because the server has premium features or whatever).

And in the opposite direction...

1. I think a lot of self-hosters may appreciate knowing that their communities can be moved to Fluxer.app or another server if the self-hosted server becomes too unmanageable for them for some reason.
2. I think a lot of community admins would be more likely to choose to host their communities on instances other than Fluxer.app, knowing they are not 100% tied to that server operator.

In the 2nd case, I think it is an acceptable risk (at least for now) that if the self-hosted server completely and suddenly disappears then the community is lost. On Mastodon this is similar with user accounts, but generally large public servers will responsibly announce a shutdown and give users a transition period. I think not accepting this risk would probably make the process too complicated.