Project ideas from Hacker News discussions.

The Murky History of Soviet-Born Tetris

📝 Discussion Summary (Click to expand)

Theme 1 – The article is vague and under‑cited
- “A sort of oddly opinionated article despite having little citation to it and being rather vague on events and timelines compared to some other pieces out there.” – Jwillacyd
- “I’d love to know why for example, the author finds it so clear that Pajitnov should not have won a copyright. I don’t have any stake in it myself, the claim just isn’t supported in the article.” – Jwillacyd

Theme 2 – Dispute over who truly owns Tetris and the fairness of credit
- “Contrary to the claim attributed to Henk Rogers there were no ‘straightforward business arrangement’ between Pajitnov and myself… I did not entirely agree with the content, but I trusted Alexey and signed the paper anyway. In a few months my name disappeared from all newly released versions of Tetris…” – ndiddy (quoting Gerasimov’s account)
- “For his part, he seems to feel here that pajitnov cut him out unfairly.” – Jwillacyd
- “Looks like he developed the original on his employer's equipment during work hours. And the copyright on tetris pieces is just ridiculous given the Colomb's publication…” – 331c8c71

Theme 3 – Misuse/misunderstanding of the term “samizdat” in the Soviet context
- “Samizdat very specifically refers to censored texts. Yeah sure various versions of Tetris informally circulated around on floppies/tapes just like all other games and software, but that's not samizdat…” – orbital-decay
- “Samizdat was not just about censored texts. The larger point of samizdat is specifically about viable ways to distribute your stuff even if it was not seen even by a single censor.” – ShinyLeftPad
- “people in the USSR had to be creative… to bypass censorship… This created things like roentgenizdat or 'ribs' (gramophone recordings made from polyester X-ray films).” – konart


🚀 Project Ideas

Tetris History Archive & Annotation Platform

Summary

  • A centralized, version‑controlled repository for primary sources, scanned documents, interviews, and differing accounts of Tetris’ creation and IP disputes, addressing the lack of citations and conflicting narratives noted by HN users.
  • Core value proposition: provides historians and enthusiasts a trustworthy, searchable collection where claims can be annotated, compared, and tracked over time.

Details

Key Value
Target Audience Software historians, IP researchers, developers, journalists
Core Feature Git‑backed store of PDFs/scans/web‑archives with inline annotation, diff view, and citation linking
Tech Stack GitLab/GitHub, Markdown, IIIF image server, Elasticsearch, React + TypeScript frontend
Difficulty Medium
Monetization Hobby

Notes

  • HN commenters expressed frustration: “I’d love to know why … the author finds it so clear that Pajitnov should not have won a copyright” (Jwillacyd) and noted that Gerasimov’s page “has been edited over the years under pressure” (msephton).
  • Enables side‑by‑side comparison of archived versions (e.g., 2006 archive) and community‑driven fact‑checking, fostering deeper discussion on software history.

ChronoClaim: Software IP Timeline Visualizer

Summary

  • Interactive timeline tool that lets users plot events, claims, and evidence for software IP cases, highlighting contradictions and missing details.
  • Core value proposition: turns vague, conflicting stories into a visual, evidence‑based chronology that anyone can explore and contribute to.

Details

Key Value
Target Audience Researchers, lawyers, tech journalists, hobbyist historians
Core Feature Drag‑and‑drop timeline with claim cards, source attachments, conflict detection, and filtering by evidence type
Tech Stack D3.js for visualization, Node.js/Express API, PostgreSQL, optional Neo4j for claim graph, hosted on Vercel
Difficulty Medium
Monetization Hobby

Notes

  • Users asked for “more detail in why … the author finds it so clear” and wanted to see “the earliest version of Gerasimov’s account” (msephton). ChronoClaim lets them attach those versions and see how claims shift over time.
  • Visualizing the back‑and‑forth between Pajitnov, Gerasimov, and Henk Rogers would clarify the “comedy of errors” described in the thread, sparking informed debate.

HistoCheck Browser Extension

Summary

  • Lightweight extension that scans tech‑history articles for questionable claims and displays inline fact‑checks sourced from a community‑curated database of primary documents.
  • Core value proposition: gives readers immediate context and credibility signals while they read, reducing reliance on vague or opinionated pieces.

Details

Key Value
Target Audience General readers of tech news, students, enthusiasts
Core Feature Real‑time highlighting of claims, tooltip with community votes, links to archived sources, and ability to submit corrections
Tech Stack WebExtensions (JS/HTML/CSS), backend Supabase for claim storage, optional Cloudflare Workers for edge caching
Difficulty Low
Monetization Hobby

Notes

  • Commenters lamented “the article … being rather vague on events and timelines” (Jwillacyd) and called out mischaracterizations of samizdat (ShinyLeftPad vs. orbital-decay). HistoCheck would let users flag those lines and link to authoritative sources like Gerasimov’s original page or archived versions.
  • By turning passive reading into an active verification process, the extension encourages higher‑quality discussion on HN and similar forums.

Read Later