Selfhosted

60281 readers

388 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

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

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

366

ntfy.sh v2.18.0 was written by AI (github.com)

submitted 3 months ago* (last edited 3 months ago) by ueiqkkwhuwjw@lemmy.world to c/selfhosted@lemmy.world

186 comments fedilink hide all child comments

According to the release:

Adds experimental PostgreSQL support

The code was written by Cursor and Claude

14,997 added lines of code, and 10,202 lines removed

reviewed and heavily tested over 2-3 weeks

This makes me uneasy, especially as ntfy is an internet facing service. I am now looking for alternatives.

Am I overreacting or do you all share the same concern?

you are viewing a single comment's thread
view the rest of the comments

[–] patrick@lemmy.bestiver.se 95 points 3 months ago (4 children)

It looks like that tool is more or less built by a single developer (you already trust their judgment anyways!), and even though the code came through in a single PR it was a merge from a branch that had 79 separate commits: https://github.com/binwiederhier/ntfy/pull/1619

Also glancing through it a bit, huge portions of that are straightforward refactors or even just formatting changes caused by adding a new backend option.

I'm not going to say it's fine, but they didn't just throw Claude at a problem and let it rewrite 25k lines of code unnecessarily.

[–] fccview@lemmy.world 3 points 3 months ago

Yeah, I mean, with or without AI, I've always only had a big pull request for releases, from a stable release branch into the main branch, the release branch would be a merge of various branches or just be worked on directly on various stages.

One big pull request doesn't really mean anything.

[–] prenatal_confusion@feddit.org -1 points 3 months ago

Wow a differentiated opinion on AI use :)

[–] sloppy_diffuser@sh.itjust.works -1 points 3 months ago (1 children)

Something like https://graphite.com/ to create stacked PRs that are reviewable probably would have helped. Can be replicated with local LLMs or remote AI providers with locally configured agentic workflows. Never used graphite personally, but I've seen some open source maintainers use it to split up large PRs.

[–] johntash@eviltoast.org 1 points 3 months ago

Huh, I was wondering how rrds would help..