are - Moozonian Search

news.ycombinator.com• Jul 29, 2026• 1 min read

Ask HN: What have you been curious about?If you are anything like me, you will have about five answers at any given point in time for "What are you curious about?".Arguably, a more interesting, revealing, and kinder question is; "What have you been curious about?".I feel a looking-back-to-curiosity exercise has power to shed light on where to look ahead (and why to do it). More so, I feel it has power to grant permission to that "insatiably curious thirteen year old self" to step out and play. Because it probably already has been up to something, while your attention was elsewhere.So, here is a prompt (see what I just did there? ;-))Um... Except for LLM stuff, if you please. Just for this thread. Because these days the plurality of HN discussion appears to be about the curiosities of LLMs.(cf. More about this in a blog post I published a while back https://www.evalapply.org/posts/what-have-you-been-curious-about/ )

supapool.io• Jul 29, 2026• 1 min read

Show HN: Supapool – a Supabase per coding agent in ~400 mshi HN,I built supapool.io, an ephemeral full copy of supabase's services that you can spin up in ~400 ms (Auth, postgres, storage, realtime).so if you run multiple coding agents in parallel in different worktrees, they can now have their own copy of supabase without making changes that conflict with eachother.> why not use supabase docker locally?when I run 3-4 instances locally, my macbook gets hot and sometimes freezes.> why not use supabase branches?branches take minutes to setup, and are designed for persistence. this is expensive, and for a dev environment, it is too slow.> why not use mocks?mocks are bad for agents. i expect agents to test their migrations, SQL against real prod service behavior. agents hallucinate working mocks often. However, upside of mocks is that its faster and runs locally, but with supapool, the upside is less convincing.> how does it work/how is this economically viable?starting supabase in 400ms requires a few things: 1. a pool of ready supabase instance

achiever.so• Jul 29, 2026• 1 min read

Show HN: Steam-style achievements, but for real life (777 milestones)For about 10 years I kept notes about things I wanted to do or already did. The notes never became anything useful, so this winter I started turning them into an app.It's not a habit tracker, it's a discrete-event tracker: 777 one-time milestones in 14 life categories (fitness, career, travel, finances, learning, mental health, etc.), each worth 5-100 points depending on difficulty. No streaks, no daily check-ins. You did it once, it counts forever.Two design decisions people argue with me about:1. I built streaks early, then hid the whole feature. Streaks push you to repeat things, but this app is about finish lines. They worked against each other, so streaks had to go.2. Profiles are public by default (it's a social tracker), but 31 achievements about addiction, therapy and mental health never show on public profiles unless you opt in. This is done with row-level security in Postgres, not filtered on the client. So you can track quitting nicotine and your profile won't announce it. T

wingman.actor• Jul 29, 2026• 1 min read

Show HN: Wingman – A client-agnostic agent harness (written in Go)Hey HN! This is a project I've been working on for a while, it's still rough around the edges but I wanted to share it and hopefully get some feedback. Wingman is a client-agnostic agent harness (written in Go). Client-agnostic means Wingman isn’t coupled to any specific problem (like a coding agent or answer engine). It’s a portable agentic runtime that lets you build arbitrary clients on top of it.So you can build a client to:- Write code- Perform automatic triage- Classify emails- Review a PRand any other LLM adjacaent problem. There are surely features that exist that aren't well documented, a bunch of small bugs/race conditions, and all kinds of things I am hoping to add in the near future so any feedback is appreciated.