• 5 Posts
  • 458 Comments
Joined 1 year ago
cake
Cake day: April 27th, 2024

help-circle


  • Actual answer for 3:

    • put jellyfin behind a proper reverse proxy. Ideally on a separate host / hardware firewall, but nginx on the same host works fine as well.
    • create subdomain, let’s say sub.yourdomain.com
    • forward traffic, for that subdomain ONLY, to jellyfin in your reverse proxy config
    • tell your relatives to put sub.yourdomain.com into their jellyfin app

    All the fear-mongering about exposing jellyfin to the internet I have seen on here boils down to either

    • “port forwarding is a bad idea!!”, which yes, don’t do that. The above is not that. Or
    • “people / bots who know your IP can get jellyfin to work as a 1-bit oracle, telling you if a specific media file exists on your disk” which is a) not an indication for something illegal, and b) prevented by the described reverse proxy setup insofar as the bot needs to know the exact subdomain (and any worthwhile domain-provider will not let bots walk your DNS zone).

    (Not saying YOU say that; just preempting the usual folklore typically commented whenever someone suggests hosting jellyfin publicly accessible)





  • Neovim, because I wanted something that would not just disappear.

    I never really got along with VSCode, opting for Atom instead. Microsoft bought GitHub, which owned Atom, and promptly discontinued it.

    Nvim has such an active community (and no “owner”) that I’m certain that this won’t happen again. At the same time, the plugin system is so flexible that I’m also certain that I will never miss out on any shiny new features.

    Over the years, my config has matured, and is mine. The thought of going back to an editor, any editor, less flexible in its configuration than nvim is just… an absolute “no”.

    It’s a steep learning curve, but well worth it.












  • I dream of a pure information protocol. Kinda like RSS, but… More.

    • allow any piece of information (news article, DM, sensor reading,…) to be wrapped in a standard format
    • subscribe to any number of source directly or indirectly (e.g. through a self-hosted relay server)
    • allow networks to define default data sources (e.g. get sensor data from machines as soon as you are connected to corporate networks
    • make the data declare what UI elements are required,
    • but allow clients to display them however the fuck they want
    • allow user to assign priorities statically or programmatically to any source, and to filter, sort, categorize based on it

    Essentially: I want “the feed” from universes like The Expanse