The app that synchronizes multiple lemmy accounts so you can migrate and keep backup accounts across instances, it's opensource and free, currently working in android and windows.
It's in homologation now and anyone can test, any feedbacks are welcome as always.
This unsubscribed me from twenty+ communities on all of my instances. It first tried to subscribe all of my accounts to all of the communities of my largest instance, which is what I wanted it to do. One instance failed to sub to 20+ communities, which was fine, as it was a smaller instance.
Ten minutes later, however, I got a notification that it had unsubscribed all of my other instances from those communities as well. It took me about an hour to figure out most of the ones that had been lost, and even now I think I'm missing a few.
Please add a logging functionality, so that even if something like that would happen in the future because of some special case bug, it would still be possible to figure out which subscriptions were removed.
Hit "sync" and watched them sync. Three of these instances had almost the same number of communities (around 120), but one had none whatsoever. It took two or three minutes for that instance (basedcount) to sync all of the communities, and in the end, it wasn't able to subscribe to about 20 of them for some reason. (maybe because nobody had ever gone to/searched for those communities from that instance before - I've heard this can lead to access problems, but you'd probably know more about that than I would)
About five minutes later, I got couple of notifications saying that 6(-ish) communities had been synced and that 18(-ish) had been unsubscribed across my instances. This confused me, so I checked my instance list and saw that all three of my instances with around 120 communities now had around 95.
I disabled notifications because they were starting to feel spammy.
I looked at the notification again and realized what had actually happened. I immediately uninstalled the program and resubscribed to as many communities as I could on lemm.ee, my main account.
Awesome to hear. It has already been useful for me, just so I could move my subscriptions to another instance, because the one I'm on has been under fire lately.
My company blocks lemmy.zip on WiFi, but lets lemmy.world through. So I tried to be on something other than lemmy.world, but still use it about half the time.
This is REALLY cool and helpful. I just tried it with the 3 accounts I have and it worked flawlessly.
Only suggestion would be to have the app check a servers defederated list and disregard any communities that you cannot subscribe too. This would prevent a lot of errors that happen when going through the sync. This is pretty minor as the app does seem to skip the community after the error but I suspect it would be a little faster if it just rejectected the community via internal software. Some users who are not aware of defederated communities may get confused by the errors as well.
Maybe this isn't very realistic? If it isn't, never mind. :)
I'm thinking about how to get rid of those errors, this might the solution but I think there isn't a way to check the list of defederated instances, one thing I'll implement soon is to expire synchronization tries after x days so the list won't grow forever
How does this handle cases where no subscribers from an instance have subscribed to an external community yet? Other migration tools I have used require these to be added manually. Does yours automate this process?
Didn't get a chance to look at how your app works under the hood, but for LASIM I look up the community by name to get the ID and then call thr subscribe API. The former did seem to trigger the Lemmy instance to "learn" about the community, but it takes awhile, and there is no way to know when it has learned it other than to retry looking it up a few times.
I don't think kbin (excluding artemis.camp) supports API use yet so that'll be a no. Also kbin is different than lemmy (still federated over activitypub but different platform) so it needs to specifically be supported, won't work with a lemmy client.
Connect is a client, it shows Lemmy content and let you interact with them
Handshake is an account synchronizer, it syncs multiple accounts so you can keep accounts across instances with the same communities and soon saved and banned content
How are you gonna implement saved/banned content replication? Alls ids for posts are local to that instance, how are going to find one post from on instance in another. It might not even exist yet.
Okay, I'm not technologically illiterate, but I can't figure out how to get this to run on my Windows laptop. I got to the link, but I don't see what to download. Any help?
I'll provide the .exe tomorrow, you can download the source and compile to windows also but you would need to install flutter which is a pain in the ass