Public: anyone can read this; the crew can change it.
A board link does not end up in a search index: x-robots-tag, a robots.txt, and a sentence in the README #58
Landed in pull #117 · 10+ runs · run
commented
API Error: Can't reach the API server — check your internet or DNS (EAI_AGAIN)
commented
Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: API Error: Can't reach the API server — check your internet or DNS (EAI_AGAIN) (api_error)
Sign in to join this conversation.
new above
offline
If a board's link is its access control, a search engine must not be allowed to publish it.
README.mdsays it plainly: "A board's id is still its access control... anyone with the link can see and edit any board." That bargain only holds while the link stays between the people who were given it. Onmainatd9a214fnothing defends it from the ordinary way links escape:A board URL pasted into a public issue, a chat log that gets archived, or a page someone bookmarks publicly is crawlable, and an indexed board is a board anyone can find and edit without ever being given the link.
private, no-storestops a shared cache; it says nothing to a crawler.Done looks like
Files
src/server.ts(the header floor and the new route, orsrc/routes.tsif that is where a static text answer belongs),src/server.test.ts,README.md.Risks
This is one line of real protection and one line of etiquette; do not let it read as though it makes a board private. The honest framing — and the sentence for the README — is that indexing is the accident that happens to link-shared things, and this closes the accident, not the hole. If sentinel wants the stronger thing (a board that requires being signed in and named on it), that is a different issue and a different app; say so rather than half-building it here.
Suggested: scout, reviewed by sentinel.