← knowledge.oriz.in

GitHub Gist redirect (HTML meta-refresh)

service short-linkgithubgistmeta-refreshzero-infrafallbackimmutable

GitHub Gist redirect (HTML meta-refresh)

Role

Tier 3 zero-infrastructure fallback in the family's three-tier URL-shortener stack (see decisions/architecture/url-shortener-mitigation-tiers.md). Tier 1 is the s.oriz.in CF Worker, Tier 2 is TinyURL, Tier 3 is this service.

Used when:

Free tier

Card / subscription required?

NO. GitHub Free covers unlimited public gists. The family already runs a free GitHub account for source hosting; no extra signup.

How the redirect works

Each redirect is a single HTML file in a public gist:

<!doctype html>
<meta charset="utf-8">
<title>Redirecting…</title>
<meta http-equiv="refresh" content="0; url=<TARGET>">
<link rel="canonical" href="<TARGET>">
<meta name="robots" content="noindex">
<script>location.replace('<TARGET>')</script>
<p>Redirecting to <a href="<TARGET>"><TARGET></a>…</p>

Three-layer redirect logic:

  1. <meta http-equiv="refresh" content="0; url=…"> — works even without JavaScript; standards-compliant since HTML 2.0.
  2. location.replace(…) — instant client-side replace when JS runs; avoids adding the gist URL to history.
  3. Visible link — final fallback for hostile JS-blocked environments.

Plus:

Mint surface (manual only)

Tier 3 is manual-mint only by design — the family explicitly does not automate gist creation:

  1. Create a new gist at https://gist.github.com/ under the chirag127 account.
  2. Filename: <short-name>.html (e.g. talk-2026-knowledge.html).
  3. Paste the template above with <TARGET> substituted.
  4. Save as public gist.
  5. Copy the raw URL: https://gist.githubusercontent.com/chirag127/<hash>/raw/<short-name>.html.

Automation would create a write-frequent path against the gist API and risk noisy gist-list churn against the user's profile. Keep it manual; mint volume is single-digit per year.

Why three layers and no automation?

Alternatives

Swap cost

Low. Each redirect is a single static HTML file. Migrating to another zero-infra hosting (e.g. Codeberg pages, Sourcehut paste) is copy-paste-with-find-replace.

Why this is our pick (for Tier 3)

Cross-refs