Relays should be as discriminatory as they please, totally! ...

npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6
hex
5e39b025e71f041025440c4a7f070ee49cc783e398f2d18e948c9e1219e0fc40nevent
nevent1qqs9uwdsyhn37pqsy4zqcjnlqu8wf8x8s03e3uk3362ge8sjr8s0csqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsydl97xpj74udw0qg5vkfyujyjxd3l706jd0t0w0turp93d0vvunggwxlzqKind-1 (TextNote)
↳ 回复 3bf0c63f... (npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6)
Another issue: can relays be really "dumb" in the way you're implying? I don't think so. If a relay should just accept anything without filtering (as...
Relays should be as discriminatory as they please, totally! I hope to see many relays with all kinds of trade-offs. There's not point in telling relays what to do but I want a client that can produce great results when reading from all relays and not just one unless that one is my trusted relay that does the heavy lifting for me - like event de-duplication.
But the default is that I don't trust your relay and I would hate to give you the power to even delay the delivery of events to me.
So maybe the confusion is that these are all "relays" and I would hate people to only read from the primal relay while you are talking about proxy/caching relays. I think you say "read" relay. Inbox/outbox, ... it's all a bit confusing.
原始 JSON
{
"kind": 1,
"id": "5e39b025e71f041025440c4a7f070ee49cc783e398f2d18e948c9e1219e0fc40",
"pubkey": "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
"created_at": 1771764168,
"tags": [
[
"e",
"bbb18519803ac7084915c3dcb3e8cc507664ca1d3633d09147ff3b8599fa19ad",
"wss://relay.damus.io/",
"root",
"46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
],
[
"e",
"f3555e12bd193ea2deb72561656f0df3d3740593725eac922decd485fc077352",
"wss://relay.damus.io/",
"reply",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"client",
"jumble"
]
],
"content": "Relays should be as discriminatory as they please, totally! I hope to see many relays with all kinds of trade-offs. There's not point in telling relays what to do but I want a client that can produce great results when reading from all relays and not just one unless that one is my trusted relay that does the heavy lifting for me - like event de-duplication.\n\nBut the default is that I don't trust your relay and I would hate to give you the power to even delay the delivery of events to me.\n\nSo maybe the confusion is that these are all \"relays\" and I would hate people to only read from the primal relay while you are talking about proxy/caching relays. I think you say \"read\" relay. Inbox/outbox, ... it's all a bit confusing.",
"sig": "94fa4e0eb37ca5a6991354c7cba799db6158ccb75ee23e3966db642eda0fb916645ebe54df287e2180c72fbbfac77cfbed888771bd00227de209ed3e02bbe59b"
}