there are some admin endpoints that are authenticated using any local IP, but the method they use allows spoofing the IP so those endpoints become accessible essentially without authentication
there were some other issues to do with unauthenticated enumeration and playback of content i believe too
i’m not likely to wrangle installing and maintaining wireguard on my mums cheap smart tv
and if that’s the solution, as i said you get plex local playback so that’s free still anyway
my main issues
the thing that everyone always glosses over is that jellyfin should not be run on a public network. it has known security vulnerabilities… that includes VPN remote proxy, so now you have to have external users on your actual VPN, and if that’s the case then plex will work fine because it’s “local”, and has a lot more features
(and my main issue: media segments don’t work on swiftfin)
if i found out someone was using a voice changer in an interview, that’d be a massive red flag for me
i’d consider that all a good thing, but i can also see how it’s more work
they’re supposed to be stateless because it’s easier to manage, upgrade, etc… if you don’t want that, you can just use load/save/commit (or import/export: can’t remember off the top of my head which is which) and ignore volumes: it amounts to the same thing… there’s also buildpack rebase so you can swap out the base container and keep your top level changes for quick version upgrades that are super simple to roll back
misconfiguration here i think is a dangerous way to phrase it… it implies that there is a secure way to run jellyfin on its own. jellyfin, by itself, should never be exposed to the www. it is, no matter the configuration, insecure. to run jellyfin on the www you must put a VPN or other reverse proxy with auth over the top of it
swiftfin is mostly there but doesn’t support media segments, which is a deal breaker for me
really unfortunate since jellyfin media segments is a much better implementation of the concept than plex
i’m watching the swiftfin issue for when it gets added and i’ll be all over compiling and testing it
you can use commit, save/load, import/export for the same thing as VM snapshots
actually for big youtubers, ad revenue from google isn’t all that huge afaik. i’m going only on the LMG breakdown they did, but they only get 26% of their revenue from adsense… that’s no tiny share of course, but i wouldn’t call it completely catastrophic to loose
i’d modify the CPU requirement and say you can sub that out for a 2nd hand cheap nvidia card if it’s easier
here’s the table of cards with nvenc: https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new
i’m running an old af xeon and added a $30 entry level GPU from years ago and it was a great upgrade
a chroot is different, but it’s an easy way to get an idea of what docker is:
it also contains all the libraries and binaries that reference each other, such that if you call commands they use the structure of the chroot
this is far more relevant to a basic understanding of what docker does than explaining kernel namespaces. once you have the knowledge of “shipping around applications including dependencies”, then you can delve into isolation and other kinds of virtualisation
there’s actually a bunch of these, but healthcare tends to fall prey to “too much money, too many consultants, fancy brochures”
i imagine that it’s only the UI - they’d have to implement all the profiling etc themselves… but it does mean they have a framework to build the tools into, and not having to build the UI rather than starting from scratch which is a huge help
waterfall:
personally, no i don’t. perhaps it’s because i skim a lot of code and im just used to it? i’m not sure, but honest truth i find capitals mostly redundant. perhaps useful to add context (names, acronyms, etc)… i add them for uncommon acronyms, but common things that people know i tend to skip too
you can say it’s lazy, and i’ll absolutely take that: it’s totally lazy… but there’s no weird effort or external image decision involved in it?
i am on a phone. i did not press any extra keys to make my phone not do caps - this is because i have changed my phone to this, because when you write about technical things, capitalisation is important - lower case everything is lower case everything. i’m not about to start hitting an extra key at random times when this is perfectly fine. i’ve never had an issue reading all lower case
it’s not try-hard; it’s practical for people who work with tech
git is exactly as unfriendly as a distributed source control system that doesn’t shy away from power user commands needs to be
… sure it’s difficult to comprehend, but yknow what’s worse? getting into a bullshit situation and having broken garbage repos in every other “user friendly” system on the planet
expanding on this, depending on technical skill level:
i’d probably get some SBCs like raspberry pi (or cheaper; raspberry pi is probably overkill here!) to be the terminals, run asterisk and have an extension for each terminal… run a voip client that automatically picks up any call it receives, and connects to a mic & speaker, connect a button to GPIO and write a script to call a conference extension for all devices (or multiple buttons for multiple extensions to call individual locations)… i’d probably add a second button for a “call back”-like feature - a terminal broadcasts a message and there’s a button to reply only to the terminal the last call was from
this would allow you to use phones as terminals too - even receiving “calls”, although in that case the caller would have to wait for the phone user to pick up - just like a regular phone. probably more useful as a transmitter
all of these things aren’t super difficult in isolation - probably setting up asterisk is the hardest part
which they handled about as well as you can: prompt and clear notification without trying to pass the buck
the potential of a data breach is just a fact of life with any SAAS product - bugs happen… and it’s exactly the SAAS part of the product that makes the invites/login/aggregation of servers so smooth