I’m actively working on building something for this. In the interim, most phones have something akin to a voice recorder with transcriptions.
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!
Its the same “power corrupts” story again and again. Karina Gould gave an impassioned speech on electoral reform (http://www.ourcommons.ca/DocumentViewer/en/42-1/house/sitting-64/hansard#Int-8963139). But after replacing Maryam Monsef as Minister of Democratic Institutions, her views suddenly became far more simplistic. In a 2017 interview on CBC’s Metro Morning, she was asked “Why is it important that people at the very least believe every vote counts?”. She replies “Because they do. … We literally count them: 1, 2, 3, 4, up to the majority that wins.”
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 [
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.
In addition, theatres advertise a starting time of X:00, but the movie can sometimes start as late as X:30 after 30 fucking minutes of ads and trailers. That was my previous and last experience in a theatre.
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.
https://serratus.github.io/quaggaJS/ and whatnot exist. Any reason why such an approach couldn’t be taken?
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.
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!
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?