Ask HN: Share your vibe coded project

A couple I've done lately:

- UDP777 - a simple UDP pager in Go: https://www.udp7777.com/

  Estimated: 2 days of work

- FIPSPad - a simple Notepad app with encryption-at-rest that only runs if your system is FIPS-compliant in Rust: https://fipspad.browserbox.io

  Estimated: 2 days of work

- A suite of AI-written alternative HN front pages (serious joy and laughs): https://dosaygo-studio.github.io/hn-front-page-2035/

  Estimated: 10 - 15 minutes work each. Total 1 - 2 hours of work, plus posting to HN and reading and replying to comments.

- A full auto-updating static interactive archive of HN with various queries and new views: https://hackerbook.dosaygo.com

  Estimated: 4 days of work

- A "most cited" HN-ecosystem ranking of topics that span multiple discussions over time ranked by the topics whose discussions/comments were most cited by other HN comments: https://hacker-backlinks.browserbox.io/

  Estimated: 3 - 4 hours of work

- A game where you have to do mental math for hexadecimal crossword puzzles: https://do-say-go.github.io/hexfiend/?hn=2

  Estimated: 1 day of work ~ 3 - 4 hours of work

- A game where you factor RSA semiprimes by doing constraint propagation on a guessable tableaux: https://do-say-go.github.io/insights/

  Estimated: 6 days of work

- BlueDot - a universal cloud-console TUI that lets you search, compare and rent VPS across 6 clouds (GCP, Hetzner, AWS, Azure, Digital Ocean and Vultr), right from your terminal: https://tui.bluedot.ink

  Estimated: 4 days of work

- An implementation of an idea I had from 2013, an "approximate matching" LZW algorithm: https://github.com/BrowserBox/LZW-X

  Estimated: (my own thinking - weeks over years), coding: 2 days of work

- An email-bridge for your CLI AI agents to let your drive them from email while you're out, leaving your laptop at home: https://ai-chat.email

  Estimated: 12 days of work (so far)

- A little open-source tool to mute your macOS mic to zero as well as detect Siri listening overrides and open settings so you can toggle: https://github.com/BrowserBox/NoSpy

  Estimated: 1 hour of work

- A set of AI "taste & doctrine" files to teach your agents code that belongs and give them procedures for checking semantics for quality, or case-by-case human overrides, to keep codebases higher quality and more maintainable, rather than just ensuring syntax parses: https://ai-lint.dosaygo.com

  Estimated: 3.5 hours of work

- git-prime - mine git commit hashes for large primes by fuzzing a nonce annotation in the message: https://textonly.github.io/git-prime/

  Estimated: 1 hour of work

- prime news - a view of all of HN that only selects items with an ID which is a prime number: https://dosaygo-studio.github.io/prime-news/

  Estimated: 2 days of work

- A visual proof of the Pythagorean theorem that let's you play with the "squares to triangles to bigger square" mapping: https://do-say-go.github.io/insights/others/interactive_peri...

  Estimated: 1 day of work

- An impressionistic Windows 98 desktop called Windows 98½ with real Web Browsers: retro UI wrapper around BrowserBox using the new BrowserBox WebView Embedding API - a showcase for my corporate work and a cool 90s tech nostalgia art project in one, what could be better! :)

  Estimated: 5 - 6 weeks of work for the Desktop (over the last 1 - 2 years), and 7 years of work for BrowserBox (rn > 90% pre-AI).

- Structropy - Towards a metric of organization. An adaption of qualities of the metric of Shannon entropy toward not just "surprise" but strucutre, to try to fill the gap that Shannon leaves where "highly random" is "high information" but "low organization". Loosely based on expected sorting time of new inserts. https://github.com/DOSAYGO-STUDIO/structropy

  Estimated: months of thinking over years, then 1 - 2 days of coding

And a few more even bigger ones. And that's just the last 3 months!

I disagree. It's interesting to see what sorts of tiny problems people had and solved. The code is less important than the problem itself. A bit like duct-taping a solution in your garage for an hyper-specific issue in your house.

Same. We have a very similar use case then. Did it handle user flows well? I'm talking about account validation, deactivation and recovery.

Or better, if the code is on GitHub, I would love to have a look.