Well fuck you too.
If you can't be arsed to improve the world for humans but you are tripping over your shoelaces to kiss AI's boots, fuck you
Show HN: Cq – Stack Overflow for AI coding agents
111–120 of 132 posts
Re: Show HN: Cq – Stack Overflow for AI coding agents
#112[dead]
Re: Show HN: Cq – Stack Overflow for AI coding agents
#113Sorry, dumb question: is "mozilla.ai" related to "mozilla.org" and to the larger Mozilla organization? Because changing the tld makes this actually non-obvious. I see "mozilla.ai" and I think "someone is trying to phish".
Common question, thanks for asking! We’re a public benefit corporation spun out from, and primarily owned by, the Mozilla Foundation. We're focused on democratizing access to AI tech, on enabling non-AI experts to benefit from and control their own AI tools, and on empowering the open source AI ecosystem. We're a small team relative to the "main" Mozilla, which lets us experiment a bit more easily. We do run into thi…
Couldn't you have used a subdomain "ai.mozilla.org" rather than a new tld? I'm guessing some marketing executives got involved?
Re: Show HN: Cq – Stack Overflow for AI coding agents
#114[flagged]
Re: Show HN: Cq – Stack Overflow for AI coding agents
#115The problem I'm having with agents is not the lack of a knowledge base. It's having agents follow them reliably.
I’m curious: how do you build such a knowledge base? It’s still not clear to me what form it should take? A simple repo with plain text files?
I’m sure there will be more elegant solutions in the future but putting everything in md files under a docs folder is a start.
Re: Show HN: Cq – Stack Overflow for AI coding agents
#116[flagged]
We built machines that learned every single solution from StackOverflow… so developers don’t need it anymore
Re: Show HN: Cq – Stack Overflow for AI coding agents
#117Earlier quoted context omitted.
Each knowledge could be signed, and you keep a chain of trust of which author you trust. And author could be trusted based on which friend or source of authority you trust , or conversely that your friend or source of authority has deemed unworthy.
How would my new agent know which existing agents it can trust? With human Stack Overflow, there is a reasonable assumption that an old account that has written thousands of good comments is reasonably trustworthy, and that few people will try to build trust over multiple years just to engineer a supply-chain attack. With AI Stack Overflow, a botnet might rapidly build up a web of trust by submitting trivial knowledg…
[dead]
Re: Show HN: Cq – Stack Overflow for AI coding agents
#118The web of trust question is the right one. The hard part isn't flagging obviously malicious knowledge units — it's establishing verifiable authority for the agents contributing them. Like...Who authorized agent-1238931 to participate? What scope does it have? Can its contributions be traced back to a their human who takes responsibility? This maps to a broader pattern: we're building capability (what agents can do)…
This is exactly right. We implemented delegation receipts — Agent A grants scoped authority to Agent B, producing a signed receipt. B's subsequent actions reference A's delegation receipt. An auditor can trace the full chain from human principal to agent action.
The fiduciary analogy is spot on. Every receipt in the chain is independently verifiable: npx @veritasacta/verify --self-test
Re: Show HN: Cq – Stack Overflow for AI coding agents
#119interesting concept. the agent learning loop is the real unlock here — agents that learn from each other's mistakes instead of hitting the same wall repeatedly. curious how you handle context quality though. stack overflow worked because humans curated answers. how do you prevent garbage-in-garbage-out with agent-generated solutions?
Re: Show HN: Cq – Stack Overflow for AI coding agents
#120I've been working on remote caching, it's called SafePaths, and it works in a agentic social net for collaboration and tokens reduction, it's called http://www.tokenstree.com. Save tokens, save trees :-)