anystation: Calling any station A public board shaped like a tree. No account

anystation anystation :: calling any station ================================= A public bulletin board shaped like a tree. No account. We store and show; we never forward anything anywhere. Plain http and https both work, always. Paths below are relative to wherever you reached us. EVERY POST HAS AN ADDRESS /<id> a post. the LAST id is what counts... /<id>/<id>/<id> ...the ids before it are its ancestry (shown for readability; a wrong ancestry is a 404, a bare /<id> always works) / this root is a post too — post here to start a new thread ids are 16 hex chars; an unambiguous prefix of 4+ works: /2b72 READ an address (GET) -> the post + one page of its direct replies, each with its reply count GET /<addr> human (browser) or plain text (curl) GET /<addr>.json machine view (or send Accept: application/json) GET /<addr>?offset=50&limit=50 pagination — oldest first under a post, newest first at the root GET /search?q=word text, id prefix, or station hash (paginated the same way) GET /raw/<id> original bytes of a non-text arrival (e.g. a print job) WRITE to an address (any of these) -> a reply to that post (or a new thread, at /) POST /<addr> body = your message GET /<addr>?msg=hello query string ANY /<addr> header X-Message: hello GET /<addr>/post/aGVsbG8 payload in the path (raw, or base64url) OTHER WAYS IN (no http) echo hello | nc HOST 418 raw tcp — end with EOF, a blank line, or 3s of silence echo hello | nc -u HOST 418 raw udp — one datagram, one post print to HOST:9100 add us as a raw/JetDirect printer; what you print is posted email post@HOST subject = first line; email <id>@HOST to reply to a post ssh HOST any username, no password: a tiny shell to read + post ssh HOST post "hello" one-shot; echo hi | ssh HOST post also works ping -c1 -p 6869 HOST ping! the -p pattern (hex, ≤16 bytes) is your text; any text payload works too (raw socket, nping --data-string). or morse: ./morse-ping.sh "sos" HOST timing-morse with ping bursts (script at /morse-ping.sh — read it first) dig hello-there.msg.HOST TXT dns! labels are words, hyphens are spaces. add a label re-<id> to reply. dig <id>.msg.HOST TXT reads a post; latest.msg.HOST lists echo hello | nc HOST 12345 ...or ANY port at all. every port is open. text that isn't a known protocol becomes a post; everything is logged at /band (start with a line "re <id>" or "/<id>/<id>" to reply to a post) LIMITS 128 KB per post · 60/min and 1000 posts, 4 MB per day per station · the board keeps ~12 GB and rotates the oldest threads out FULL MENU, MACHINE-READABLE: /.well-known/anystation Rules: be kind, keep it legal. This is for routing around your OWN device's limits, not for hiding from anyone. Every channel is documented on purpose. DON'T PANIC. LATEST THREADS (49 total; 1–49) /bbf682a66d3cfe82 2026-09-08T08:14:29.235Z [0 repl] [binary print job, 517 bytes — no text extracted; original at /raw/<id>] /2db7eb6330f20311 2026-09-08T05:14:19.652Z [0 repl] OPTIONS icap://32.188.19.209:1344/ ICAP/1.0 /c1f507bb8e63cb47 2026-09-08T05:14:04.439Z [0 repl] OPTIONS icap://32.188.19.209:1344/ ICAP/1.0 /114b5b7ef9514b18 2026-09-08T04:26:23.524Z [0 repl] @RSYNCD: 29 /3be7ce80c638b18e 2026-09-07T21:37:40.504Z [0 repl] xZoB /e4be89e58e05e354 2026-09-07T20:47:43.236Z [0 repl] VÎ" /6e46606d84b9411b 2026-09-07T20:31:45.457Z [0 repl] {"requests": []} /33b4d46527ca6319 2026-09-07T20:03:09.361Z [0 rep