Repository navigation
Unlisted talk deck at /harness - #17
Merged
Merged
Conversation
Self-contained HTML deck (public/harness.html) served via a rewrite in next.config.js. Intentionally not linked from any nav.
The deck is deliberately unlinked, but robots.txt allows / and nothing stopped a crawler that found the URL from indexing it. A meta robots tag enforces the intent at the page; adding /harness to robots.txt would do the opposite and advertise it.
Both properties are silent when broken: dropping the noindex tag or inlining a CDN font still renders fine locally and only shows up as a search result or a blank slide on someone else's wifi. Each guard was verified to fail against a deliberately broken copy.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
`rewrites` is optional on NextConfig, so calling it directly failed `tsc --noEmit` — which neither vitest nor next build covers for files under tests/. Narrowing it explicitly also turns a deleted rewrites() hook into a named failure instead of a type error.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Serves the Norwegian talk deck ("Agent = modell + harness") at
/harness: oneself-contained HTML file in
public/, reached through a rewrite. Nothing linksto it.
Changes
feat— the deck plus the/harness→/harness.htmlrewrite.fix— anoindex, nofollowmeta tag. The deck was unlinked but notunindexed:
robots.txtallows the whole origin, so any crawler that learnedthe URL would have put a Norwegian slide deck in the results for a name the
homepage is deliberately tuned to own. The tag enforces the intent on the page
itself. Adding
/harnesstorobots.txtwould have done the opposite andadvertised the URL.
test— guards for the two properties that fail silently. Dropping thenoindex tag or inlining a CDN font both still render fine locally; the first
shows up months later as a search result, the second as a blank slide on a
meeting-room wifi. Each guard was verified to fail against a deliberately
broken copy, not just to pass against the current one.
Verification
next buildsucceeds./harnessreturns 200 with the deck,the noindex tag reaches the response,
sitemap.xmldoes not list it, androbots.txtdoes not mention it.the hash deep-links work, no console errors, and no slide overflows the
1280×720 stage.
Note
The repo is public, so
public/harness.htmlis readable on GitHub regardless ofthe noindex tag. The tag keeps the deck out of search results for hackimi.dev;
it does not make the file private.