![](https://forum.basedcount.com/pictrs/image/7b629d19-c52d-41d8-b1a5-806838b03a5d.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Ansible guide. I didn’t follow this one myself but the guy who set up my instance said it was pretty easy
https://github.com/LemmyNet/lemmy-ansible
…or join a smaller instance.
Ansible guide. I didn’t follow this one myself but the guy who set up my instance said it was pretty easy
https://github.com/LemmyNet/lemmy-ansible
…or join a smaller instance.
Same, since I updated my instance to 0.18 Jerboa doesn’t work and instantly crashes.
Upvoting this post from Connect for Lemmy. Actually I think I still prefer Jerboa. Unfortunately it has stopped working since I updated my instance to 0.18 so this will have to do for now.
Couldn’t the protocol be updated to be more compliant with the right to be forgotten? Something like, when a user deletes a comment it gets deleted from the DB of every federated instance. Sure enough, admins might have made backups and that would theoretically go against the GDPR but still… you can only apply these laws to a certain extent. It’s the same as you posting a picture on Facebook, me downloading it and you deleting it afterwards. Even if you were to make a GDPR request to Meta you still couldn’t get the picture on my PC. But that’s not Meta’s fault, they can’t do much about that.
That’s what I’ve blocked yeah. Though you can’t really have any confirmation (the “software” and “version” fields will remain blank) because they haven’t even enabled federation yet.