The influencer use-case was just an example. We can think of...

3bf0c63fcb934634...

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

hex

48e53049840d33161babed8a583da9910c5247aac9f63dec048f88d9d943fece

nevent

nevent1qqsy3efsfxzq6vckrw47mzjc8k5ezrzjg74vna3aaszglzxem9plansprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8g6dvldv

Kind-1 (TextNote)

2026-02-22T03:30:40Z

↳ 回复 Leo Wandersleb (npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6)

But relays allow me to provide very long lists of pubkeys to filter what I want to see. I can get all from my WoT and work from there. The influencer...

The influencer use-case was just an example. We can think of others. I could prefer to use a different filtering criteria than follows-of-follows, maybe using 3 levels, or 2, maybe I want people to be known to publish about certain topic (according to an LLM judgement) for a while before I read their stuff, I don't know, there are many possibilities, and the client can pick and choose any by just switching their "read" relays.

The alternative of doing it on the client, even if it was possible in practice, would require a huge number of clients or a lot of complex implementations in the same client.

原始 JSON

{
  "kind": 1,
  "id": "48e53049840d33161babed8a583da9910c5247aac9f63dec048f88d9d943fece",
  "pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
  "created_at": 1771731040,
  "tags": [
    [
      "e",
      "bbb18519803ac7084915c3dcb3e8cc507664ca1d3633d09147ff3b8599fa19ad",
      "wss://relay.damus.io/",
      "root",
      "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
    ],
    [
      "e",
      "0308f5b0f5f22bceeff51fda26bb17dd86f6d5ece46f25aa40c5094444a2ada3",
      "wss://relay.damus.io/",
      "reply",
      "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
    ],
    [
      "p",
      "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
    ]
  ],
  "content": "The influencer use-case was just an example. We can think of others. I could prefer to use a different filtering criteria than follows-of-follows, maybe using 3 levels, or 2, maybe I want people to be known to publish about certain topic (according to an LLM judgement) for a while before I read their stuff, I don't know, there are many possibilities, and the client can pick and choose any by just switching their \"read\" relays.\n\nThe alternative of doing it on the client, even if it was possible in practice, would require a huge number of clients or a lot of complex implementations in the same client.",
  "sig": "51f8975c4c3e9628b2b010fd67a7d4e536a8c7bc5bb4078d8519e3f4d5a43bcb7485b3cb0f5686249a1a1eaa36ec0065bcd9555bf65dd53bcd84f9a9c1981cee"
}