• 3 Posts
  • 116 Comments
Joined 11 months ago
cake
Cake day: April 27th, 2024

help-circle

  • I mean… “To fear”? No. But There are plenty legitimate to remove comments and posts that have nothing, and I mean absolutely nothing, to do with mod overreach or censorship.

    • removing derailing threads from heated discussions
    • removing the annoying “just asking questions” people from LGBTQ+ safe spaces
    • removing posts accidentally posted into the wrong community
    • removing troll posts
    • banning repeat troublemakers not willing to follow the rules
    • removing aggressive, sexist, racist,… posts

    On the other hand, anti-moderation people only ever seem to come up with “but I want to be able to post whatever I want!”

    “Free speech” in this context means: you can go create your own instance or community, with blackjack and hookers! And mods can use the tools at their disposal to enable the rest of us to not have to deal with bullshit.






  • At this point, package management is the main differentiating factor between distro (families). Personally, I’m vehemently opposed to erasing those differences.

    The “just use flatpak!” crowd is kind of correct when we’re talking solely about Linux newcomers, but if you are at all comfortable with light troubleshooting if/when something breaks, each package manager has something unique und useful to offer. Pacman and the AUR a a good example, but personally, you can wring nixpkgs Fron my cold dead hands.

    And so you will never get people to agree on one “standard” way of packaging, because doing your own thing is kind of the spirit of open source software.

    But even more importantly, this should not matter to developers. It’s not really their job to package the software, for reasons including that it’s just not reasonable to expect them to cater to all package managers. Let distro maintainers take care of that.






  • I am a bit confused tbh 😅

    The link you send links to docker projects, the link I sent is the second one of those. Seems pretty straightforward?

    But to be fair, I have never used docker for any of this. In my nix config, it’s literally just:

        services.prowlarr.enable = true;
        services.prowlarr.openFirewall = true;
    

    There’s not really anything you need to configure host-side. Prowlarr needs to be able to communicate with sonarr and radarr (same as jackett), but otherwise it’s basically stateless.