Oddbean new post about | logout
▲ ▼
Vitor Pamplona | 3 months ago (raw) | root | parent | reply | flag +3 
 % of all nostr keys. 

But once the client receives the data, it can filter further to the matching IDs. So, you will see the same thing, but there will be X number of posts returned that are not in your follow lists.

i.e. errors consume data but doesn't change your UX
▲ ▼
David A. Harding | 3 months ago (raw) | root | parent | reply | flag +1 
 So you save 50 kb on the query but may receive a response that's bloated by potentially more than 50 kb of unwanted data?
▲ ▼
Vitor Pamplona | 3 months ago (raw) | root | parent | reply | flag +1 
 Good point, I am not sure how heavy the error rates would be. We might need to decrease the error % as new users join the protocol 🤔

But keep in mind filters change every second on Amethyst. So, it's 60kb per second in exchange of the added payloads from the errors ONCE.