Technology

40769 readers

286 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

coldredlight@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

Plex’s crackdown on free remote streaming access starts this week (arstechnica.com)

submitted 1 day ago by along_the_road@beehaw.org to c/technology@beehaw.org

57 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] MaggiWuerze@feddit.org 1 points 1 day ago (1 children)

The main issue there isn't the fact that these issues exist. The problem is the Jellyfin devs attitude towards them, most of these problems have been known for years (more than five in some cases) but are largely ignored. Client compatibility is valued over everything else.

There have been plenty of suggestions, ideas and even PRs, but the devs priorities don't allow for any security centered patches to get merged

[–] theangriestbird@beehaw.org 1 points 1 day ago (1 children)

idk the full history, but Joshua's comment here does not give me the impression of devs that are just deliberately ignoring security issues. It seems like they are simply balancing priorities, which is what all good devs should do. Personally I like that client compatibility is valued over everything else - I would be pissed if they broke the Fire TV client to fix a minor security hole on a niche Linux distro, because then one of my users would be SOL. And as Joshua says in that comment:

many other options are now open to us in a post-10.11 landscape now that we have a proper library database ready.

So it seems like now they are better set up to address the security issues without breaking compatibility.

[–] MaggiWuerze@feddit.org 2 points 1 day ago

There are ways to fix these issues while preserving legacy client support. And honestly I don't see how changing their database mess would help in solving security issues. In the end they'll have to change their API to a more secure one, which will definitely disrupt client support for future updates