Developer Redirects His AI-Built App to Original Creator After Discovering It Copied a Bug
Mea Culpa – Dark Hours
Terry Godier launched a web utility called Dark Hours, only to discover it was strikingly similar to an existing open-source project, DarkHours.app, even reproducing a bug the original developer had fixed. After a public exchange on Bluesky, Godier redirected his domain to the original creator, abandoned plans for an iOS app, and apologized for his irresponsible use of AI in building the project without checking for similarities.
That’s on me, and I am responsible for what I published.
- user43928
On the previous HN posts I got this impression:
The developer's astrology app containing tarot reading features was rejected from Apple's App Store that prohibits astrology apps.
He then replaced the app's content with a clone of, if not the identical open source astronomy app "Dark Hours", copying even the name. The original is here: https://darkhours.app
The developer was then in contact with John Gruber, who wrote an article claiming Apple's reviewers confuse a nice, scientific astronomy app with astrology. The developer reviewed the article before publication.
It then turned out that the developer forgot to mention that originally he did upload an astrology app for review. Gruber felt duped, and noted that it's unclear whether an updated build containing the new astronomy app was ever submitted to Apple for review: https://daringfireball.net/2026/08/retraction_app_store_reje...
Now the developer seems to claim that he merely accidentally cloned that open source app when working with Claude.
I am not buying it.
- InsideOutSanta
Something went seriously wrong there, and I'm not sure it's just Claude copying an existing project bug-for-bug. For more context, see also this post from Gruber at Daring Fireball:
https://daringfireball.net/2026/08/retraction_app_store_reje...
- chuckadams
Yeah, the big bad AI made you plagiarize a whole project down to the name, and lie to everyone about the review process. Not buying any of it.
- cube00
It's not much of a mea culpa when there's not even a mention, let alone an apology, for misleading John Gruber.
- pohl
Fun and useful PR jargon to describe what this post smells like: a “limited hangout”.
(a damage-control strategy where an organization or individual admits to a portion of a secret or scandal after a cover story fails, while still hiding the most damaging key facts.)
- mechanicum
I’d love to see the other repo, and the prompts that led to both.
Did Godier copy the other guy’s repo, name and all, and try to pass it off as his own work? That seems like the obvious conclusion, albeit brazen to the point of insanity.
Did Claude copy the repo, in response to a prompt? If Claude copies a Claude vibe-coded project, can any plagiarism really be said to have taken place?
Or is this just what Claude is statistically likely to spit out if you prompt it to build an astronomy app and leave it to it?
- mark_l_watson
He did the right thing. The very idea of Claude copying an existing project to answer one of my prompts or a whole project in Claude Code is a nightmare scenario.
I have all but given up using the multiple trillion weight models in favor of smaller open weight models that have hopefully abstracted away copyrightable details. Right now deepseek-v4-flash-0731 seems usually perfect for my needs.
I saw Cees de Groot post about LLM vibe coded projects containing all sorts of licensed material, and I think he is correct.
Perhaps another good reason to just use the AGPL for new projects? I decided to use the AGPL for may latest fun project https://github.com/mark-watson/racket-coding-agent (personal AI coding harness written for my own use in Racket Scheme). Everything I do is open source or open content books, so I am happy to have everything I do to be used by humans and also for AI training, however: it is scary to by mistake be in the position of not acknowledging other work when appropriate.
- moritzwarhier
> While I had genuinely never seen DarkHours.app before yesterday, I was careless in relying on AI to generate the project without doing the work to understand whether it closely resembled an existing project. That’s on me, and I am responsible for what I published.
Super-convincingly phrased, but after skimming how this unfolded without knowing the author, it could just as well be the inference result of
Write a convincing apology and defence regarding this blog post <url> / bsky thread <url>
I was totally caught off guard and making an honest, altruistic effort here!