You can update the warning to the current situation, telling the users that they can continue using the pod for a few more months, or switch to another pod earlier if they wish. It’s not forcing anybody to stay longer than they want, but after you wrote that you plan to keep the server running for a while anyway, why not also allow the users to still use it? It would be an offer to the users, not a force.
Keeping the pod running for a few more weeks/months wont change much about when migration will be possible, but it probably changes how well the user experience with it will be and how big the disruption for the users will be. It allows us to polish a few more things, then start testing with a few users, then probably fix a few more things, test again, and so on. Migrating all 1000 users on the day the pod shuts down is not really realistic and if something goes wrong there is no time left to fix anything, not a great experience for users. And if the migration isn’t finished enough at all then they don’t have anything?
If they already created a new account, they can either manually migrate to that, or use the migration in whatever state it is at the moment, or just keep this new account and continue using the old account until the more polished migration/import is done and then import their old account a few weeks/months later. The users are free to do whatever they want.
Same, but I thought if you plan to keep the server running, both to still allow active users to still export their data, and also to close some of the inactive accounts every day, why not allow users still to use it to also read/write posts. My initial thought were, that it’s planned to hard pull the plug and shut it down, also to save resources/cost, but if the server stays there for a few months anyway, why not keep it available to the remaining active users?
If users already created accounts, they probably already migrated some contacts manually, either that’s enough until they can import their profile, or they go back to the old account for some weeks. Or again, they are free to use the migration in whatever state the migration is. Keeping the pod available won’t change anything about the current state of the migration/import. It just gives more options to the users, and gives us the possibility to fix bugs as they are found and then import some users with an improved/fixed version of the code, instead of being forced to import 1000 users at once with the same probably not 100% stable code.
The migration was designed to never break federation for new entities, even if migration/import completely fails, so the new account will always work as a new account. But it can lead to inconsistency and broken UX, one user thinking they share with each other, but the other user/pod not knowing about that, or as said, I think there was a problem with existing private-messages with Jonne, so they were migrated on one pod, but not imported on the other (or something like that), so one user could think they can answer on that, but it never is received on the other pod, because they don’t know about that conversation (but here again, new conversations will always work, it’s only existing/migrated stuff that maybe breaks) … so stuff like that, inconsistency and bad UX for existing/migrated stuff.
Photos are also still an open topic, Thorsten added some code to import the photos in the new pod (but I didn’t have a full look at it yet), but other pods still have the old URLs, so as soon as framasphere would go down completely all posts with images will look broken on all other pods. To fix that something would need to be added to 0.7.x (so another minor release there, or we release it with 0.8.x, but then pods would need to upgrade to that before running the majority of the migrations), so they also change the URLs of the images to the new target.
So stuff like that, where a few more weeks/months could drastically improve the experience for the users. Again, I’m not forcing anybody to not migrate right now, but I feel for most users it would be better to delay the migration a few weeks/months. If we force everybody to migrate right now there will be broken stuff (hopefully nothing catastrophic, but there will be broken stuff). So that’s why I think more options for the active users would be a better solution, so users can choose when to migrate, spread over a few weeks/months with the possibility to fix/improve stuff in between.