Show HN: GobanFTP – a game of Go that lives in FTP listings
GobanFTP is a unique implementation of the game Go that utilizes FTP listings to store game data. It organizes the game as a directory structure, where moves and events are represented as filenames. The system allows for replaying games while ignoring various metadata, focusing solely on the essential game elements.
- ▪GobanFTP reconstructs a Go game using a directory-shaped protocol object.
- ▪Moves and acknowledgements are stored as event filenames under an 'events/' directory.
- ▪The game can be replayed without relying on file metadata, ensuring a focus on the gameplay itself.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/molang163/GobanFTP |
| Publication time | Tue, 19 May 2026 14:55:48 +0000 |
| Retrieval time | 2026-05-19T15:04:57.721Z |
| Last seen | 2026-05-19T15:04:57.721Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | O8-eQBXvLKZl |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
GobanFTP English | 简体中文 | 日本語 A Go game reconstructed from enumerable names. GobanFTP stores a Go game as a directory-shaped protocol object. The game descriptor directory names the game, rules, and players. Moves and acknowledgements are event filenames under events/. Replay reads those basenames. It ignores file bytes, file size, mtime, listing order, server order, sidecars, projections, and tmp entries. Current line: v1.0/package 1.000 release source. Three-minute check · Terminal play · Static specimen · The contract Quick local check: perl Makefile.PL make test prove -lr t/showcase-demo.t First Look These screenshots show the same object from four angles. The replay input is still the game descriptor basename plus direct event basenames. Protocol Object The game is visible as a tree.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.