TL;DR if you can’t read the code: the client architecture is heavily reliant on a centralized caching server and often trusts it as is

your relays determine maybe some and reads, and event writes, that is it nostr:note1lmvcjjls0zwh49sexphrzg3rp5l9l5lu9wpfm8f8qd5x07kd7zcs5p4zyx

Reply to this note

Please Login to reply.

Discussion

User experience suggests the caching server isn’t even all that fast. Serving up posts from days or weeks ago and not reading/caching real time notes from a wide enough variety of relays.

I don't really get the point of the caching server. Seems like a bottleneck. 🤷🏻‍♀️

Is that where they make copies of the media, that they then replace in the original rendered events?

You can just use an alternative caching service or use none at all.

The cache provides a smoother user experience but they support user choice.

The app literally doesn’t work without it. Source: I tried it, instead of blindly trusting.

good thing we have alternative apps then. What a blessing

check