1. Relays can ignore it (my implementation currently does ignore it, which is wrong, and I think it's a client choice to include the references, if the client doesn't include anything the relay should just accept it), but I don't think it's hard, you can keep the past x message ids in memory and check against that, no?
2. I agree, but I also don't think most people expect anything super secure when they see the word "private". That's probably the expectation of just a few nerds. I think clients can use different wording though.
3. That's easy to do, we already have a kind that is a request to join, we can just shove a secret into that. But, again, public groups where anyone can join do exist on Telegram and have huge adoption. I was thinking that relays could do some basic filtering of who is entering -- like checking if they have some WoT ties to other people that are in the group, for example.
fiatjaf /
npub180c…h6w6
2024-07-05 19:58:28
in reply to nevent1q…v2vs
Author Public Key
npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6Published at
2024-07-05 19:58:28Event JSON
{
"id": "cb542c5ca54d515381e5665dd8def30a5c83aa42a981bba0cb12989773ecf5b9",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1720202308,
"kind": 1,
"tags": [
[
"client",
"gossip"
],
[
"p",
"7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
],
[
"p",
"c5cfda98d01f152b3493d995eed4cdb4d9e55a973925f6f9ea24769a5a21e778"
],
[
"p",
"50809a53fef95904513a840d4082a92b45cd5f1b9e436d9d2b92a89ce091f164"
],
[
"e",
"0348a66ff5586842df16ffa97e03864c1d5f95f05325f4673680ecdd645ae32a",
"wss://nostr.mom/",
"root"
],
[
"e",
"68544145ed1d2e3e39b0c86351bfc05c969a8c431e672c8d7bd7f413e10e2f77",
"wss://nostr.wine/",
"reply"
]
],
"content": "1. Relays can ignore it (my implementation currently does ignore it, which is wrong, and I think it's a client choice to include the references, if the client doesn't include anything the relay should just accept it), but I don't think it's hard, you can keep the past x message ids in memory and check against that, no?\n\n2. I agree, but I also don't think most people expect anything super secure when they see the word \"private\". That's probably the expectation of just a few nerds. I think clients can use different wording though.\n\n3. That's easy to do, we already have a kind that is a request to join, we can just shove a secret into that. But, again, public groups where anyone can join do exist on Telegram and have huge adoption. I was thinking that relays could do some basic filtering of who is entering -- like checking if they have some WoT ties to other people that are in the group, for example.",
"sig": "120bbc631d46a777656dec90e595fcb310e9a88a4f0e16d1429cd660605e2cf7c98bebb78c3e4a1ba605dc0b8589c3da64378c6ddc619f075c57559ec1efd6ef"
}