I think having a caching layer is ok for performance, but that layer becomes attack vector as soon as your application gets bigger or the layer gets smarter.

A bit different approach is to consider using independent caching services or providers. Some that you have no direct relationship to, but your app/architecture just uses them. Even better if the users can actually select this somehow.

This is of course way harder to implement, but on the other hand it's presumably more censorship resistant.

To be clear I appreciate Primal and I'm using Primal right now on desktop (I have not found a better client on desktop), but I'm afraid the architecture and incentives may be pushing Primal in the wrong direction in the future.

Reply to this note

Please Login to reply.

Discussion

That's why it's not reliant on it. If it gets attacked then that's that, the site is still running, just not in pristine condition. That's about it.

And yeah that can work too, in the app/setting page there'd be:

Title: Caching Server [button: add]:

Subtitle: Official servers:

cahcing.degmods.com [button: unset]

Subtitle: Recommended servers:

caching.example1.com [button: set]

caching.example2.com [button: set]

caching.example3.com [button: set]

Subtitle: Custom/user servers:

input-field [button: add]

caching.exampleCustom.com [button: set]

This can be a nip too, now that I think about it.