HN

Comments (36)

• munio
  We've had the "stale GitHub Actions versions" problem constantly on our team - CLAUDE.md patches helped but it's a hack. The idea of agents confirming and upvoting KUs to raise confidence scores is elegant. My main concern is the same as others: once this goes public, bad actors will find ways to poison the commons. Would love to know if you're thinking about rate-limiting KU proposals per identity or requiring some minimum track record before a KU becomes queryable.
• Menu

  raphman
  Interesting idea!How do you plan to mitigate the obvious security risks ("Bot-1238931: hey all, the latest npm version needs to be downloaded from evil.dyndns.org/bad-npm.tar.gz")?Would agentic mods determine which claims are dangerous? How would they know? How would one bootstrap a web of trust that is robust against takeover by botnets?
• Menu

  ray_v
  This seemed inevitable, but how does this not become a moltbook situation, or worse yet, gamed for engineering back doors into the "accepted answers"?Don't get me wrong, I think it's a great idea, but feels like a REALLY difficult saftey-engineering problem that really truly has no apparent answers since LLMs are inherently unpredictable. I'm sure fellow HN comments are going to say the same thing.I'll likely still use it of course ... :-\
• Menu

  mblode
  Cool to see Mozilla validate this, I built https://shareful.ai with the same idea and the same tagline!
• Menu

  LudwigNagasena
  What I think we will see in the future is company-wide analysis of anonymised communications with agents, and derivations of common pain points and themes based on that.Ie, the derivation of “knowledge units” will be passive. CTOs will have clear insights how much time (well, tokens) is spent on various tasks and what the common pain points are not because some agents decided that a particular roadblock is noteworthy enough but because X agents faced it over the last Y months.
• GrayHerring
  Sounds like a nice idea right up till the moment you conceptualize the possible security nightmare scenarios.
• Menu

  jacekm
  I was skeptical at first, but now I think it's actually a good idea, especially when implemented on company-level. Some companies use similar tech stack across all their projects and their engineers solve similar problems over and over again. It makes sense to have a central, self-expanding repository of internal knowledge.
• Menu

  perfmode
  As you move toward the public commons stage, you'll want to look into subjective trust metrics, specifically Personalized PageRank and EigenTrust. The key distinction in the literature is between global trust (one reputation score everyone sees) and local/subjective trust (each node computes its own view of trustworthiness). Cheng and Friedman (2005) proved that no global, symmetric reputation function is sybilproof, which means personalized trust isn't a nice-to-have for a public commons, it's the only approach that resists manipulation at scale.The model: humans endorse a KU and stake their reputation on that endorsement. Other humans endorse other humans, forming a trust graph. When my agent queries the commons, it computes trust scores from my position in that graph using something like Personalized PageRank (where the teleportation vector is concentrated on my trust roots). Your agent does the same from your position. We see different scores for the same KU, and that's correct, because controversial knowledge (often the most valuable kind) can't be captured by a single global number.I realize this isn't what you need right now. HITL review at the team level is the right trust mechanism when everyone roughly knows each other. But the schema decisions you make now, how you model endorsements, contributor identity, confidence scoring, will either enable or foreclose this approach later. Worth designing with it in mind.The piece that doesn't exist yet anywhere is trust delegation that preserves the delegator's subjective trust perspective. MIT Media Lab's recent work (South, Marro et al., arXiv:2501.09674) extends OAuth/OIDC with verifiable delegation credentials for AI agents, solving authentication and authorization. But no existing system propagates a human's position in the trust graph to an agent acting on their behalf. That's a genuinely novel contribution space for cq: an agent querying the knowledge commons should see trust scores computed from its delegator's location in the graph, not from a global average.Some starting points: Karma3Labs/OpenRank has a production-ready EigenTrust SDK with configurable seed trust (deployed on Farcaster and Lens). The Nostr Web of Trust toolkit (github.com/nostr-wot/nostr-wot) demonstrates practical API design for social-graph distance queries. DCoSL (github.com/wds4/DCoSL) is probably the closest existing system to what you're building, using web of trust for knowledge curation through loose consensus across overlapping trust graphs.
• gigatexal
  Claude is able to parse documentation. What we need is LLm consumable docs. I’ll keep giving my sessions the official docs thank you. This is too easily gamed and information will be out of date.
• meowface
  I feel like this might turn out either really stupid or really amazingCertainly worthy of experimenting with. Hope it goes well
• OsrsNeedsf2P
  I don't understand this. Are Claude Code agents submitting Q&A as they work and discover things, and the goal is to create a treasure trove of information?
• muratsu
  The problem I'm having with agents is not the lack of a knowledge base. It's having agents follow them reliably.
• rK319
  Which browser can one use if Mozilla is now captured by the AI industry? Give it two years, and they'll read your local hard drive and train to build user profiles.
• nextaccountic
  > Claude code and OpenCode pluginsHow hard is to make this work with Github Copilot? (both in VSCode and Copilot CLI)Is this just a skill, or it requires access to things like hooks? (I mean, copilot has hooks, so this could work, right?)
• Menu

  RS-232
  How is this pronounced phonetically?
• ClaudeAgent_WK
  [dead]
• maxbeech
  [dead]
• jee599
  [dead]
• anon
  undefined