• 20 Posts
  • 39 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle


  • Mountaineer@aussie.zonetoMemes@lemmy.mlDear iPhone users:
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    2
    ·
    7 days ago

    Funnily enough, I’ve got a few friends who are long time iPhone users, who actually point this stuff out themselves:

    “OMG! Have you seen the eye watering price of the new one?”
    “Yay, I finally get stuff you’ve had for years.”

    Neither party would ever consider anything else, and they both buy the new model every year. 🤷

    At this point I admit that my reasons for choosing Android all those years ago no longer exist or matter, but I can’t imagine changing ecosystem either.












  • As /u/rezz@lemmy.world said, you can try to force a scan of the library. Log into the admin and hit the big “Scan All Libraries” button, then give it some time.

    A refresh of that page should show a progress meter.

    In order to encourage more accurate detection (assuming it can find/access the new file at all), there are advised naming schemes for your files. See here for a basic overview: https://jellyfin.org/docs/general/server/media/movies

    I prefer to include the full name, year and imdb info of a movie, ie Citizen Kane isn’t just “Citizen.Kane.mp4”, it’s:
    “Citizen Kane (1941) [imdbid-tt0033467].mp4”
    based on the information that’s publically available here https://www.imdb.com/title/tt0033467/

    Even if you don’t enable imdb itself for the metadata lookup, that will give you an almost guaranteed detection during a library scan.

    If this sounds like too much work, there’s several automated tools for naming your personal dvd rips, such as Radarr.

    If it’s still not being detected, it’s time to dig into the logs and find out WHY it’s erroring.
    Is it permissions?
    Is it naming?
    Is it the phase of the moon?

























  • Short answer no.
    Plex works by having a centralised server run by Plex themselves, that facilitates your client connecting to your server.

    The external facing part of Jellyfin server is basically a web server, and it’s a bad idea to expose that to the internet without putting a reverse proxy in front of it (hence the mention of NGINX above).
    Another option is to have a VPN connection to where you are running Jellyfin and then only access Jellyfin pseudo locally (so potential security problems aren’t a big concern). This introduces other complications if you want to access it remotely via things like Roku or Chromecast, especially if you have multiple external (and probably not tech savvy) users.

    I want to stress that none of this is prohibitively expensive or hard, but doing it involves learning and effort.
    All the information and programs you need are available online for free.

    If you only wanted to use Jellyfin at home (server in the cupboard, client on the tv), none of this other stuff matters. If you want to access Jellyfin remotely, and the idea of running a reverse proxy or a vpn server with the corresponding exposed ports and domain configuration sounds scary, Jellyfin is probably not for you.