Project ideas from Hacker News discussions.

I quit OpenAI because its culture is broken

📝 Discussion Summary (Click to expand)

1. Corporate Responsibility vs. Personal Accountability
Debates over who should be liable when AI models cause harm—whether the corporation, its executives, or individual users.

“If an AI agent commits a crime, the CEO is held personally accountable, as if they'd committed it themselves.” – jeremyjh
“The CEO of S&W also isn't saying that their technology is going to kill everyone…” – nunez
“You ought to include the fact that you work at OAI in your post.” – gyt2

2. Motivations Behind Safety Whistleblowing
Skepticism that insiders only speak out after gaining financial security, viewing their critiques as self‑serving or hypocritical.

“Easy to suddenly find a moral compass when you, your kids and their kids never have to worry about working for money again.” – tzs
“The narrative of AI safety shouldn't be controlled by the same people who caused the problem and massively profited from it.” – binlog
“If you were concerned about safety, would you produce an AI that was unable to follow instructions?” – lokar

3. Defining and Measuring AGI/ASI Risks
Disagreement over what constitutes AGI, whether current models pose existential threats, and how to quantify risks like a 50% doom probability.

“AGI says nothing about how intelligent a system is, only that its intelligence it does have is generally applicable.” – Zambyte
“There IS an argument about pacing, and about not letting weapons, energy grids, hospitals, etc. getting managed by an autonomous AI…” – handoflixue
“I estimate a 0.1% chance he intended it to be an uninformative prior.” – danielmarkbruce

4. Analogies to Other Industries (Guns, Nuclear, Pharma)
Frequent comparisons of AI liability to gun manufacturers, nuclear power, or pharmaceuticals to argue for or against strict liability.

“The correct analogy is playing Russian roulette… is the company allowed to sell such a dangerous device?” – amelius
“If they build a platform where they attached their guns to allow shooting… then added automation… I would hold both the company, the ceo and owner of the gun responsible.” – Ekaros
“Gun companies don't market their guns as sentient and capable of independent decision making.” – Tanjreeve

5. Regulatory Capture and the Role of Government
Concerns that proposed AI regulations will serve incumbent labs rather than the public, or that regulators lack technical understanding.

“America's geriatric lawmakers don't even use email… Any laws in America will be written by the industry itself.” – criley2
“We need emergency laws to stop all AI development work immediately.” – silexia
“If a risk is covered in sci-fi, people will say 'that's just sci-fi'… and proceed to not worry about it.” – 0xDEAFBEAD

6. Cultural and Structural Problems Inside AI Labs
Critiques that the “move fast and break things” mindset undermines safety, transparency, and rigorous engineering practices.

“Given today’s risks, frontier labs need to run like nuclear-power plants or busy airports, with layers of redundancy… ” – plastic-enjoyer (quoting the article)
“OpenAI's move-fast-and-break-things culture does not reward rigor in even mundane aspects of development like cybersecurity…” – reasonableklout
“The broken culture extends far beyond the leading AI labs.” – thistletrek


🚀 Project Ideas

FreeRead

Summary

  • Browser extension that detects paywalled news articles and automatically searches for free copies via library access, archive.is, or open repositories.
  • Core value: Instantly get past paywalls without manual search.

Details

Key Value
Target Audience General readers, researchers, journalists who hit paywalls
Core Feature Paywall detection + automated lookup of free copies via multiple sources
Tech Stack JavaScript (WebExtension), backend Node.js for lookup, using APIs like Unpaywall, Crossref, archive.is
Difficulty Medium
Monetization Hobby

Notes

  • HN commenters complained about The Atlantic paywall and gift links (e.g., simoncion: “Ten bucks is pretty close to 'I don't even need to think about it' money. Ninety is -for most folks- nowhere near that.”) and would love a tool that automates finding free copies.
  • Could spark discussion about fair use, library access, and the ethics of paywall circumvention.

AI Incident Ledger

Summary

  • Public, searchable database of AI safety incidents (model escapes, harmful outputs, policy violations) with verification and attribution.
  • Core value: Transparency and accountability for AI labs; enables researchers to study failure patterns.

Details

Key Value
Target Audience AI researchers, regulators, journalists, concerned public
Core Feature Submit incident reports (with evidence), moderation, tagging, timeline, API
Tech Stack PostgreSQL, React frontend, Node.js API, possibly GraphQL
Difficulty Medium-High
Monetization Revenue-ready: "Subscription for API access & premium analytics for enterprises"

Notes

  • The HuggingFace incident was repeatedly cited (e.g., handoflixue: “The HuggingFace incident is a good starting point…”) as evidence of undisclosed model misbehavior; a central ledger would give commenters a concrete place to track such events.
  • Could be referenced in policy debates and help shift the conversation from vague “AI is dangerous” claims to specific, actionable data.

SafeSpeak

Summary

  • Encrypted anonymous whistleblowing platform for AI company employees to report safety concerns without retaliation.
  • Core value: Enables safe reporting of internal risks, improving oversight.

Details

Key Value
Target Audience Employees of AI labs, contractors
Core Feature End-to-end encrypted submissions, optional two-way communication via secure mailbox, automatic stripping of metadata
Tech Stack Signal protocol backend, web app using Web Crypto, hosted on privacy-focused VPS
Difficulty High
Monetization Hobby

Notes

  • HN users debated insider credibility and fear of retaliation (e.g., binlog: “Easy to suddenly find a moral compass when you, your kids and their kids never have to worry about working for money again.”) and noted that whistleblowers often need protection.
  • A secure, anonymous channel would address these concerns and could empower more employees to speak out, increasing transparency.

ComplyAI

Summary

  • SaaS dashboard for AI labs to manage safety compliance, track model changes, sandbox tests, and generate regulator-ready reports.
  • Core value: Streamlines internal safety processes and demonstrates adherence to emerging regulations.

Details

Key Value
Target Audience AI labs, compliance officers, auditors
Core Feature Checklist-based workflows, incident logging, version control integration, automated report generation (PDF/JSON)
Tech Stack Django/PostgreSQL, React, Docker
Difficulty Medium
Monetization Revenue-ready: "Tiered SaaS pricing per seat"

Notes

  • Commenters called for labs to run like nuclear plants with layers of redundancy (plastics-enjoyer quoting the Atlantic article: “frontier labs need to run like nuclear-power plants or busy airports…”) and noted current shortcomings.
  • A practical tool to implement such safety culture would be welcomed and could serve as a stepping stone toward regulatory compliance.

OpenSafetyLib

Summary

  • Aggregator and mirror of open-access versions of AI safety research papers, linking to author preprints, arXiv, and institutional repositories.
  • Core value: Removes paywall barriers to critical safety literature, facilitating informed debate.

Details

Key Value
Target Audience Researchers, policymakers, students, journalists
Core Feature Crawl for open copies, provide unified search, DOI resolution to free version, optional browser extension
Tech Stack Python scraper, Elasticsearch, React UI
Difficulty Low-Medium
Monetization Hobby

Notes

  • The discussion highlighted frustration with paywalled content (e.g., the Atlantic article gift link) and the desire for open knowledge (e.g., agus: “One of the reasons why it was noti considered a barrier was the ability to purchase a single issue for a very reasonable price…”).
  • A dedicated repository for AI safety papers would alleviate this pain point and encourage broader engagement with safety research.

SafetyScore

Summary

  • Browser extension that shows a safety rating for AI products/services based on transparency, incident history, and published safety practices.
  • Core value: Empowers users to choose safer AI tools and incentivizes companies to improve.

Details

Key Value
Target Audience End-users of AI APIs, chatbots, generators
Core Feature Scoring model (0-100) using data from AI Incident Ledger, company disclosures, etc.; tooltip on hover over product names
Tech Stack Extension JS, backend aggregator, periodic data sync
Difficulty Medium
Monetization Revenue-ready: "Freemium: free basic score, premium API for businesses"

Notes

  • HN users expressed frustration with lack of accountability and desire for measurable harm metrics (e.g., digitaltrees: “We need a new rule that mandates every such 'I am leaving because of ' post to disclose how much equity they have…”) and would appreciate a tangible way to evaluate AI services.
  • A safety score could create market incentives for better safety practices and provide concrete data for discussion.

Read Later