"simply" being able to bypass the caching server would totally solve it (+ some honest explanation in the settings).

"simply" in quotes because I'm sure that would be a large refactor to their networking code. But worth it in my opinion, as the guy not paying the bills ;)

> "Uncheck this box to bypass the caching server and get content directly from the relays set below. Note: the caching server may filter content and order posts at the discretion of the server operator. You may supply your own caching server, use the Primal default, or bypass the feature altogether"

That would clear up user confusion, build trust, and avoid this whole spat we find ourselves participating in.

Reply to this note

Please Login to reply.

Discussion

lmao at "70 people"

Lol shit that went right over my head. nice one

it also is much cheaper! their caching service is not optimized, and they probably use the more enterprisey clouds, so you are looking at a few thousand/mo on caching

hetzner dedicated machine.

no cache is cheaper than cache on what is likely aws + a lot more unnecessary infra (image modification and storage of those images, the DBs and search, so on)