Live data from Hacker News

Jellyfin LLM/"AI" Development Policy

jellyfin.org

41–50 of 112 posts

Re: Jellyfin LLM/"AI" Development Policy

#41
post #10

Earlier quoted context omitted.

Although: "An exception will be made for LLM-assisted translations if you are having trouble accurately conveying your intent in English."

I am quite obviously blind, but I still stand by my sentiment. I would rather have a "bad" but honest PR body than a machine translated one where the author isn't sure about what it says. How will you know if what it says is what you meant?

突然出現一大段外文文字會讓很多人感到反感。即使不能百分之百確定翻譯準確,大多數使用者仍然更傾向於將其翻譯成英語。

Re: Jellyfin LLM/"AI" Development Policy

#42

Earlier quoted context omitted.

I’m glad they have a carve out for using LLMs to translate to, or fix up English communications. LLMs are a great accessibility tool that is making open source development truly global. Translation and grammar fix up is something LLMs are very, very good at! But that is translation, not “please generate a pull request message for these changes.”

Better to use Google Translate for this than ChatGPT. Either ChatGPT massively changes the text and slopifies it, or people are lying about using it for translation only because the outputs are horrendous. Google Translate won't fluff out the output with garbage or reformat everything with emoji.

"Translate this from X to X, don't change any meaning or anything else, only translate the text with idiomatic usage in target language: X"

Using Google Translate probably means you're using a language model in the end anyways behind the scenes. Initially, the Transformer was researched and published as an improvement for machine translation, which eventually led to LLMs. Using them for translation is pretty much exactly what they excel at :)

Re: Jellyfin LLM/"AI" Development Policy

#43

Earlier quoted context omitted.

I’m glad they have a carve out for using LLMs to translate to, or fix up English communications. LLMs are a great accessibility tool that is making open source development truly global. Translation and grammar fix up is something LLMs are very, very good at! But that is translation, not “please generate a pull request message for these changes.”

Better to use Google Translate for this than ChatGPT. Either ChatGPT massively changes the text and slopifies it, or people are lying about using it for translation only because the outputs are horrendous. Google Translate won't fluff out the output with garbage or reformat everything with emoji.

Yep. If you don't know the language, it's best not to pretend you do.

I've done this kind of thing, even if I think it's likely they speak English. (I speak zero Japanese here.) It's just polite and you never know who's going to be reading it first.

> Google翻訳を使用しました。問題が発生した場合はお詫び申し上げます。貴社のウェブサイトにコンピュータセキュリティ上の問題が見つかりました。詳細は下記をご覧ください。ありがとうございます。

> I have found a computer security issue on your website. Here are details. Thank you.

Re: Jellyfin LLM/"AI" Development Policy

#44
post #39

Earlier quoted context omitted.

No, I think GP means grammar fixes to your own communication. For example if I don't speak Japanese very well and I want to write to you in Japanese, I might write you a message in Japanese, then ask an LLM to fix up my grammar and check my writing to make sure I'm not sounding like a complete idiot.

I have read a lot of bad grammar from people who aren't very good at the language but are trying their best. It's fine. Just try to express yourself clearly and we figure it out. I have read text where people who aren't very good at the language try to "fix it up" by feeding it through a chat bot. It's horrible. It's incredibly obvious that they didn't write the text, the tone is totally off, it's full of obnoxious C…

You seem to be judging business communications by weird middle-class aesthetics while the people writing the emails are just trying to be clear.

If you think that every language level is always sufficient for every task (a fluency truther?), then you should agree that somebody who writes an email in a language that they are not confident in, puts it through an LLM, and decides the results better explain the idea they were trying to convey than they had managed to do is always correct in that assessment. Why are you second guessing them and indirectly criticizing their language skills?

Re: Jellyfin LLM/"AI" Development Policy

#45

I think at some point we will need a "PEP-8" for LLM / AI code contributions document that is universally reusable and adoptable per project, call it an "Agent Policy" or what have you, that any agent worth its Salt should read before touching a codebase and warn the user that their contributions might not be accepted or what have you, depending on project policy, just like we have GPL, BSD, MIT, etc it would probabl…

> that any agent worth its Salt should read before touching a codebase and warn the user that their contributions might not be accepted

Are you talking about some agent that is specific for writing FOSS code or something? Otherwise I don't see why we'd want all agents to act like this.

As always, it's the responsibility of the contributor to understand both the code base and contributing process, before they attempt to contribute. If they don't, then you might receive push-back, or have your contribution deleted, and that's pretty much expected, as you're essentially spamming if you don't understand what you're trying to "help".

That someone understands this before contributing, is part of understanding how FOSS works when it's about collaborating on projects. Some projects have very strict guidelines, others very lax, and it's up to you to figure out what exactly they expect from contributors.

Re: Jellyfin LLM/"AI" Development Policy

#46
I very much like the no LLM output in communication. Nothing is worse than getting huge body of text the sender clearly hasn't even read. Then you either have to ignore it or spend 15 minutes explaining why their text isn't even relevant to the conversation.

Sort of related, Plex doesn't have a desktop music app, and the PlexAmp iOS app is good but meh. So I spent the weekend vibe coding my own Plex music apps (macOS and iOs), and I have been absolutely blown away at what I was able to make. I'm sure code quality is terrible, and I'm not sure if a human would be able to jump in there and do anything, but they are already the apps I'm using day-to-day for music.

Re: Jellyfin LLM/"AI" Development Policy

#47

> LLM output is expressly prohibited for any direct communication I would like to see this more. As a heavy user of LLMs I still write 100% of my own communication. Do not send me something an LLM wrote, if I wanted to read LLM outputs, I would ask an LLM.

yeah, you could ask a LLM, but are you sure you know what to ask?

like in that joke with the mechanic which demands $100 for hitting the car once with his wrench

Re: Jellyfin LLM/"AI" Development Policy

#48
post #39

Earlier quoted context omitted.

I have read a lot of bad grammar from people who aren't very good at the language but are trying their best. It's fine. Just try to express yourself clearly and we figure it out. I have read text where people who aren't very good at the language try to "fix it up" by feeding it through a chat bot. It's horrible. It's incredibly obvious that they didn't write the text, the tone is totally off, it's full of obnoxious C…

You seem to be judging business communications by weird middle-class aesthetics while the people writing the emails are just trying to be clear. If you think that every language level is always sufficient for every task (a fluency truther?), then you should agree that somebody who writes an email in a language that they are not confident in, puts it through an LLM, and decides the results better explain the idea they…

Running your words through ChatGPT isn't making you clear. If your own words are clear enough to be understood by ChatGPT, they're clear enough to be understood by your peers. Adding ChatGPT into the mix only ensures opportunity for meaning to be mangled. And text that's bad enough as to be ambiguous may be translated to perfectly clear text that reflects the wrong interpretation of your words, risking misunderstandings that wouldn't happen if the ambiguity was preserved instead of eliminated.

I have no idea what you're talking about with regard to being a "fluency truther", I think you're putting words into my mouth.

Re: Jellyfin LLM/"AI" Development Policy

#49
In other words, you are responsible for the code you submit (or cause to be submitted via automated PRs), regardless of how fancy your tools are.

That said I understand calling it out specifically. I like how they wrote this.

Related:

> https://news.ycombinator.com/item?id=46313297

> https://simonwillison.net/2025/Dec/18/code-proven-to-work/

> Your job is to deliver code you have proven to work

Re: Jellyfin LLM/"AI" Development Policy

#50

Earlier quoted context omitted.

I’m glad they have a carve out for using LLMs to translate to, or fix up English communications. LLMs are a great accessibility tool that is making open source development truly global. Translation and grammar fix up is something LLMs are very, very good at! But that is translation, not “please generate a pull request message for these changes.”

Better to use Google Translate for this than ChatGPT. Either ChatGPT massively changes the text and slopifies it, or people are lying about using it for translation only because the outputs are horrendous. Google Translate won't fluff out the output with garbage or reformat everything with emoji.

[deleted]
Post reply on HN