• 0 Posts
  • 126 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle
  • Being able to sell FOSS is one of the freedoms “free software” refers to.

    Honestly though I think the thing that struck me the most and I found kind of scummy was their “value statement” where they were advertising the OS by comparing it to the prices of the proprietary software is includes alternatives to. You misreading the website wasn’t an accident, they designed it in a deceptive way IMO.

    If they were more honest about it, I wouldn’t have any problem with them charging for the convenience of having everything pre-bundled. Of course you could set everything up yourself, but Linux is notoriously finnicky. People want a complete experience, they want support. They want the slick branding.








  • It seems like multiple things are being conflated here and I’m not sure what the reality is because I’ve never used Plex.

    Some people claim this has something to do with Plex needing to pay for NAT traversal infrastructure. Okay, that seems sort of silly but at least there’s the excuse that their servers are involved in the streaming somehow.

    But their wording is very broad, just calling it “remote streaming.” That led me to this article on the Plex support website, which walks people through setting up port forwarding in order to enable “remote streaming”! So that excuse doesn’t really seem to hold water. What exactly is being paid for here then? How do they define what “local streaming” is?


  • As a Trek fan, I think the term “egg prime directive” itself is bad and causes miscommunication. The people who are pro-EPD seem to mostly argue the EPD is about not dictating to people what their gender is, while people who are anti-EPD say the EPD is about not mentioning the possibility that someone could be trans at all.

    Taking everyone at their word, it seems like people are interpreting the egg prime directive differently. If pro-EPD people really do think it’s okay to suggest/ask if someone has considered if they might be trans, and the only thing forbidden is explicitly dictating “you ARE trans”, I think the prime directive analogy is a bit misleading and might be part of the issue.

    The prime directive is very dogmatic at times and basically says that you can’t interact with prewarp civs period. Following the metaphor, it suggests that you aren’t allowed to talk about being trans at all with potential eggs until they crack their own egg first. Based on that, I can see where the OOP is getting their interpretation from.


  • LLMs are very good at giving what seems like the right answer for the context. Whatever “rationality” jailbreak you did on it is going to bias its answers just as much as any other prompt. If you put in a prompt that talks about the importance of rationality and not being personal, it’s only natural that it would then respond that a personal tone is harmful to the user—you basically told it to believe that.








  • Tailscale is just a bunch of extra fancy stuff on top of Wireguard. If you don’t need the fancy stuff, using raw Wireguard can be more lightweight, but might require more networking knowledge.

    The biggest thing Tailscale brings you the table is NAT traversal. On top of that it uses direct Wireguard tunnels as necessary instead of creating a mesh like you usually would if you were using raw Wireguard. It also offers convenient bits of sugar like internal DNS, and it handles key exchanges for you so it’s just generally easier to configure. When you do raw Wireguard you’re doing all the config yourself, which could be a pro or a con depending on your needs—and you’ll be editing config files, unlike Tailscale which has a GUI for most things. It also supports some more detailed security options like ACLs and I think SSO, while Wireguard is reliant on your existing firewall for that.

    Here’s what Tailscale has to say about it: https://tailscale.com/compare/wireguard

    I’ve messed around with Tailscale myself, but ultimately settled on running Wireguard. The reason I do that though is because I trust my LAN, and I only run Wireguard at the edge. Tailscale really wants to be run on every node, which in turn is something that raw Wireguard theoretically can do but would be onerous to maintain. If I didn’t trust my LAN, I’d probably switch to Tailscale.


  • A lot of people have suggested Tailscale and it’s basically the perfect solution to all your requirements.

    You keep saying you need ProtonVPN which means you can’t use Tailscale, but Tailscale actually supports setting up an exit node which is what you need. Put Protonvpn on the Raspberry Pi, then set it up as an exit node for your tailnet. There’s a lot of people talking about how they did this online. It looks like they even have native support for bypassing the manual setup if you use Mullvad.

    As long as every client has the ability to use Tailscale (I.e. no weird TVs or anything) this seems like it checks all your boxes. And since everything is E2EE from Tailscale, TLS is redundant and you can just use HTTP.