Access MSPMetro via Tor and IPFS

Why: resilience, censorship resistance, and offline-friendly delivery. Content is identical across clearnet, onion, and IPFS/IPNS.

Clearnet

Primary: https://mspmetro.com
S3 mirror: Scaleway bucket

Tor

Vanity onion: HTTP · HTTPS (trust bundle)
Trust bundle: onion-ca-bundle.crt (import to trust HTTPS on the onion)
IPFS gateways (onion): hetz gateway · ord gateway

IPFS / IPNS

IPNS ID: /ipns/k51qzi5uqu5dlwnidjycj5bhfmfds005bvc6q80fk1q1tdkgmj46n5k9w7atkx
DNSLink: `_dnslink.mspmetro.com TXT "dnslink=/ipns/k51qzi5uqu5dlwnidjycj5bhfmfds005bvc6q80fk1q1tdkgmj46n5k9w7atkx"`
Clearnet gateway: https://dweb.link/ipns/mspmetro.com
Self-host: ipfs add -Qr build && ipfs name publish --key=mspmetro /ipfs/<CID>

Offline/PWA

A service worker caches core pages (front page, offline.html, CSS). If you lose connectivity, you’ll see the cached content instead of a blank page.

How it works (plain language)

IPFS/IPNS: IPFS stores content by CID; IPNS is a pointer that updates to the latest CID. DNSLink maps `mspmetro.com` to that IPNS pointer.
Tor: Onion services provide end-to-end encrypted access without relying on DNS. The vanity onion points to the same content as the clearnet site.
Parity: We publish the same build to web, onion, and IPFS so users can choose the path that works best.