@Bobetap @satori Starting new instance under same domain should be almost a noop, but migration from mastodon that allows to retain access to old content would require to map data to different persistence layout and either implement custom authentication to work with old hashes, or perform an instance-wide password reset. To also allow old content to remain federatable, an id correspondence will have to be stored somewhere during migration and a simple translation service using that information added to the reverse proxy. All could take several weeks to implement and test out at leisurely pace, but probably worst of all, it will also remove the justification for more gibs.