Sounds good. Let me know how it goes. Hopefully it’s just instance instability.
Sounds good. Let me know how it goes. Hopefully it’s just instance instability.
Could be some kind of new bug, but I’ve also seen this happen when an instance is under heavy load or otherwise glitching out - it’s starts sending back invalid items on the API and LASIM chokes on them.
For what it’s worth I made an account on reddthat.com and was able to download and upload to it fine.
Maybe try again? Or is this some other instance? (I’m making assumptions based on your account)
Yep, if you are on Windows just extract that .exe somewhere and then run it.
The README is displayed underneath the screenshots on the link to LASIM above. It tells you how to run it. See “How it Works”.
https://github.com/CMahaff/lasim#how-it-works
The latest version supports any Lemmy 0.18.3 instance. You can see which version a Lemmy instance is at the bottom of site. For example, your instance, reddthat.com, is 0.18.3. Most instances should have upgraded to 0.18.3 already - choose one of those. Any instance running 0.18.3 should work, big or small.
The account you “download” with won’t be touched at all. The account you “upload to” will receive all the subscriptions and blocks of the downloaded account.
Thanks for spreading the word about LASIM!
Just letting you know that today I finished an update that adds upload options, including an option you can turn on to “sync removals”, which kindof achieves this.
It may not be the right tool for every scenario though - turning it on basically means that whatever account you upload too will end up identical to the one you downloaded by following/unfollowing and blocking/unblocking as needed. But if you’ve got new follows, blocks, etc. spread across several accounts you wouldn’t want to turn it on or you’d lose all the changes on the accounts except for whichever one you downloaded.
The option works better in scenarios where you’re mostly using a Main account, and just trying to keep the Alt accounts in sync with whatever the Main account does.
That’s so odd. No idea what would be causing that on Windows 10.
For the windows 11 issue I can only think short downtimes of the instance you are trying to use, or your account has something unique about it that I’ve never encountered before.