Thats the designed behaviour, because expose your instance at public network and welcome anyone to open anything might quickly exhaust your poor oauth tokens’ use credits, which are just around 100 API requests per 10 mins.

So there is a main switch called “Disable upstream requests”, let that cloud svg besides searchbox to be grey and save your credits for NP archiving.

Anyway, if you host your own instance at homelab and turn that switch off, every sub is normal and free to browse.

Thx for that, I could write my own words anyway, I just thought it would be more native if I use cluade to translate … sorry for those grating words

Five layers of NP (Natural Prefetch), HR (the outbound rate-limit layer) and the caching/failover stack aren’t boilerplate — they’re original designs I built from scratch. The first demo did come together fast, sure, but what you don’t see behind it is two-plus months of testing, reverse-engineering how Reddit actually behaves, hunting down bugs, iterating, and writing a real test suite.

One concrete example: I wrote the cache-eviction logic myself. Small and large files are each run through a scoring function, and every cleanup pass consults that score to decide what to drop — done as a non-IO-intensive, incremental sweep instead of a blocking purge. That’s not something a one-shot prompt hands you; it came out of actually watching the thing misbehave under load and tuning it until it didn’t.

If you want to dig in, the commit history and the test suite are right there in the repo — happy to walk through any part of the design.