The Man in Seat 61
A long-running personal website, “The Man in Seat 61,” is widely praised as an old‑school, hand‑crafted guide to international train travel that makes complex, country-specific rail systems understandable for non‑locals. Commenters highlight its depth, practical tips, simple design, and apparent accuracy across regions from Europe to India, while noting the challenge of keeping such a static, manually maintained resource up to date. Some see it as a model of the early, decentralized web, resisting trends toward bloated design and AI‑driven services, even as others speculate about layering automation or conversational interfaces on top of its rich content.
Overall sentiment about Seat61
- Widely praised as an “old internet” gem: single maintainer, niche obsession, high information density, minimal fluff.
- Many report using it for complex rail trips in Europe, India, Southeast Asia, Trans‑Siberian, North America, and the Balkans.
- Seen as uniquely practical: route options, how to book, where to sit for the best views, station logistics, and even hotel recommendations.
- Several people mention the site directly enabled memorable family trips and reduced planning stress.
Design, UX, and philosophy
- Simple, fast, “early‑2000s” static HTML design is broadly appreciated.
- Ads are present but generally viewed as modest compared to modern sites; some dislike the added Google ads.
- The site’s non-commercial feel and refusal to take donations (redirecting support to a UNICEF fundraiser) are seen as part of its charm.
Data quality and maintenance
- Many users find the information impressively current given it’s largely hand-edited static HTML.
- Others worry about maintenance burden: updates rely on large-scale find/replace, with no CMS.
- Some call for more visible timestamps to judge freshness.
- At least one commenter finds the UK section “laughably out of date” and overly focused on a single booking platform, casting doubt on overall reliability.
- Specific complaint that the Amtrak California Zephyr on-time description is now severely inaccurate.
Technical hosting and decentralization
- One commenter notes it still runs on an old self-managed VM and SAN, surviving HN spikes.
- Debate over whether it should move behind Cloudflare/AWS for DDoS protection and latency vs. keeping self-hosting to avoid centralization and preserve sysadmin skills.
AI, tooling, and search
- Some suggest an AI/chatbot interface for natural-language queries and to help maintain content.
- Others argue a CMS or existing search is sufficient and resist “AI for everything.”
- Middle stance: LLMs could assist with bulk text updates without changing the site’s front-end simplicity.
Broader rail context
- Discussion branches into rail reliability (especially Amtrak long-distance delays) and freight vs. passenger priority in the US.
- Noted gaps and geopolitical changes: some older overland routes (e.g., via Syria, Sudan, Russia, ferries in the Med) are now impractical or unsafe.
- Mention of missing coverage for Mexico’s new Tren Maya.