If Denuvo has no negative impact on sales, what’s the need for their recent PR campaign to “rehabilitate their image”? https://feddit.nl/post/22918778

Denuvo is a deal-breaker for me.

And I can refund the game if I don’t like it. And I can see reviews of the game by those who have been vetted as having bought it.

Steam Deck support?

Oh man, you read my mind: https://github.com/jellyfin/jellyfin/pull/7663#issuecomment-1758314971. Thanks for jumping on this!

Yes, modifying the value is going to break the mappings (see https://github.com/jellyfin/jellyfin/blob/master/Emby.Server.Implementations/Localization/Ratings/us.csv). Anywho, I think we’ve discovered the root of your problem. How you choose to rectify it I leave to you! Personally, I’d recommend suffixing your filenames with [tmdbid-123456] as per https://jellyfin.org/docs/general/server/media/movies/ and letting themoviedb.org handle it all for you.

https://github.com/jellyfin/jellyfin/blob/31aa44d23d12b5dbb5f9a131242cc82c9ef98f24/Emby.Server.Implementations/Data/SqliteItemRepository.cs#L2279 is what’s discovering similar content. If the InheritedParentalRatingValue is considered zero, it’s only going to match other content with the same value. Can you elaborate on “I did change the name of the key for the rating variable in the metadata to be ‘MPAA rating’ instead of the default which I think was ‘rating’ before since I found it confusing.”? I suspect we’re zeroing (ha ha) in on the problem.

Hey, I’ve worked in the recommendations/similarity calculations. Could you post a screenshot of the detail page for Inside Out? I suspect your media doesn’t have associated metadata (e.g. tmdb tags) that are used to power similarity calculations.

Likewise. Debian, installed Steam, updated my graphics driver, and everything runs smoothly. I’m surprised how well Linux gaming has come along!

I suspect the difficulty the publishers face is that fun is difficult to quantify. The read on this might end up being “All things being equal, DRM/MTX/etc aren’t statistically impediments to financial success if the game is going to sell well anyway. If we percieve them to improve our bottom line, let’s include them”.

Getting the code running, easy. Getting the pull requests moved forward, a lot more frustrating than expected.

https://lemmy.ca/post/6420647 summarizes my feelings on the latter.

I got a bunch of commits in around searching and similarity. https://github.com/jellyfin/jellyfin/pulls?q=is%3Apr+author%3Abradbeattie+is%3Amerged, https://github.com/jellyfin/jellyfin-web/pulls?q=is%3Apr+author%3Abradbeattie+is%3Amerged.

In some cases, PRs that have no merge conflicts can sit and languish for months on end. Example: https://github.com/jellyfin/jellyfin/pull/8914. I’m not suggesting cavalierly accepting all PRs, but the devs could do a better job of communicating with prospective contributors. My desire to contribute to Jellyfin was somewhat dampened by that initial experience.

Edit: To be more constructive, I’d recommend not just a call to action (the blog post), but explicitly reaching out to devs who submitted their first PRs within the past year and finding out what their experiences were. Discovering a leaky onboarding process that you lose potential devs through could be instrumental!