Twtxt is a decentralised, minimalist microblogging service for hackers

Original Article ↗ Hacker News Discussion ↗

Name & Branding

  • Pronunciation is debated (twit-text, tweetext, twixt), highlighting awkward branding.
  • Community often uses “Yarn” for the network and “twtxt” for the protocol, partly sidestepping the name issue.

Protocol & Ecosystem

  • Core idea: a microblog is just a UTF‑8 text file served over HTTP, with simple line-based format (timestamp + text).
  • Registries and aggregators exist (e.g., registry APIs, tilde.institute, feeds.twtxt.net) to help discover feeds.
  • Some static site generators and personal sites expose twtxt feeds; others have written hosted servers and registries.

Community Size & Activity

  • One commenter struggles to find live feeds and notes stalled commits, suggesting low activity.
  • Another points to hundreds of feeds and estimates ~70 active interactors on one instance and ~1000 active feeds overall.
  • General consensus: the community is small and niche compared to mainstream platforms.

Use Cases, Benefits, and Limitations

  • Benefits: extreme simplicity, easy to implement, self‑hostable, “for hackers,” interoperable with other tooling.
  • Critiques: unclear what problem it solves beyond RSS/HTML; feels like “just a shared text file.”
  • Managing follows and polling many feeds can be cumbersome; discovery remains a hard unsolved problem.

Comparisons to Other Platforms

  • Compared to Mastodon/ActivityPub, Nostr, RSS/Atom/JSON Feed, and traditional blogs.
  • Some argue you don’t need microblogging at all; others value diversity of decentralized options.

Minimalism, UX, and Design Debates

  • Strong disagreement over text‑only bias: some see ASCII/monospace social systems as crude or limiting to human expression.
  • Others defend minimalism as focusing on content, reducing distraction, and fitting CLI/terminal workflows.
  • Debate touches on images, layout, math notation, and whether “presentation” is part of expression.

Technical Issues & Tooling

  • One user reports bugs and brittle behavior with non‑default configs, leading them to abandon it.
  • Others mention potential bots, email, or RSS clients as nicer frontends, but note lack of polished mobile apps.