joeruelle on Nostr: Ah yes, I was thinking more along the lines of counts and such that a client can only ...

Ah yes, I was thinking more along the lines of counts and such that a client can only achieve with some kind of central-server model, and that users would therefore be trusting the client on (seeing as they can't get such accurate counts from the protocol itself.) But I didn't think about blocked/delayed sync for notes themselves as a dark tactic, that's an interesting thought.

Where I'm a little confused still is why this cacheing sometimes seen as a looming threat to the model when it's just on the read side? I'd totally get it if it was on the write side too, but if just on the read side then it seems to be benign enough, like watching live events streamed on YouTube but things being buffered a few minutes for smoothness.