I think it’s more or less as you describe. I think what OP is suggesting would be more like a way to migrate a community. Export everything from [email protected] and import everything to [email protected]
I think something like this exists for Mastodon users, but I’ve never played with it. You could use this to migrate communities from an instance that was going down or otherwise no longer suitable. Even if all old conversations are “frozen” or locked, it would still be useful upon occasion.
Could probably be doable with database fuckery. Make a second community locally with an identical name, then in the backend swap some IDs around and make it think the posts were actually in the new one all along.
Granted, I haven’t looked at the DB structure, so I don’t know how plausible it is. If someone tries it, don’t blame me if the instance breaks, do at your own risk.
But that creates a problem with potential duplicate name, but there is even bigger problem. By export I assume You mean taking ownership so adopting this community into the new server, who decides that? First come first served does not look good in my eyes as a good solution. Since that community is stored as a copy in other instances it should maybe just go into read only mode for eternity
I think it’s more or less as you describe. I think what OP is suggesting would be more like a way to migrate a community. Export everything from [email protected] and import everything to [email protected]
I think something like this exists for Mastodon users, but I’ve never played with it. You could use this to migrate communities from an instance that was going down or otherwise no longer suitable. Even if all old conversations are “frozen” or locked, it would still be useful upon occasion.
Could probably be doable with database fuckery. Make a second community locally with an identical name, then in the backend swap some IDs around and make it think the posts were actually in the new one all along.
Granted, I haven’t looked at the DB structure, so I don’t know how plausible it is. If someone tries it, don’t blame me if the instance breaks, do at your own risk.
But that creates a problem with potential duplicate name, but there is even bigger problem. By export I assume You mean taking ownership so adopting this community into the new server, who decides that? First come first served does not look good in my eyes as a good solution. Since that community is stored as a copy in other instances it should maybe just go into read only mode for eternity