Hacker News new | past | comments | ask | show | jobs | submit login

Perhaps you could avoid some pitfalls, which only become obvious when the practical application of the protocol is scaled. I have not dived deep into either nntp or nostr, but existing standards might offer useful considerations that could be reused. For example, it seems like nntp exchanges first a list of articles and clients only download the ones they don't have already. Does nostr do something similar? Like being able to get a list of event ids with minimal metadata and clients can selectively request the whole event data afterwards. As events might contain bigger text blobs, that could be important for performance or for adding placeholders to the UI. In general, it seems to me that nostr and nostr clients might need to come up with good strategies for caching and bandwith optimizations, considering the decentralized design. But please correct me if I am wrong.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: