I’m just curious, since I tend to get attached to my accounts but I also like having access to all information so I don’t want to use a defederated instance. If, say, kbin got overrun by bad actors and was defederated by everyone else, is the only option to jump ship? Unfortunately I don’t have the capability to selfhost or I would to avoid such problems.
What are your contingency plans if such a thing occurs?
If it gets defederated by instances I care about, then i’d migrate my account.
One of the things the Lemmy devs community need to work on is migration tools. Mastodon, for instance, has tools to migrate your account to another instance that would carry your followings and such. I’d expect something that at least takes the communities/magazines I’m subscribed to with me.
As I do not use kbin, i don’t know if it has similar tools, but in any case, my response is the same.
Edit: there is a difference in migrating a microblogging account and migrating a threadiverse account that i’d care about, for instance. In microblogging, past posts do not care as much, it’s a more ephimeral thing -I have autodelete my posts set on, for example-. On the other hand in the threadiverse, there may be more timeless meaningful posts that I may care about not being lost and want to take with me if I migrate instances. Because of that, I think migration in the threadiverse is more complex and i’d like the migration tools to reflect that too.
@brunox unfortunately it doesn’t have similar tools as of yet but I imagine they’ll be worked on eventually!
Lemmy, and I guess kbin too as I understand it’s newer, are still in a very early stage of development (Lemmy is now in version 0.17 in my instance). The bump in users may bring interested to developers and there would probably be an acceleration. No idea where the priorities in development are right now though.
Lemmy devs made some sort of post where they said their priorities right now are stability and bug fixes.