My Steam Deck convinced me to try Linux (Debian) a try for desktop gaming. So long as you install the latest GPU drivers, it’s smooth as butter. I guess what I’m saying is Linux for everything at this point… for those capable of installing drivers from the CLI.

Dug up the paper in question for anyone curious: https://sci-hub.se/https://www.science.org/doi/10.1126/science.aaq0216. At a cursory glance, I’m not seeing any of the referenced concerns. But, y’know, down vote away I guess.

Following the trail of your comment: https://ourworldindata.org/land-use-diets does indeed cite https://www.science.org/doi/10.1126/science.aaq0216, but I’d love it if you could provide more details on your criticisms of methodology.

If the camera really does need to be that thick for lens reasons, couldn’t we at least make the rest of the body bigger with more battery?

I’m actively working on building something for this. In the interim, most phones have something akin to a voice recorder with transcriptions.

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!

If only https://en.m.wikipedia.org/wiki/United_States_v._Paramount_Pictures,_Inc. was expanded to streaming services instead of repealed.

Take a read through https://en.m.wikipedia.org/wiki/United_States_v._Paramount_Pictures,_Inc.

Real shame this was terminated rather than extended to streaming platforms.

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.

I’d recommend considering how the recently expired https://en.m.wikipedia.org/wiki/United_States_v._Paramount_Pictures,_Inc. would have applied to streaming services.

Or https://en.m.wikipedia.org/wiki/Zero-width_space ? But seriously, just use unique random strings likely through a password manager.

https://ourworldindata.org/environmental-impact-milks and https://ourworldindata.org/grapher/environmental-footprint-milks

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!