• 10 Posts
  • 638 Comments
Joined 2 years ago
cake
Cake day: June 2nd, 2023

help-circle


  • Yes with ActivityPub there’s always failed federation. But Lemmy will send the delete request out when you delete your account. Other software or instances might not honour it, but the intent is there.

    As opposed to reddit who do not remove comments when an account is deleted, only mark it as a comment from a deleted account.

    I’m not against Lemmy’s implementation, but it does require you to collect information you need at the time not assume it will always be there.








  • No problem! I’ve used it for years, though my home assistant running on a Raspberry Pi 4 is now doing the pi-hole thing with adguard instead as the original one was having issues. Though you get weird DNS quirks when the machine running DNS also relies on the internet.

    Plus that time I did a dumb thing in home assistant to see what would happen, and it brought the internet down.

    So I am keen to get another Pi. I highly recommend keeping it on a dedicated device you never touch except for updates!




  • Vote privacy can be tricky in an environment where every vote gets sent to thousands of instances and needs to be verified as legit via the ActivityPub protocol.

    Piefed does a good job of this I think. If vote privacy is enabled, they create a second account that is used only for votes. Other instances see the votes and can validate them against the vote account but it’s not tied to the actual user (except in their home server database).

    A benefit of this is that the vote account for the user is always the same, so you can still track vote manipulation, and ban the vote account if needed.


  • One of my favourites that I haven’t seen mentioned is the Todo.txt extension.

    It adds a todo list in the tray synced to a couple of files (that I store in Nextcloud). I add things I need to do to the list, and I also play with the settings so it colours by priority and sorts by priority.

    I also use the ntodotxt app on my phone to sync items. The app is fine but I really like the gnome extension, very handy.


  • From my understanding, that’s not quite the intent.

    Currently, there are a bunch of bots that behave themselves. For example, Google’s search crawler.

    They identify themselves with a user agent, e.g. GoogleBot, so Cloudflare know what it is and don’t block it.

    Unfortunately, some bad bots pretend to be GoogleBot by setting the same user agent. To counteract this, Cloudflare compares the known IP address ranges with the traffic to make sure it’s actually coming from Google. If it’s not coming from a Google IP range but the user agent says it’s Googlebot, they block it because it’s probably bad.

    But knowing which IPs are OK and which aren’t is a challenge because they change over time.

    So the proposal here, as I understand it, is to create a system whereby by publishing a public key, you can prove that GoogleBot really is from Google, AmazonBot is from Amazon, etc, and not another crawler pretending.

    The spammy ones can keep generating new domains and keys, but you know for sure it’s not Googlebot or whatever.

    So it helps “good” traffic prove who it is, it’s not supposed to be for tracking bad traffic.