Shimitar

  • 38 Posts
  • 1.17K Comments
Joined 1 year ago
cake
Cake day: January 28th, 2025

help-circle
  • No, really, wireguard encryption overhead is negligible unless you have a really old CPU (like a Pentium100 or something).

    Whatever slows down your N100 is not wireguard per se, probably some tailscale overhead going trough their servers.

    I have a fairly dated rented server, with an Atom D510, 2 cores, which is 10 years old, and accessing it over wireguard or not, I can still max out the network bandwidth without any visible CPU overhead.


  • 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.










  • I fully respect your comment, and I don’t doubt there are good reasons behind Plex. I choose to use jellyfin because I was put off by the corporate product resell approach of Plex that goes against my self host idea, so I never used Plex and cannot say anything bad about it.

    But I find annoying and even suspicious that every time there is a Plex or jellyfin discussion a few voices always denigrate jellyfin like it’s a no good choice for lack of features or dubious security and such.

    Yes guys (not talking to you in specific) I understand that jellyfin lacks those features, many people don’t care, and who do care they already know.





  • Been on jellyfin since day one. Works fine, UI is great and gets the job done. TV UI maybe not top notch, buy usable. Mobile UI just fine and usable.

    Also, exposed on the internet (reverse proxy, OIDC, https the works) for years now with zero issues whatsoever as well .

    There are a few users always throwing thrash on jellyfin, maybe pissed off users that paid for Plex, or Plex shills that like to denigrate jellyfin, I don’t know.

    Just ignore them.

    Jellyfin is perfectly usable, yes you need to setup port forward, VPN or whatever, but it’s exactly our target audience so move along and stop bitching, Plex shills.

    Stay with Plex, use jellyfin, whatever fit your bill.

    Anyway plex does not fit my concept of self hosting to be free from cloud lock ins.


  • As far as I get it, subsonic has an open API implemented by navidrome and a few other open source servers. All subsonic compatible apps will work.

    For Android the best is by far Symfonium, but it a paid app (well worth it).

    Otherwise tempus is another valid and open source app.

    And no, subsonic (and navidrome) has nothing to do with audiobooks or podcasts. I selfhost both navidrome and audiobook shelf to cover all cases, and I am pretty comfortable.





  • Https add an encryption layer on top of http. Except that, they are the same. Also, https provide a way to make sure the website is who he claims to be and not a random hacker website pretending to be it.

    Whatever you do on https it’s encrypted end to end and cannot be read by somebody in the middle.

    For example, if you login to a webpage with http your password will be sent in clear text and possibly read by somebody in the middle (your internet provider, your company, any other network in between …) while on https that same password is encrypted before it leaves your browser and it’s safe until it reaches the server, where is decrypted

    It works with a chain of certificates approved by some authorities that your browser trust, so that beside encryption you can also trust that the website you are connecting to is actually who it claims to be (of course, that require you trusting the web site certificate and chain of trust).