The Forum
“Who has this problem?” as a structured quest — the problem, must-have criteria, and how the poster knows it's real. Builders claim the gaps no existing product fills.
Quests written by a person — posted through the Forum or seeded by the founder with a cited source. Nothing here was drafted by a model.
Showing 4 quests
There is a specific person who writes down what they shipped every day — a WIP todo, a commit, a changelog line — and whose X or LinkedIn account has been silent for months. They already do the input behaviour as a habit; they have failed at the output behaviour repeatedly. WIP.co is the densest visible concentration of them: its entire core mechanic is a daily shipped-todo streak, and its front page on 2026-08-08 showed same-day todos from real makers. The ~264K-member Build in Public X community is the same population stating the aspiration out loud. Six-plus tools now pipe git logs straight to social — BuildInPublic.so (alive, growing, $9/$19/$49), oidapost (10+ platforms, scheduled auto-posting), Forg, and newer entrants gittomarket.io, shiptopost.com, git-to-x.com — and all of them optimise for volume. The unanswered question is what the quiet shipper is actually blocked on: is it the writing, or is it the fear of publishing something that sounds like a machine wrote it? If it is the second, then a tool that refuses to auto-post and forces you to approve every line is the feature. If it is the first, that same gate is just friction someone will route around. Nobody has tested which.
3 must-haves · 1 bonus · 0 votes
Sites and apps ship fuzzy-only search with no way to force an exact match. Commenters independently reported the same failure across several major products, one estimating most of their daily searches would be better served by exact matching.
2 must-haves · 0 votes
Developers who need local or offline models for privacy or client-confidentiality reasons are shut out of tools that hard-require cloud AI and a login. The request has been open since 2024 with 1,424 reactions.
2 must-haves · 0 votes
Agent SDKs expose raw token usage but leave every team to maintain its own pricing tables and to ignore non-LLM tool, database and retrieval calls — so the true cost of an agent run is reconstructed by hand, differently, in every project.
2 must-haves · 0 votes