MaggiWuerze

I fell like the way investments are currently made, coming up with something new is made almost impossible. Most of the hardware is designed with LLMs in mind

Was my first thought as well. These things really need to find a way to store a larger context without ballooning past the vram limit

Funny, most people I’ve talked to said that the backend code usually is better structured and written, while the frontend (web and games) was a hot mess

Even if they build the AI doing it from scratch, all by themselves?

The magic bullet in that sentence is VPN not reverse proxy

You don’t need to post it. Bots are scanning every ip, 24/7, looking for servers to infect, endpoints to abuse and data to extract.

Go set up a ssh tarpit on your server and watch the flies drown in it. I will not expose anything on my server that has so many known vulnerabilities

Your content might be legitimate, but the vast majority use Plex and Jellyfin as a media Server for pirated content and still want to share it with their friends or family. And just FYI, most blurays and DVDs also forbid this kind of sharing in their license

Because Plex handles the initial connection for you allowing the clients to lunch through CGNAT and other shit. Also they handle the authentication, which I would fully agree would be nice to have independent, but that’s the reason

They can stream content from your server or map out what you have on there by using a rainbow table. Depending on the country you live in they can and will use that combined with your IP to start litigating you

Honestly yeah. The Jellyfin Backend is basically unauthenticated for a large part, allowing anyone to map and stream your content as soon as they guessed the ids, which isn’t that hard, since they are based on the paths on your device. So if your movie sits in /mnt/media/movies/the_bee_movie that is pretty esay to guess and calculate the id from, allowing anyone to stream that content from your server

And they actively refuse to do anything about them because it would force clients to update. You could just just as well open an unsecured ftp server to your content

External servers are shared with you, they can just check which owners have libraries shared with them. That’s not some nefarious logging, its information they need to offer that function

No, I’m the kind who thinks security by obscurity is bullshit. But you do you

What? Why would I have to make my library harder to manage just because Jellyfin devs can’t get their act together? They should just start a api/v2 and secure it properly while allowing to disable the old one

Not everything you don’t like to hear comes from a bot

I am waiting for opencloud to finish its calendar implementation. The only thing I have reservations about is the fact it doesn’t use a database to store file info. Not sure I trust their approach

Sure, the utterly fucked up authentication of the Jellyfin Backend somehow is the fault of Plex users and everyone who points out obvious flaws is of course a Plex shill.

Maybe you should take a look at what you are defending here. The fact that the devs openly refuse to fix this to maintain backwards compatibility, thus endangering their users speaks a lot about the quality of the project

It’s not chance if the I’d is based on the path to your media. There’s but that much variation in the path to a certain movie and its trivial to build a rainbow table to try them out. This way unauthenticated users can not only stream from your server but effectively map your library

It’s not impossible, Far from it. The ids are not random uuids but hashes derived from the path. Since most people have a similar setup to organize their media, this gets trivial very fast

Is this a joke about duplicates on SO?

If it wanted to get my attention it should have been an error