![](https://slrpnk.net/pictrs/image/883a171f-2b6b-46bc-93e7-a3485f857763.gif)
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
- “display_name”
- “bio”
- “avatar”
- “banner”
- “matrix_id”
- “bot_account”
- “settings”
- “followed_communities”
- “saved_posts”
- “saved_comments”
- “blocked_communities”
- “blocked_users”
- “blocked_instances”
Dev and Maintainer of Lemmy Userdata Migration
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.
Great synopsis!
The cool thing about GrapheneOS: It provides basically all the comforts and usability as any Android (stock) ROM minus some compatibility issues with a portion of Google Apps and services (Google Pay doesn’t and probably will never work, for example) while providing state-of-the-art security and privacy if you choose to utilize those features. A modern Pixel with up-to-date GrapheneOS, configured the right way, is literally the most secure and private smartphone you can get today.
I prefer Lemmy for:
I prefer Reddit for:
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.
Only do that if you know how to properly secure your server and your (V)LAN, if you host from your residential connection (and your ISP supports it).
It’s a very nice feature of a pretty polished frontend I haven’t heard of before, I’ll be sure to try it out!
Ah, so the “100% private” part is purely the recommendation engine.
This one is absolutely hilarious.
The guy allegedly knows his stuff from a technical point of view. And yet he searches for very specific info on google while logged in to his personal google account and further links his personal accounts to a forum where he proceeds to advertise his darknet marketplace and to SO where he asks for very specific advice?
This muppet searched for very specific infos on components he wanted to develop on his *personal fucking google account and implemented them shortly afterwards.
He literally panic searched, again, on his personal google account on Google in order to debug his server going down - minutes after the FBI temporally took his server physically offline to grab an image from it.
I expected elaborate timing and traffic correlation attacks, I got a stupid scammer treating his drug empire as a hobby project for his resume. Glorious.
The problem isn’t necessarily “stuff not sent over vpn isn’t encrypted”. Everyone uses TLS.
Never said it was. It’s a noteworthy detail, since some (rare) HTTP unencrypted traffic as well as LAN traffic in general is a bit more concerning than your standard SSL traffic contentwise, apart from the IP.
For this to be practical you first need a botnet of compromised home routers
This is more of a Café/Hotel Wi-Fi thing IMO. While it may take some kind of effort to get control over some shitty IoT device in your typical home environment, pretty much every script kiddie can at least force spoof the DHCP server in an open network.
Interesting read.
So, in short:
DHCP option 121 is still used for a reason, especially in business networks. At least on Linux, using network namespaces will fix this. Firewall mitigations can also work, but create other (very theoretical) attack surfaces.
The problem with Nix and its forks, imho, is that it takes a lot of work, patience, time and the willingness to learn yet another complex workflow with all of its shortcomings, bits and quirks to transition from something tried, tested and stable to something very volatile with no guaranteed widespread adoption.
The whole leadership drama and the resulting forks, which may or may not want to achieve feature parity or spin off into their own thing, certainly doesn’t make the investment seem more attractive, either.
I, too, like the concept of Nix very, very much. But apart from some experimental VMs, I’m not touching it on anything resembling a production environment until it looks to like it’s here to stay (predictable).
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!