• 0 Posts
  • 9 Comments
Joined 3 years ago
cake
Cake day: June 10th, 2023

help-circle
  • As much as I despise Oracle and the lawn mower man known as Larry Ellison, I don’t think this is a problem. Oracle also had a lot to do with btrfs, and while that filesystem has problems, they’re not the sort of problems usually associated with Oracle (i.e. rapacious capitalistic practices like patent trolling and suing the fuck out of everyone all the time always). Oracle won’t own XFS, it’s owned by every single person who has ever contributed to that codebase.




  • Badabinski@kbin.socialtoMemes@lemmy.mlIt's true
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 years ago

    While I’m glad that furries have a nice space where they can (hopefully) not be harassed, I decided I could use a bit less furry porn in my life. On kbin (on mobile, in the PWA), you can block a domain by searching for it (I think it was yiffit.net, but I can’t remember), then click the kbin logo at the top right, then scroll down to where you see /d/yiffit.net, then click the little block icon. I’m sure Lemmy has the same capability, but I don’t know how to do it. With that, the new feed has a lot less porn lol.

    EDIT: it was yiffit.net, not furryit.net



  • TOR was started and funded by the US Naval Research Labs ¯⁠\_⁠(⁠ツ⁠)⁠_⁠/⁠¯ it’s not perfect, but I know it’s widely used as a first line of defense. I won’t comment on the Radio Free Asia stuff because I have no knowledge of that, but I feel like there’s a lot of privacy tools we use that were initially funded by the US government, and even the US military in some cases. It always comes back to relative threat levels. Are you trying to avoid invasive corporate monitoring and some degree of government surveillance as a regular person? Signal is fine. Are you actively trying to hide from government intelligence agencies? Maybe it’s not so fine. Signal is still preferable to a messaging application owned by Meta, imo.



  • Just to be sure — you uploaded the public key to your servers, right? In your user’s directory on the remote server at ~/.ssh/authorized_keys. Your private key should never leave your system. That’s a very common mistake in my experience. The wording of your post makes it seem like you may have done that.