Privacy hardening — the follow-ups have now landed
Quick update on the broader privacy work I mentioned last time. The audit beyond Google Translate turned into a set of small, self-contained changes, and the batch is now merged.
The goal was to ensure that visitors’ browsers only ever communicate with the wiki itself and not with a dozen other companies simply because a page has been opened. What’s now live:
- The wiki serves its own assets. Fonts, images and the built-in PDF viewer used to load from Google and outside CDNs as a page rendered; they’re now served by the site directly, so no third party learns you’re here just from a page loading.
- Live data goes through the wiki’s own server. Prices, chain stats, and “last updated” dates were previously fetched straight from external services by your browser. The site now fetches them server-side and passes them on, so those services no longer see individual readers.
- Baseline browser protections. Pages no longer leak which page you’re reading to outside sites, ad-targeting browser APIs are switched off, framing/clickjacking is blocked, and a content-security policy is now in place (in monitoring mode as a first step).
- Embedded keys removed. Access keys that were being shipped to every visitor have been pulled from the code, and the old ones have been revoked and rotated.
- Click-to-load for embeds. Embedded videos and maps only contact YouTube or the map provider when you choose to load them, nothing reaches out on page load.
- Google Translate fully removed. The last on-the-fly Translate widget is retired; all translations are now served locally from the wiki itself.
Same approach everywhere, everything cross-checked with an independent second/third model.
Special thanks to @squirrel for the support!