Project ideas from Hacker News discussions.

Which Odyssey translation wins a blind reading test?

📝 Discussion Summary (Click to expand)

Theme 1 – “Invented” poetic lines are common
Many users point out that several hallmark phrases in English Odyssey translations are not literal but were invented to create a poetic effect.

“wine dark sea” is a poetic/literary leap by Chapman and Pope that then became a functional convention in most subsequent translations.
— AlanYx

Theme 2 – Preference for literalist translations
The discussion is dominated by a desire for translations that stay close to the Greek wording, with several readers praising Lattimore (and sometimes Fagles) over more interpretive versions.

“man of many turns” sounds closer to the original than Wilson’s “complicated man,” but neither sounds made up.
— oliculipolicula

Theme 3 – Translation is a matter of audience and style, not pure fidelity
Contributors stress that “faithful” can mean different things—literal accuracy versus evoking the original vibe—and that translators often choose language that suits modern readers.

“It does seem like Nolan's adaptation would be not be popular with you or your schoolmates. But a screenplay based off Fagles' might have a chance.”
— oliculipolicula


🚀 Project Ideas

Generating project ideas…

Odyssey Translator Explorer

Summary

  • A web platform that lets users compare multiple English translations of the same Homeric passage side‑by‑side, with AI‑highlighted differences and fidelity tags.
  • Core value: helps readers identify literal vs invented phrasing, directly addressing the frustration expressed about “made‑up” lines in translations.

Details

Key Value
Target Audience Classicists, students, literature lovers, translators
Core Feature Multi‑translation overlay with AI‑generated fidelity scores and commentary
Tech Stack React front‑end, Node.js/Express API, Python NLP model (GPT‑4), PostgreSQL
Difficulty Medium
Monetization Revenue-ready: subscription tiers

Notes

  • HN commenters repeatedly asked for a way to see which translations are “invented” – this tool answers that directly.
  • Generates discussion‑worthy insights by surfacing translation choices, perfect for forum debates.

Homeric Verse Engine

Summary

  • SaaS that converts modern English text into Ancient Greek‑style poetry using LLMs, preserving meter and formulaic phrasing.
  • Core value: gives enthusiasts a way to create “Homer‑like” verses and discuss translation fidelity.

Details

Key Value
Target Audience Classicists, creative writers, educators, LLM hobbyists
Core Feature Natural‑language‑to‑Ancient‑Greek‑verse generator with meter control
Tech Stack Python backend, GPT‑4‑Turbo fine‑tuned on Homeric corpus, PoetryDB for meter validation, Docker
Difficulty High
Monetization Revenue-ready: pay‑per‑generation credits

Notes

  • Directly addresses comments about “LLM‑generated fake texts in Shakespeare or Homer style” and the desire to see such parodies “go viral”.
  • Opens space for community‑driven verses that can be voted on, fostering the kind of discussion seen in the thread.

Translation Blind Tester

Summary

  • Interactive web app that randomly presents short Homeric excerpts from different translations without revealing the source, letting users rank them.
  • Core value: replicates the blind‑reading test mentioned in the discussion, feeding data back to the community.

Details

Key Value
Target Audience Scholars, translation aficionados, casual readers curious about translation preferences
Core Feature Blind ranking interface with aggregate preference visualization
Tech Stack Next.js, GraphQL, Firebase Firestore, Python ranking algorithm
Difficulty Low
Monetization Revenue-ready: ad‑supported free tier with premium analytics

Notes

  • Mirrors the “blind reading test” topic that many commenters referenced, offering a practical implementation.
  • Provides tangible data for future surveys and can spark debate about which translations are truly preferred.

Read Later