ODC Explorer: a web directory you browse locally over IPFS. No search engine, no gateways, no trackers.

Search engines see every query you type, rank results for their own reasons, and know who asked. I've been building ODC Explorer as an alternative: a desktop client for the Open Domain Catalog, a directory of websites organised like a library and read straight from IPFS.

What it is

The Open Domain Catalog files websites under call numbers, like books on shelves: 1 Reference › 15 Search Engines, 3 Entertainment › 30 Gaming › 300 Web, and so on. You browse the shelves instead of typing queries. The whole catalog is stored as content-addressed blocks on IPFS and published under a single signed IPNS name.

ODC Explorer runs on your own machine. It's a small local web app with its own embedded IPFS peer, written in pure Python.

What it does for your privacy

• No queries to log. There's no search box sending what you're looking for to anyone. You browse a catalog, and the browsing happens on your machine.
• No middleman server. It talks to the IPFS network directly. There's no HTTP gateway, no API backend and no account.
• No third-party requests from the page. No CDNs, no web fonts, no analytics, no cookies. Every page is sent with Content-Security-Policy: default-src 'self', so the browser can't load anything from elsewhere even by mistake.
• No referrers. Links to listed sites open only when you click them, in a new tab, with no referrer.
• Local by default. The web interface listens on 127.0.0.1 only.
• Settings stay in your browser. Your theme, the 18+ switch (adult content is hidden by default) and whether you've seen the donation prompt live in localStorage, never on a server.
• Tamper-evident content. Every block is checked against its content hash and against the catalog spec, and the catalog root is signed. Nobody in the middle can quietly change what you see.

What it does NOT protect you from (please read)

I'd rather be upfront about this than have you find out later:

• IPFS is a peer-to-peer network, not an anonymity network. Peers you fetch from can see your IP address and which blocks you request, and blocks map to catalog categories.
• Your node shares what it reads, publicly. To keep the catalog online, every reader serves the blocks it has fetched and announces them on the IPFS DHT. That means your IP is publicly listed as a provider of the blocks you've read, which can reveal that you use ODC and roughly which shelves you've browsed.
• DNS. To join the network it looks up the standard IPFS bootstrap hostnames through your system resolver, and falls back to public resolvers (1.1.1.1 and 8.8.8.8) if yours fails.
• Router port mapping. It asks your router (UPnP/NAT-PMP) to open a port so other readers can reach you.

If your threat model includes your ISP or network observers knowing you use it, this isn't the tool for that, at least not yet.

Try it

Linux, Python 3.9+, Flask:

git clone https://github.com/ki4jgt/ODC-Explorer.git
cd ODC-Explorer
./install.sh

Or run it from source with ./run.sh --open.

It's early. The catalog is young and the spec is a draft (v0.1), and I've only tested on Linux. but I'm spending most of my nights adding, shifting, updating and ranking sites captured by my web crawler (respects robots.txt and sends a hit to each domain name only once every 30 seconds).

There are adult categories

I'd especially like to hear from privacy folks: which of the caveats above matter most to you?

Repo: https://github.com/ki4jgt/ODC-Explorer