Re:ZapFast: A fast, native WhatsApp client in Rust and egui
by zerr on Sunday November 08, 2026 @07:14AM
(#50412596)
For any vibe-coded open-source project, shouldn't the prompt history and token costs be published as well?
[ Parent
| on HN ]
Re:ZapFast: A fast, native WhatsApp client in Rust and egui
by arjie on Sunday November 08, 2026 @07:30AM
(#50412697)
What purpose would that serve? You have the source code. In the old days we’d just share tarballs. No provenance. It’s fine. You have the unit of legible modifiability.
In the early days of AI coding someone did publish the prompts and it was utterly useless to me https://github.com/i365dev/LetterDrop
The source code itself is a sufficient prompt.
Re:ZapFast: A fast, native WhatsApp client in Rust and egui
by saghm on Sunday November 08, 2026 @09:46AM
(#50413792)
There have definitely been times when I've cloned repos that were vibed, pointed my own agent at it, and then hacked up whatever changes I've wanted. I don't think there's been a single time that a lack of prompts has caused any issues, but there have been at least a few times where stuff like AGENTS.md checked into the repo has caused hiccups from them encoding stuff that conflicts with how I want things done.