Thanks for the response man. I was trying to figure that out and I don't know the NIPs like the back of my hand quite yet. I've been following Nostr and dabbling with it since there were like 17 NIPs and the protocol was much simpler and keeping up with this stuff can be hard as it's happening fast, I need an RSS feed (or a Nostr bot?) to help me keep track of all the changes.
So there are 3 ways you can get relays to fetch from, the NIP-02 way, the way I'm talking about where they're in the content (and they're the recipient's relays, not a dump of all follows relays if I understand that correctly?) and the NIP-65 way? I ask because I'm working on something and I want to make sure to cover all my bases and implement everything I need to implement to satisfy users.
An aside, I quite like the NIP-02 way of storing them with one caveat: I think the field for a relay in the p tag should be a list of relays as this would help with censorship resistance. I really like a simpler protocol, and I like the idea of client side storage of feeds, I've actually got a client I'm in the very beginning stages of building that is focused largely on user definable client side feeds, but it is on the backburner in favor of a CLI utility that uses bittorrent and nostr to enable media sharing.
mister_monster
npub1m5…jgjl3
2024-08-29 17:06:23
in reply to nevent1q…lnp4
Author Public Key
npub1m5s9w4t03znyetxswhgq0ud7fq8ef8y3l4kscn2e8wkvmv42hh3qujgjl3Published at
2024-08-29 17:06:23Event JSON
{
"id": "2ce5dc06cdb53c5cca62381c54a5aaa152e7a81236601ccf691f45b5d41959a8",
"pubkey": "dd2057556f88a64cacd075d007f1be480f949c91fd6d0c4d593baccdb2aabde2",
"created_at": 1724951183,
"kind": 1,
"tags": [
[
"e",
"000060fd71eef355cf92cc70722baf7042b5c27482cb78339fe7b563bb9e871c",
"",
"root"
],
[
"e",
"e6a6ba2435a4377bfa9cce1f15903cea5f721597ae296aa331dbfb69891f7b98"
],
[
"e",
"621d1a5b740525d763b8dea1541da216d74e239daa6c6043682e0dc7e7cb2bec",
"",
"reply"
],
[
"p",
"dd2057556f88a64cacd075d007f1be480f949c91fd6d0c4d593baccdb2aabde2"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49"
],
[
"monero",
"8AC3x3ZkW2hYm7Sr888ZexDTAywHZyGoPYUDbYojgkB9L8r6L8YbrwZibxg28q3t6GZpacpkzVEnD798eYar2aMQQzV9CiS",
"1.0"
]
],
"content": "Thanks for the response man. I was trying to figure that out and I don't know the NIPs like the back of my hand quite yet. I've been following Nostr and dabbling with it since there were like 17 NIPs and the protocol was much simpler and keeping up with this stuff can be hard as it's happening fast, I need an RSS feed (or a Nostr bot?) to help me keep track of all the changes.\n\nSo there are 3 ways you can get relays to fetch from, the NIP-02 way, the way I'm talking about where they're in the content (and they're the recipient's relays, not a dump of all follows relays if I understand that correctly?) and the NIP-65 way? I ask because I'm working on something and I want to make sure to cover all my bases and implement everything I need to implement to satisfy users.\n\nAn aside, I quite like the NIP-02 way of storing them with one caveat: I think the field for a relay in the p tag should be a list of relays as this would help with censorship resistance. I really like a simpler protocol, and I like the idea of client side storage of feeds, I've actually got a client I'm in the very beginning stages of building that is focused largely on user definable client side feeds, but it is on the backburner in favor of a CLI utility that uses bittorrent and nostr to enable media sharing.",
"sig": "02c475cdd69143867ad25ede28c3c9c522c6d00f3ee4706f53f20082d09a893d3fbb082b2ce06edb443d29e95e2e3c52e8711fe4c77ad3ed5d82299da9414a97"
}