Late.sh – a command-line Clubhouse for computer people

Original Article ↗ Hacker News Discussion ↗

An experimental “command-line clubhouse” called late.sh lets people hang out, chat and play games over SSH, evoking old-school BBS or IRC vibes for terminal enthusiasts. Commenters are enthusiastic about the concept and the depth of features, but sharply divided over the landing page’s low-contrast, LLM-flavored design and the prominence of a copy‑paste curl|bash installer. Security‑minded users highlight concerns around leaking existing SSH public keys and real usernames, urging clearer guidance on throwaway identities and server fingerprints, while others argue the trade-offs are acceptable for a niche, developer-focused social space.

Overall reaction & concept

  • Many commenters find the idea “terminal-native social space” / modern BBS very cool, nostalgic, and well executed.
  • The ability to use it with just ssh late.sh (no extra client required) is widely appreciated.
  • Some compare it to IRC, BBSs, Habbo Hotel, Club Penguin, and other SSH-based chat projects; consensus is that it’s more like a feature-rich BBS than plain IRC.

Landing page copy & design

  • Strong disagreement over the landing page: some think the copy is sharp and engaging; others see it as generic “LLM-y” text that’s confusing or unhelpful.
  • One thread critiques specific phrases like “no accounts” and “no OAuth” as marketing-y and unclear about user benefits or edge cases (lost keys, multiple devices).
  • Several wish the intro text explained design choices (SSH key auth) more concretely and answered obvious questions up front.

Accessibility, contrast & theming

  • Repeated complaints about low-contrast gray-on-dark text; some readers literally have trouble reading it, especially on e-ink or lower-quality displays.
  • Others report no issues and argue the low-key dark theme fits the “late night” brand.
  • There’s a meta-debate: how much a site should compromise aesthetics for accessibility vs. relying on user-level tools (extensions, custom CSS).
  • The app itself has multiple themes, including higher-contrast ones; a new higher-contrast web design is promised.

Security, privacy & SSH keys

  • Multiple comments warn against blindly running curl … | bash installers and note that servers can serve different content to curl vs. browsers.
  • Some suggest linking a public repo near the install one-liner to improve trust and transparency.
  • Detailed discussion around SSH public key “leakage”: connecting with default keys exposes all your public keys and may allow correlation with other services (e.g., work servers, GitHub).
  • The site documents and commenters reiterate an option to use a throwaway SSH key and IdentitiesOnly to limit what’s revealed.
  • One comment requests publishing the server’s SSH fingerprint for verification.

Identity & usernames

  • Concern that default SSH usernames (which may be real names on work machines) are used as platform nicknames without explicit consent.
  • Suggestions include clearer instructions to choose a pseudonymous [email protected] and/or an in-app confirmation step.

Miscellaneous

  • Some nitpicks: CLI that isn’t easily grep-able feels more like a GUI; questions about what the companion client adds beyond plain SSH.
  • Despite criticisms of the landing page and UX details, many still call it one of the coolest projects they’ve seen recently.