• 14 Posts
  • 453 Comments
Joined 1 year ago
cake
Cake day: January 28th, 2025

help-circle


  • The maximum internet speed you get is the speed of the slowest link in between your house, your ISP, any other network in the middle, and the ISP you are using to connect your remote device to the internet itself

    On top of that, put tailscale. Assuming packets go directly between home and your remote device, then tailscale should not impact. But if the packets do go trough a tailscale server, like you have no public IP address at home, or CG-NAT, then that will be the bottleneck most probably.

    Tailscale on itself isn’t a measurable overhead.

    In general, for home network speed, consider your home UPLOAD speed (as that will the seen as “download” speed from outside) not the download speed, which is often many times faster.






  • Lowering the entry barrier is a good thing… Self hosting need critical mass to support and use all the nice things we like to selfhost

    More so, from the point of view of big tech independence, for those who care, again lowering the barrier is very important

    So welcome to docker and stuff, I use docker for half my stuff or more, it’s just so much more convenient.

    But never stop trying to understand and don’t be a passive docker-puller whenever possible :)











  • Agree. I went directly with Jellyfin because I joined late the party, but never regret it.

    So can’t comment on Plex, because I never used it. But I see the news and see the enshittified path it’s going on with Plex

    I understand that they need revenue, specially if they actually provide the bandwidth to let you access your media from outside home. I also understand why people is mad, but I guess convenience come with a price, of you don’t want to pay for it, there are alternatives I don’t see anything bad in switching to jellyfin.


  • I fully understand your point, but the mailcow as open relay seems strange. Anyway, it’s a risk/cost tradeoff right? Everybody should do it’s own assessment and experimentation. But after the initial setup, it’s zero maintenance. The only maintenance i do is keep the stack regularly updated, and it broke twice in 20+ years (dovecot new config format, WTF…)


  • Isn’t that the gist of selfhosting?

    Yes you can do it, yes you can have it done for you by somebody else. The first is fun, and risky, the second is less fun and less risky. We are all here for the fun… and probably we all don’t care too much of the risks. But why shut down everybody who ask about email selfhosting with a don’t do it? Let them try, make errors and fix them, maybe they learn something new, maybe it works out for them

    What is the worst that might come out of it? Some spam? A blacklist? Come on, you can survive both. Don’t use your primary email account as self hosted from the beginning maybe, to mitigate all those risks, no?