5 ms·
Does somebody know whether the same or something similar could be achieved by using the "Network News Transfer Protocol" (nntp), without designing a whole new p
by snowstormsun 4y ago
Does somebody know whether the same or something similar could be achieved by using the "Network News Transfer Protocol" (nntp), without designing a whole new protocol?
- thinkmassive 4y agoFrom the Wikipedia page: > NNTP is an application protocol used for transporting Usenet news articles (netnews) between news servers, and for reading/posting articles by the end user client applications. nostr relays are not supposed to connect with other relays (I think to avoid the inevitable concentration of centralized hubs), which is a small but very significant difference
- fiatjaf 4y agoWhat would we gain by doing that?
- Karrot_Kream 4y agoAccess to the existing NNTP infrastructure. It's not worth it IMO, the state of NNTP servers is quite bad.
- snowstormsun 4y agoPerhaps 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.