4 ms·
Unlike web scraping where spaghetti logic is required to follow abstracted JS links, archival of nostr events can be as simple as running a relay and mirroring
by jron 2y ago
Unlike web scraping where spaghetti logic is required to follow abstracted JS links, archival of nostr events can be as simple as running a relay and mirroring blog content.[1][2] nostr does a lot of what NNTP did but with additional flexibility.
[1] https://logperiodic.com/rbsr.html#nostr https://logperiodic.com/rbsr.html#nostr
[2] https://github.com/hoytech/strfry/blob/master/docs/negentropy.md https://github.com/hoytech/strfry/blob/master/docs/negentrop...
- troupo 2y agoFor that you will need to connect to all relays in existence, right?
- jron 2y agoUsers currently tend to push events to massive relays but decentralization is still a goal: https://raw.githack.com/dtonon/oracolo/master/examples/fiatjaf.html#1e950a50c95d11266258912d91ce116380e48b18f3c2c39ec60a42d66cdc3427 https://raw.githack.com/dtonon/oracolo/master/examples/fiatj... https://github.com/nostr-protocol/nips/blob/master/65.md https://github.com/nostr-protocol/nips/blob/master/65.md Still, the short answer to your question would be "yes."
- dtonon 2y agoNot necessarily, the gossip/outbox model (NIP-65) tells clients which relays they should check: https://mikedilger.com/gossip-model/ https://mikedilger.com/gossip-model/ It is of course possible to combine this approach with undifferentiated access to well known relays, to fetch content from not followed people.