laurel on Nostr: NOSTR Ramblings Been looking into nostr. Those relays they keep talking about are not ...
NOSTR Ramblings
Been looking into nostr. Those relays they keep talking about are not like fedi servers. They just store messages. For instance the "profile" kind-0 message doesn't include followers/following . Rather only a public key, some custom text, and a signature. And this is by design since every relay has a profile stored for each corresponding message posted and of course a followers/following list gets updated dynamically which means that if it was included in the "profile" it would differ from relay to relay depending on when it was updated.
Their solution is to allow the user to publish a message of kind-3 that is his following list, which may or may not be updated and may or may not be true all together. Oh, and to get a follower list you need to donwload every following list that is available, and grep them for the nick you are interested in. Then subscribe for updated following lists and do the same thing every time someone updates those that he follows and wishes to disclose.
Relays being basically messaging servers (think XMPP) with PGP for auth. All the social networking part of the network falls on the "clients". And of course there is no real spec for the client. The docs don't even really make a distinction between a client that just publishes messages with a single private key and a full blown web app that stores social graphs, following lists, and basically creates a social network out of the messages that get propagated through the relays.
tldr: AP is social networking infrastructure. Nostr is a messaging system spec on top of which people are trying to build social networks without any common spec.
91140dc27b1e676e88052be3f0a5f0cdab4a7ea9d155c2a3a2d310cdaa7a2b55.jpg
Been looking into nostr. Those relays they keep talking about are not like fedi servers. They just store messages. For instance the "profile" kind-0 message doesn't include followers/following . Rather only a public key, some custom text, and a signature. And this is by design since every relay has a profile stored for each corresponding message posted and of course a followers/following list gets updated dynamically which means that if it was included in the "profile" it would differ from relay to relay depending on when it was updated.
Their solution is to allow the user to publish a message of kind-3 that is his following list, which may or may not be updated and may or may not be true all together. Oh, and to get a follower list you need to donwload every following list that is available, and grep them for the nick you are interested in. Then subscribe for updated following lists and do the same thing every time someone updates those that he follows and wishes to disclose.
Relays being basically messaging servers (think XMPP) with PGP for auth. All the social networking part of the network falls on the "clients". And of course there is no real spec for the client. The docs don't even really make a distinction between a client that just publishes messages with a single private key and a full blown web app that stores social graphs, following lists, and basically creates a social network out of the messages that get propagated through the relays.
tldr: AP is social networking infrastructure. Nostr is a messaging system spec on top of which people are trying to build social networks without any common spec.
91140dc27b1e676e88052be3f0a5f0cdab4a7ea9d155c2a3a2d310cdaa7a2b55.jpg