I wrote a simple, locally running Webapp some time ago, that targets the Lemmy Import-/Export-API and supports transferring only specific userdata between accounts, as demonstrated in this corresponding Wiki Entry.

The import functionality in Lemmy is additive in nature, meaning anything you import gets added on top of existing settings instead of replacing it.

Does the same thing as these manual instructions for this usecase, may be helpful to some.

Indeed it does, I was talking about adding a checkbox tagged “Only transfer blocked users” instead of having to click through some menus.

Sure, the code is completely client-side, simply clone it. If you’re running into CORS problems due to the file:// scheme Origin of opening a local file, simply host it as a local temporary server with something like python -m http.server .

This is due to the two ways most instances validate Cross-Origin requests:

• Sending Access-Control-Allow-Origin: * (allow all hosts)
• Dynamically putting your Origin into the Origin header of the response to your requests by the backend

file:// URLs will result in a null or file:// Origin which can’t be authorized via the second option, therefore the need to sometimes host the application via (local) webserver.

The whole point of this being a web app is to make it as easy as possible for the user to download/modify/transfer their user data. LASIM is a traditional app the user has to download and install, similar to a script this web app was developed to replace due to being too difficult to use for some users.

The import functionality targeted by this API is additive and my app features a built-in editor to add, modify or remove information as the user sees fit. To achieve your stated goal, you’d have to remove anything except the blocked_users entries before importing, which my app supports, I added a wiki entry explaining the workflow in more Detail.

I may add options to modify the exported data in some ways via a simple checkbox in the future, but I wouldn’t count on it. I’m always open for pull requests!

• “display_name” ​
• “bio” ​
• “avatar” ​
• “banner” ​
• “matrix_id” ​
• “bot_account” ​
• “settings” ​
• “followed_communities” ​
• “saved_posts” ​
• “saved_comments” ​
• “blocked_communities” ​
• “blocked_users” ​
• “blocked_instances”

The export/import functionality is, yes. This implementation uses the same API endpoints, but the main reason for this existing:

An instance I was on slowly died, starting with the frontend (default web UI). At least at the time, no client implemented the export/import functionality, so I wrote a simple script in Bash to download the user data, if the backend still works. Running a script can still be a challenge to some users, so I wrote a web application with the same functionality. It’s a bit redundant if we’re talking about regularly working instances, but can be of use if the frontend isn’t available for some reason.

Pretty much anything, from your Desktop Environment to the simplest application running in the background, will have way more of an impact than pretty much any semistatic website. I’m curious, what do you mean with “in the optimal way possible”? Are you constantly maxing out your RAM already, and if so, how?

I prefer Lemmy for:

• actually engaging with content (commenting/posting/voting) instead of simply consuming. By the time the API restrictions came around and the ads/bots started to dominate, it felt pointless to engage on Reddit any more.
• the positive parts of the federated and FOSS nature. Choose an instance, build your own, use or build any client you want to, federate or defederate whoever you want.

I prefer Reddit for:

• getting info/recommendations on things. The knowledge base is magnitudes larger than anything Lemmy can offer atm. Also, due to the centralized nature, it’s so much easier to search for something on Reddit.

Lemmy’s got some problems and I can’t stand the interinstance drama, also, due to the decentralized nature, some instances can’t keep up or the admins don’t care any more, so whole communities can essentially be held hostage or simply die until a toolset to move a community from one instance to another (and propagate the change properly to the Fediverse) becomes available.

Well, this tells us that more privacy minded people with a background or interest in technology tend to be more present/engaging on Fediverse platforms. Not really surprising.