I made LASIM! https://github.com/CMahaff/lasim
I currently have 3 accounts (big shock):
To add on to this answer (which is correct):
Your “of” can also just be a regular file if that’s easier to work with vs needing to create a new partition for the copy.
I’ll also say you might want to use the block size parameter “bs=” on “dd” to speed things up, especially if you are using fast storage. Using “dd” with “bs=1G” will speed things up tremendously if you have at least >1GB of RAM.
But on the other hand, if loans were subject to bankruptcy, most poor people would never be approved to get them.
Absolutely this. There are issues with deletes not federating properly too, right?
That’s a big part of the issue here too since even when .world cleans up the content it’s already been pushed out to every other instance and will now remain there until all THOSE admins also purge it.
Under this broad of a ruleset, all software would have to be open source.
The PR for the necessary back-end changes is out for review on GitHub: https://github.com/LemmyNet/lemmy/pull/3869
FYI LASIM now supports 2FA login
This was reported a few days ago: https://github.com/CMahaff/lasim/issues/15
You can see my responses - I’m not sure there is much I can do, but I’m open to suggestions.
As stated in the linked issue, the most secure thing is to build it yourself or download directly from GitHub actions vs trusting the binaries I publish to releases.
This one got me too.
lemmy.ml specifically is running requests through a user agent checker - and if it’s empty, which reqwest is by default, you will get a 403.
You can see an example here of using ClientBuilder to set a user agent string: https://github.com/CMahaff/lasim/blob/main/src/lemmy/api.rs
So set any string (should be your project name) and then it should work.
Author of the tool here! If you are okay letting me know the instance, I can definitely take a look and see if I can figure out the issue. I might need to make an account though.
There’s lots of Lemmy instances, and I’m always finding new quirks with different configs. But it’ll help the next person who might run into the same thing!
Author here! I’ve been posting about it a good bit, and especially with the hack of .world and vlemmy’s disappearance, now others have started sharing it too. Besides myself testing it with lemmy.ml, lemmy.world, and lemm.ee, I’ve seen at least a handful of people that say they’ve run it without issues. I’m assuming the real number is much higher but there isn’t any tracking in the app, or even a download counter, so I really have no idea.
Only known issue at the minute is whether it works on Mac OS X. It theoretically does, but the only person who attempted it ran into issues where OS X wanted to open it as a text file instead of running the program - and it’s the only platform I can’t test myself.
Obviously if you do have any issues you can report them on GitHub.
In fairness to kbin, Lemmy’s API is mostly undocumented and changing constantly 😅
The linked GitHub has a “releases” section. Download for your platform. Double click executable.
Not to my knowledge, but I also haven’t checked (or looked at how kbin’s API works)
In fairness, LASIM has only been out for 5 days :)
Apparently not per the post-hack report: https://lemmy.ml/post/1901079
LASIM definitely does not - it’s designed for desktop and written rust, so not easily portable to iOS/Android.
Doesn’t look like lemmy-migrate would either - it’s a python script - unless there’s a mobile python interpreter app or something.
Hey, author of LASIM here if people have any questions!
Just so people know it does save everything to a JSON file when you click “download” so you can absolutely upload to multiple accounts or keep it as a backup.
FYI there was a federation issue and long story short this post is effectively only visible to .world, while everyone else sees this one: https://lemmy.ml/post/1870958
Apologies!
Hey OP, I wrote a tool that does this if you are still looking for one: https://github.com/CMahaff/lasim
Does profile settings, subscriptions, and blocks.
IIRC Alaska Airlines knew the plane had issues and decided to keep flying it anyway.
So yes, it’s Boeing’s fault the plane’s door blew off, but Alaska Airlines also deserves blame for continuing to fly a plane that was reporting issues with the door hatch.