

The UFOs nobody cares about /s.


The UFOs nobody cares about /s.


We’ve already seen these movies. And they weren’t very good to begin with.


Well that was an impressive speed run to enshitifcation. What kind of sensorship is queued up next?


Get a router/travel router and set it up as a gateway where it provides its own SSID for the Roku to connect to. Basically a bridge to the complex, where you can inject some software. A lot of the travel devices have baked in Wireguard+Tailnet support. iNet are generally good products.


to get something that is idiot proof.
The problem with Jellyfin in particular is that it needs to support binary streaming protocols. You can implement some gateway/firewall-based security in front of Jellyfin, but in the end it is still Jellyfin’s internal mechanisms mostly responsible for its own security. I don’t use Authentik but I have read many good things. The only real “advantage” of it is that it forces your users to somewhat better credential handling. Jellyfin still only supports LDAP, so the users will have to enter their Authentik username and password – very similar to just local accounts managed by Jellyfin. So IMO, not offering you that much extra in terms of security. You will be better served by firewall tools like fail2ban, crowdsec, geo-fencing, etc.
Depending on where/how your users access Jellyfin you could have something a bit tighter. If they never run it on a TV you could do something more advanced like mTLS where you issue them a certificate with a TTL of several years, walk them through installing it on their phones/laptops, and then have that in a reverse proxy. But at that point you might as well walk them through setting up a VPN mesh network.
For Seerr, it’s just a standard web app .You could put a reverse proxy in front that requires OIDC with Authentik. Seerr is also pretty close to having native OIDC integration. Personally I prefer having two rounds of OIDC – reverse proxy really narrows what the public can see as a first layer.
For BookOrbit, I am not familiar enough with the Kobos. My guess is, you could put BookOrbit behind a reverse proxy that enforces OIDC, but you might have to allow a bypass for /api route. Then you’re relying on BookOrbit to authenticate all /api requests through API tokens. This would look like the normal Kobo linking process, so no real difference, but then your BookOrbit web UI is locked behind OIDC authentication.


Glad California is fighting but they aren’t really my concern. I’m worried all these shithole red states are doing exactly what the fascist want, and red states being complicit with illegal requests is all they need. We really need overwhelming number of votes to overcome the fascism.
He gifted it to media companies. They know who butters their bread, and that’s not a good thing. Even if it means he doesn’t have the money anymore. Its also a waste because it forces Democrats to spend more than they would, even if it’s now know to not be the driving factor. He’s just so fuckign rich he can do the same thing every year for the rest of our lives and wouldn’t care.