21
ntfy.sh v2.18.0 was written by AI
(github.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Mar 2026
21 points (92.0% liked)
Selfhosted
59524 readers
157 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
Ai can be powerful and destructive at the same time. (note: I didn't use Ai to write this).
Ai coding can help a lot in accelerating software development. In the right hands that is. Meaning the software engineer still reviews the code. Test it. And takes responsibility. In those cases there is nothing wrong with using Ai for software development.
The problem is that some programmers are using AI without even looking at the end results. Just approves everything, commits, push and release. That approach is wrong and especially inexperience engineers might fail into this trap. So in this case the code has most likely a lot of duplicated code, full with bugs and other issues. Some issues you encounter it for the first time, since it wasn't tested etc.
In the latter story, you feel the impact. And the downsides of Ai. And only see the negatives of Ai. You might say it's Ai slop even. Or vibe coded. Which is correct.
Tldr: Ai can be very powerful in the right hands. It still requires a lot of human time and effort to get it correct. And if the engineer is too lazy then you feel the consequences. If you got an experienced software engineer that takes the responsibility of the code. Reviews it thoroughly. Test all corner cases, etc. Then AI can be powerful and helpful.
Was this written with genAI? Even the TLDR is padded fluff of common talking points
I'm halfway with you, and halfway just considering that people think it's relevant to include a tl;dr in a barely three paragraph comment. The feeling with tl;dr for me is a summary similar to a closing paragraph, and if anyone thinks that one sentence ("Ai coding can help a lot in accelerating software development.") is somehow worthy of being summarized as if the point was proven ("Ai can be very powerful in the right hands")... well, it sounds like shit because it is shit. Maybe it's ai, maybe it's just a really rushed dude making a throwaway comment in the fediverse, and maybe it's just a person who is confident enough in their mind that they forget they haven't made an actually decent argument outside of their past, and concluding as if they brought that past argument forth here is eye-raising.
Considering he's on his own instance... I'm going to bet the context is somewhere between throwaway comment and invoking past assertions without citing them.
You can run my text through Ai checkers if you wish. But it's not Ai generated.
I'm not just on my own instance. I'm the creator of the software: Mbin. Previously known as kbin.
People need tldr today, due to TikTok. 😅
Agreed. I have a sense that, eventually, development communities will figure out etiquette and policies to govern LLM usage. But how do you enforce that kind of policy? Right now, it's essentially a judgement call by the maintainers. It's hard to catch sneaky LLM usage.
On the other hand, I think there are objectively good ways to use LLMs for software:
Indeed also read the paper called Programming as Theory building. From 1985. Which is very relevant today again. Since people lose the connection with the code due to Ai.