Yes, no (built-in) AI is now a feature
-
To be clear, GPT's suggestion to drain input from the server side of the socket was the actual solution. My code worked completely after that.
The suggestion to avoid partial writes was a sound one. I was under the mistaken impression that Java does its own retrying and partial writes therefore can't happen. But this was not the real problem; it was only incidental.
@argv_minus_one @grvsmth @wobweger @moskitokoenig
My agent's response was a bit too long for here (they talk and talk and talk....)
https://gist.github.com/worikgh/7991845fca528436d158df081dbb98fa
I hope that works, I do not often use GitHub gisttl;dr: The root cause: a single blocking socket.write() call on an interrupted thread
My Java is weak, but the analysis it gave makes sense in general terms
-
@argv_minus_one @grvsmth @Garonenur @wobweger @moskitokoenig
> Yes, and that's the hard part of programming anyway.
> I don't need help writing code. I have perfectly serviceable hands and keyboard with which to do so.
This is where I urge you to try.
The AI agents are very good at assembling the boiler plate, then, with guidance, honing that into useful artefacts
https://kerkour.com/open-source-golden-age-ai by Sylvain Kerkour is an interesting read on this
That site doesn't work without JavaScript, so I'm gonna pass on reading it.
Anyway, if you have a boilerplate problem, then you need macros, not AI. Macros are reliable and maintainable; vast volumes of repetitive code, whether AI-generated or copy-and-pasted, are not.
-
@argv_minus_one @grvsmth @wobweger @moskitokoenig
My agent's response was a bit too long for here (they talk and talk and talk....)
https://gist.github.com/worikgh/7991845fca528436d158df081dbb98fa
I hope that works, I do not often use GitHub gisttl;dr: The root cause: a single blocking socket.write() call on an interrupted thread
My Java is weak, but the analysis it gave makes sense in general terms
Nope, that's a fail.
The thread gets interrupted after 30 seconds, but ECONNRESET happens instantaneously.
Partial writing didn't happen.
The interrupt is intentional and not optional. The server is intended to only run for 30 seconds—long enough for the user's browser to start up and fetch the page—and then shut down, which is what the interrupt achieves.
The interrupt also prevents malicious clients from holding open a connection indefinitely.
-
That site doesn't work without JavaScript, so I'm gonna pass on reading it.
Anyway, if you have a boilerplate problem, then you need macros, not AI. Macros are reliable and maintainable; vast volumes of repetitive code, whether AI-generated or copy-and-pasted, are not.
@argv_minus_one @grvsmth @Garonenur @wobweger @moskitokoenig
https://worik.org/gist.html from pandoc on the original https://worik.org/gist.md
-
Nope, that's a fail.
The thread gets interrupted after 30 seconds, but ECONNRESET happens instantaneously.
Partial writing didn't happen.
The interrupt is intentional and not optional. The server is intended to only run for 30 seconds—long enough for the user's browser to start up and fetch the page—and then shut down, which is what the interrupt achieves.
The interrupt also prevents malicious clients from holding open a connection indefinitely.
The bot is correct that the serveThread fails to catch InterruptedIOException. I hadn't added that yet, but it is there in the production code.
And the bot is correct that partial writes aren't being handled properly.
But that's it. The bot has failed to correctly explain what's happening, failed to fix the bug, and introduced a security vulnerability. And it did so with the utmost confidence.
-
Yes, no (built-in) AI is now a feature
https://blog.documentfoundation.org/blog/2026/09/03/yes-no-ai-is-now-a-feature/
@libreoffice God bless y'all
️ -
@argv_minus_one @wobweger @libreoffice @grvsmth @moskitokoenig That is what generative AI is useful for.
It is very good at generating computer code and will vastly increase the quality of what professional programmers can produce.
That is my experience
@worik @argv_minus_one @wobweger @libreoffice @grvsmth @moskitokoenig That is not what generative AI is useful for.
It is very good at destroying people, many social contracts, our ability to think, our ability to create, our resources, our environment, all while creating absolute crape no one wants and shoving it to everybody's face, surrendering ourselves to fascist tech giants, and allowing plenty of fascist to be smug about it.
That is my experience.
-
@argv_minus_one @wobweger @libreoffice @grvsmth @moskitokoenig
Have you tried using a coding agent in a suitable domain? (They are not original, they are thorough)
@worik @argv_minus_one @wobweger @libreoffice @grvsmth @moskitokoenig I don't need to try shooting at people with a gun to know it's bad.
-
@argv_minus_one @grvsmth @Garonenur @wobweger @moskitokoenig
I think the point, Greg's in the video, and mine here, is these are tools and need to be wielded. Careless use has bad results
Careful use increases the reach of the user
@worik
https://deadsimpletech.com/blog/no-such-thing-as-just-a-tool
By @iris_meredith
https://tante.cc/2026/04/21/ai-as-a-fascist-artifact/
By @tanteSomewhere in this discussion drug dealers get mentioned.
All of the people trying to convince me to use AI sound like addicts trying to sell me drugs so they can justify their own (mis-) use.
And I *hate* drugs of any kind. -
Yes, and that's the hard part of programming anyway.
I don't need help writing code. I have perfectly serviceable hands and keyboard with which to do so.
It would be helpful if AI could reason about code and invent a novel solution to the problem at hand…but if it can do that, then it also can, and probably will, go full Skynet and kill us all.
@argv_minus_one @worik
The creation of code was never the bottleneck anyway -
@cosmin @argv_minus_one Ah, another high-quality Mastodon discussion. Again: No core developers use LLMs. We rely on contributions from the wider community and don't explicitly list tools people can't use – but we do require people disclose when they use LLMs and generally discourage the practice. We carefully review submissions by contributors to make sure the code quality is good and that the patch author understands their own code. LLMs are prohibited for students. That is not "slop".
@libreoffice @cosmin @argv_minus_one although I disagree with Libreoffice's LLM policy, it's still better than debian. I appreciate that Libreoffice's stance on AI features, and I also appreciate that Libreoffice exists.
-
@argv_minus_one @worik
The creation of code was never the bottleneck anyway@Garonenur @argv_minus_one @worik @wobweger @moskitokoenig This is a great post, thanks!
-
@worik @argv_minus_one @wobweger @libreoffice @grvsmth @moskitokoenig I don't need to try shooting at people with a gun to know it's bad.
Indeed. Because we've observed what happens to other people who are shot with a gun.
Some people, however, seem incapable of learning from the misfortunes of others. Not sure why, but it's terribly harmful to them and to society as a whole.
-
@libreoffice Nice. Here in Norway, we've been doing the no (built in) AI features too: https://vivaldi.com/blog/keep-exploring/
@brucelawson @libreoffice thank goodness. saves me having to build my own browser.
-
Yes, no (built-in) AI is now a feature
https://blog.documentfoundation.org/blog/2026/09/03/yes-no-ai-is-now-a-feature/
@libreoffice@fosstodon.org this is so performative. stop allowing ai code contributions.
-
Yes, no (built-in) AI is now a feature
https://blog.documentfoundation.org/blog/2026/09/03/yes-no-ai-is-now-a-feature/
@libreoffice I feel it's how "without poison food" (organic) came to existence : and it's depressing.
-
@Jeff None of the core developers use them. We rely on contributions from the wider community and don't explicitly list tools people can and can't use – but we do require people disclose when they use LLMs and generally discourage the practice. We carefully review submissions by contributors to make sure the code quality is good and that the patch author understands their own code. LLMs are prohibited for students and other mentored work.
LLMs are prohibited for students and other mentored work.
This is good. Kudos. Nobody will learn anything otherwise.
-
Yes, no (built-in) AI is now a feature
https://blog.documentfoundation.org/blog/2026/09/03/yes-no-ai-is-now-a-feature/
@libreoffice cc @mozilla , you might want to read this one...
-
@libreoffice so you're telling me that libreoffice is "Zuzai"? (https://zuzai.org)
congrats!!
@parrot @libreoffice I like making words myself, but I have questions.
You mention it is an acronym. What is an acronym for?
When you present a new word, you need to very clear from the getgo what the origin of the word is, what images it leans upon, what meaning you attribute to it. If you don't do this, then the word is going to end up being superficial.
-
@parrot @libreoffice I like making words myself, but I have questions.
You mention it is an acronym. What is an acronym for?
When you present a new word, you need to very clear from the getgo what the origin of the word is, what images it leans upon, what meaning you attribute to it. If you don't do this, then the word is going to end up being superficial.
@parrot @libreoffice
I would drop the part of whether the word is an acronym, retronym.Do not bring up widespread adoption, future will reveal itself anyways.
Should we be clear what we mean by AI? No, let people judge by themselves what they consider AI, let language live it's life.
Using an existing word? Or using loanwords? Good question, but this just reveals hesitation about your word. You should not hesitate if you are serious.
The text oozes with hesitation. Not a good sign.
