So I want to leave .social for a better server that doesn't federate with Threads, but the ones on the fedipact website either actually do federate with Threads anyway (looking at you mas.to) or they're invite-only. :(
@trumpet Something that could work is setting up an alternative instance—one federating with Threads and the other not—so they run as separate entities but are run under the same administration as mas.to right now. There might be a small overhead, but with the same total number of users a lot of the costs should be similar. It may be possible to migrate people at a database level so they don't have to do it themselves. But there are already plenty of instances that federate with Threads.