• 0 Posts
  • 9 Comments
Joined 8 days ago
cake
Cake day: May 14th, 2026

help-circle

  • The Jellyfin vs Plex thing always struck me as odd. As in - why are we holding JF to a different standard to (say) Immich, Syncthing, Pi-hole or any one of a thousand different programs people self host?

    Yes, JF ships multi-user accounts and client apps etc. I get it, “multi-use” is implied, so the comparison isn’t totally unfair. But there’s a difference between ‘this feature exists’ and ‘this is the primary purpose of the tool’.

    The fact that you CAN share it externally doesn’t mean everyone running JF is doing that, or that it should be the benchmark the whole project is judged by.

    To me, self host means “I host it, myself” not “I host it and then pretend to be Netflix for family and friends”. If that’s the use case, then of course, Plex away.

    It’s cool that you CAN share JF externally, and it’s cool that Plex does that differently / better. We shouldn’t hold one to the standards of the other.



  • I’m with you on this I think.

    I have no problem with anyone using an AI scribe (though I would prefer one that was on device rather than cloud based). I am aware of things like Lyrebird Health that integrate with EHR management software - frankly, anything that allows the practitioner to focus more solely on the patient is a good thing. After all, they are meant to be treating the patient in front of them, not the computer screen.

    The prior point about legal liability is accurate IMHO. Medical health records are functionally a legal record, and should be treated as such. Responsibility for review, redress of inaccuracies etc cannot be waved away as “ChatGPT did it”. If the practitioner is willing to take the onus of that on, and treats the scribed document with the same fidelity, chain of provenance etc as other records, I’m probably ok with it.

    Requiring patients to consent to cloud-based AI scribing as a condition of access is where it gets uncomfortable, and your point about local alternatives is exactly why. If deterministic, on-device transcription exists and does the job, the justification for mandating a cloud pipeline through a psychiatric service gets pretty dicey, pretty fast.

    I think I can see a way to have Dragon Dictate record the audio, convert it to text and then have on device AI pull out relevant bits to populate a template. That doesn’t abrogate the need to actually LISTEN to the patient but it might fix that ‘capture’ part of the funnel.



  • Cool. So what happens if I run a version of Android that doesn’t inherit Google security theater cruft? That is to say…what if the user simply…does not…upgrade the Android version to be affected by this (eg: uses an old phone or blocks OS version update?).

    My phone is going on 7yrs old. Perfectly happy with it. When it breaks, I will get a phone of the same era (2nd hand or new-old stock) or investigate other options.

    So, it seems to me, the winning move is not to play the game (in any one of 100 diff ways).

    Or am I missing something here? Is there something that will prevent older tech from working? Because if so, I am happy to YOLO my phone and switch to a dumbphone if I have to.


  • Yeah, transcoding entirely off - directly stream stored 720/1080p files (downloaded like that, although I did use handbrake on the pi once to transcode Space 1999 season 1. Took about 2 days I think).

    Someone else was just talking about Wyse thin clients. I’m fairly sure that a $40 Wyse thin client out performs even the best Pi 4 (maybe 5 sometimes). If I can’t find a way to fix mine, I may have to buy a few for uh…science. IIRC, they idle at about the same as the Pi



  • It’s very ok, as long as you don’t expect multiple 4K streams at it.

    I ran JellyFin on a Pi 4 for about 3 or 4 yrs before it started acting up. So long as you don’t transcode, it works wonderfully well. I had it serving upto 4-5 x 720p streams at same time. IIRC, it can just about do a single 4K, 60? Never tried - all my media is 1080p or less.

    IIRC, mine is overclocked and undervolted using PiTools (and is in a Argon 40 case with a m.2). The Argon 40 case (I think) is causing it to short (something with the daughter-board? Dunno). Better options these days.

    Paperless I don’t use but I don’t see why it shouldn’t be possible.

    Don’t try Immich unless you like pain (or turn off the AI stuff)