melmi
@melmi@lemmy.blahaj.zone
- Comment on AceCoding.social - Vibe coding on the social web based on the semi-formalic language ACE (Demo) 1 week ago:
The cursed LLM thing uses buttplug.io on the backend, I just wanted to share it because the premise is very funny to me.
- Comment on AceCoding.social - Vibe coding on the social web based on the semi-formalic language ACE (Demo) 1 week ago:
- Comment on How do I securely host Jellyfin? (Part 2) 2 weeks ago:
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: 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.
- Comment on How do I securely host Jellyfin? (Part 2) 2 weeks ago:
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.
- Comment on Pixelfed leaks private posts from other Fediverse instances - fiona fokus 4 weeks ago:
I kinda of lean towards the idea of “private posts” being a bad idea as a result, just because it creates a false sense of security.
- Comment on Pixelfed leaks private posts from other Fediverse instances - fiona fokus 4 weeks ago:
The issue is that if you don’t default to federation, it becomes essentially impossible for new instances to join the fediverse. A potential new instance would have to go around to every single existing instance and ask to be allowlisted, which is onerous for both the new instances and for the large server admins who would be getting tons of requests. It would also essentially kill selfhosting as a result.