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

help-circle










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



  • You can interoperate with googles RCS.
    If you are willing and able to enter a partnership like Samsung, you can do it fully (including encryption support etc).

    Google are determined to not make it easy, and I agree with you, it appears to be yet another messaging land grab.

    Trying to put myself in their headspace for a moment, one justification for making it hard is to stop thousands of apps coming out declaring “full RCS support!” through the APIs, then screwing the pooch (through poor security or deliberate back doors or or or).
    Right now Google are desperately attempting to make RCS happen, after almost a decade of trying and failing to make various carriers play ball.
    They do not want any bad press about how feature poor/insecure/slow/buggy it is right now.


  • Mountaineer@aussie.zonetoAndroid@lemdro.idIs RCS an open standard?
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    9 months ago

    Only Google can make an RCS app

    Yes and no.
    You don’t need to make your own OS, but you do need to implement support for the RCS protocol within your app, rather than piggyback on Googles APIs.

    I don’t like it, but there’s no legal requirement for google to provide those APIs, like they did with SMS etc.




  • it’ll work just like SMS does now

    I agree with this part of your statement 100%.
    It will work POORLY.

    Whether it’s in the same app or simply a different colour like SMS is currently, it’ll be a half assed implementation, designed to segregate your iphone and android friends.

    Got an existing iphone group chat? Bet you can’t add an RCS participant to it.
    Create a new RCS group chat so you can include everyone? Bet it’s missing features that you’d get in imessage.
    Receive a high resolution video from a friend via imessage? Forward that to another friend via RCS and they’ll receive 5 blurry pixels.

    And throughout all of this, apple will blame the RCS protocol and say “We’re actively working with GSMA to improve RCS”.

    No one trusts apple for the very simple reason that they have a habit of saying the quiet part out loud: Tim Cook Says ‘Buy Your Mom An iPhone’