Links to fox's work

A word about accessing my content...

...that's also a good primer on the decentralised web (or what's being called Web3)

Network-based protocols:

DNS: Traditional top-level domains (TLDs) like .com or .net managed through centralized domain name resolvers. Internet Corporation for Assigned Names and Numbers (ICANN) sells domain names under the TLD to third-party registrars. Internet Assigned Numbers Authority (IANA) additionally assign IP address blocks to Internet Service Providers (ISPs) and "cloud" providers. Registrars like GoDaddy or BigRock lease out domains on yearly plans to individuals and corporations, often with shady pricing practices ($6 for first year, $499 for the second, and so) while ISPs make their share by charging monthly premiums for a static IP (necessary for DNS to work). Purchased domains are delegated to an authoritative DNS server that resolves domain names to its host IP. Traditional hosting depends on ICANN-accredited registrars, authoritative DNS providers, and ISP's hosting provisions, whereas "cloud" hosting requires abiding by their policies while entrusting your data to their facilities. Needless to say, this opens many areas for arbitrary abuses of power.

Tor: Anonymous .onion addresses that resolve on the Tor network. Tor does not require Transport Layer Security (TLS) as encryption is built into onion routing. Each .onion address is automatically generated as a hash of the server's public key, uniquly binding them to the instance running the Tor Hidden Service. Anyone can generate an ed25519 key to obtain a v3 .onion address. Onion addresses are self-authenticating and require no DNS, making them trustless. Requires Tor browser or proxy (running a Tor client on OpenWRT router for LAN-wide access).

Token-based protocols:

IPFS: Pointers to content on the IPFS peer-to-peer (P2P) network. Unlike http://, ipfs:// is a content-addressed storage protocol. Its P2P architecture can be likened to torrents, but for digital content meant to be rendered inside a browser. Each IPFS content ID (CID) is a hash of the file's data and uniquely references the content, not the host seeding it (for lack of a better analogy). Links remain valid as long as at least one node hosts the content. Unlike traditional DNS and Tor, IPFS's content-first design routes using a distributed hash table, rethinking content delivery and caching altogether. Requires an IPFS gateway (IPFS Desktop for Linux/Mac/Windows).

ENS: Ethereum Name Service (ENS) addresses like .eth that resolve to cryptographic hashes on the blockchain. ENS can point to everything from crypto wallets to static IP addresses (using text records instead of A/AAAA). Unlike DNS, ENS is decentralised by design, giving unconditional ownership of domains to individuals without necessary trust in centralised nameservers or namespace authorities like ICANN, a privately run organisation. Requires an ENS-compatible browser (Mist) or extension (MetaMask).

Recommended: For maximum availability, bookmark IPFS hashes and .onion addresses as they are impossible to control and persistent. You may contribute by pinning (the IPFS equivalent of seeding a torrent) my content using IPFS Desktop. Together, they resist the usual barrage of moral threats, legal wordcraft, and other psychological tactics used time and again by this delusional, painfully clueless society to silence awareness of reality, especially where the content being produced is deemed "inconvenient" to vested interests or leads to widespread moral panic.