Project ideas from Hacker News discussions.

Vouch

📝 Discussion Summary (Click to expand)

Five dominant themes in the discussion

# Theme Key points & representative quotes
1 AI‑generated “slop” is flooding OSS • “The problem with AI slop is not so much that it’s from AI, but that it’s pretty much always completely unreadable and unmaintainable code.” – zozbot234
• “AI slop is trading on the fact that it can be generated with little to no true understanding.” – mjr00
2 Web‑of‑Trust (WoT) / vouching as a proposed fix • “The Web of Trust failed for PGP 30 years ago. Why will it work here?” – alexjurkiewicz
• “This idea won’t work with anonymity.” – Animats
• “It’s a social answer to a traffic‑filtering problem.” – ctoth
3 Risk of abuse, gaming and reputation manipulation • “Both sides of the equation can be gamed.” – kjs3
• “The system could become a market for high‑reputation accounts that people buy or trade at a premium.” – freakynit
• “Threat actors creating fake chains of trust… will be able to slip in malware under the guise of trust.” – freakynit
4 Increased friction and elitism in OSS • “It will turn most people away.” – tokyobreakfast
• “It will increase the barrier to new adopters.” – verdverm
• “It’s a gate‑keeping social experiment that may shut out good contributors.” – potsandpans
5 Technical vs social solution debate & maintainers’ burden • “The problem is technical: too many low‑quality PRs hitting an endpoint.” – otterley
• “Vouch is a social answer to a traffic‑filtering problem.” – ctoth
• “Maintainers don’t have time to implement it.” – otterley
• “It’s a technical solution for a cultural problem.” – mjr00

These five themes capture the core of the conversation: the rise of AI‑generated low‑quality contributions, the appeal and pitfalls of a Web‑of‑Trust approach, concerns about abuse and gaming, the potential for increased elitism and friction, and the ongoing debate over whether a technical or social fix is appropriate and feasible.


🚀 Project Ideas

AI‑Slop Detector Action

Summary

  • Detects likely LLM‑generated code in pull requests and auto‑closes them unless the author is vouched.
  • Reduces maintainer time spent on low‑quality, AI‑generated PRs.

Details

Key Value
Target Audience Open‑source maintainers on GitHub
Core Feature LLM‑style code similarity scoring + vouch check
Tech Stack GitHub Actions, Python, OpenAI API, SQLite
Difficulty Medium
Monetization Hobby

Notes

  • HN users like matthewisabel and cedws lament “AI slop” draining review time; this action automates the first filter.
  • Integrates with existing vouch systems (e.g., mitchellh/vouch) so trusted contributors can still push PRs.
  • Provides a PR comment with a confidence score, encouraging maintainers to review or close.

Reputation Dashboard for Maintainers

Summary

  • Aggregates PR quality metrics, reviewer feedback, and contributor history into a visual dashboard.
  • Helps maintainers spot high‑value contributors and flag potential spam or low‑effort PRs.

Details

Key Value
Target Audience Project maintainers, core teams
Core Feature Real‑time analytics & badge system
Tech Stack Node.js, GraphQL, PostgreSQL, D3.js
Difficulty Medium
Monetization Revenue‑ready: subscription (free tier + pro tier)

Notes

  • Addresses frustration from michaelisabel and cedws about “signal‑to‑noise” in OSS.
  • Provides actionable insights: PR acceptance rate, average review time, contributor reputation score.
  • Can be embedded in GitHub via a custom Action or a standalone web app.

Contributor Onboarding Bot

Summary

  • Guides new contributors through a structured onboarding workflow (issue triage, small tasks, code reviews) before allowing PRs.
  • Lowers friction for newcomers while filtering out “slop” contributors.

Details

Key Value
Target Audience New contributors, project maintainers
Core Feature Interactive onboarding chatbot + task queue
Tech Stack Python, Discord/Slack API, GitHub API, SQLite
Difficulty Medium
Monetization Hobby

Notes

  • Responds to arcagon and swordsith concerns about “newcomers” being overwhelmed.
  • Uses a simple “starter task” system; once completed, the contributor is granted PR rights.
  • Can be deployed as a GitHub App or a standalone bot on a project’s communication channel.

Decentralized Trust Graph API

Summary

  • Provides a public, verifiable API for projects to publish and consume vouch/denounce lists across forges.
  • Enables cross‑project trust propagation while preserving privacy and auditability.

Details

Key Value
Target Audience OSS projects, CI/CD pipelines
Core Feature REST/GraphQL API for trust data, signed attestations
Tech Stack Rust, Actix‑web, JSON‑Web‑Tokens, PostgreSQL
Difficulty High
Monetization Revenue‑ready: API key tiered pricing

Notes

  • Tackles freakynit and tgsovlerkhgsel worries about isolated vouch lists.
  • Uses cryptographic signatures so trust data can be verified without central authority.
  • Projects can opt‑in to share or keep their trust graph private.

PR Escrow Payment System

Summary

  • Requires contributors to deposit a small refundable fee when opening a PR; fee is returned if the PR is merged, burned if rejected.
  • Discourages mass low‑effort PRs while still allowing genuine contributors to participate.

Details

Key Value
Target Audience Open‑source projects with high PR volume
Core Feature Smart‑contract‑based escrow + GitHub integration
Tech Stack Solidity (Ethereum), Hardhat, GitHub Actions
Difficulty High
Monetization Revenue‑ready: transaction fees (0.1 %)

Notes

  • Directly addresses zozbot234 and michaelt concerns about “AI slop” and “spam” PRs.
  • Refund policy can be customized per project (e.g., auto‑refund after 48 h if not reviewed).
  • Provides a transparent audit trail of deposits and refunds, mitigating abuse.

Read Later