sebastiaand

> Do you still have a gopher client?

This is a big problem. Firefox dropped Gopher and Chrome never supported it. Most Gopher users, presumably, use a Gopher web proxy.

For fun I recently built a Gopher web client, implementing the entire protocol in a single page app (literally a single HTML file, no frameworks or dependencies). It supports most documented file formats including "modern" extras like video and audio.

Gopher client: - https://gopher.commons.host

Source code: - https://gitlab.com/commonshost/gaufre

Thanks! Pi-hole is a great project. We have been looking at how to incorporate filtering. Current challenge is making DOH more accessible through a reverse proxy. Coming soon: https://github.com/commonshost/dohnut

  npx tlx-keygen

- No installation required, npx comes with Node.js and downloads/runs/removes the package.

- Generate localhost certs with support for *.localhost, 127.0.0.1 (IPv4), ::1 (IPv6), etc.

- Register in operating system trust store (Win/Lin/Mac)

- Tested with major browsers (Chrome/Firefox/Safari/Edge)

https://www.npmjs.com/package/tls-keygen

There is an experimental RFC currently being discussed: https://datatracker.ietf.org/doc/draft-ietf-httpbis-cache-di... The technique is derived from the H2O Casper work (and by the same author).

I have a Javascript service worker implementation here: https://www.npmjs.com/package/cache-digest-immutable

Note: This is still based on a Golomb-coded set (GCS). Current proposal under discussion is to use a Cuckoo filter. Takes slightly more bandwidth but allows removal when browser caches evict items.