I do have a local relay that aggregates from multiple public...

d475ce4b39775071...

npub1636uujeewag8zv8593lcvdrwlymgqre6uax4anuq3y5qehqey05sl8qpl4

hex

6e74b472a578fafaedb145a134650be2e3416b25b91116205b2a2373ebaaa9e7

nevent

nevent1qqsxua95w2jh37h6akc5tgf5v5979c6pdvjmjygkypdj5gmnaw42necprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdgawwfvuhw5r3xr6zcluxx3h0jd5qpuawwn27e7qgj2qvmsvj86gl7cng9

Kind-1 (TextNote)

2026-05-07T06:36:20Z

↳ Reply to ChipTuner (npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7)

Yes. This also goes with most services as well. For example, my rate limits are targed for end-users. I can't really know the difference between a cen...

I do have a local relay that aggregates from multiple public relays, but I’m deliberately limiting the scope of kinds I’m pulling in. But I am being oportunistic about events that don’t fall into my immediate sphere of concern, and those I try to fetch on demand, when they come up.

So I might find a highlight, then look for the article it’s referencing. Of find a nested kind:1 in an article and try to fetch that, then it’s comments/thread.

It all revolves around articles, so I’m not storing all possible kind:1s, for instance.

I’m trying to scale it down enough so I don’t have to negotiate with relays for extra access, so I can keep my client resilient to decentralization of relays and do outbox.

On the other hand, I’ll invariably end up with most traffic going through major relays, so yes, we’ll likely need to coordinate that.

Raw JSON

{
  "kind": 1,
  "id": "6e74b472a578fafaedb145a134650be2e3416b25b91116205b2a2373ebaaa9e7",
  "pubkey": "d475ce4b3977507130f42c7f86346ef936800f3ae74d5ecf8089280cdc1923e9",
  "created_at": 1778135780,
  "tags": [
    [
      "e",
      "066bb2ee252c41132f518b408ebbee6b5c300a8c218e63eb6f3a9448e719146a",
      "wss://relay.damus.io/",
      "root",
      "52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd"
    ],
    [
      "e",
      "7ce4825dc938150ea822cf181ede9a7a8eea8fdcea6172010e2241d4141c2dfb",
      "wss://relay.damus.io",
      "reply",
      "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
    ],
    [
      "p",
      "52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd"
    ],
    [
      "p",
      "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
    ]
  ],
  "content": "I do have a local relay that aggregates from multiple public relays, but I’m deliberately limiting the scope of kinds I’m pulling in. But I am being oportunistic about events that don’t fall into my immediate sphere of concern, and those I try to fetch on demand, when they come up. \n\nSo I might find a highlight, then look for the article it’s referencing. Of find a nested kind:1 in an article and try to fetch that, then it’s comments/thread. \n\nIt all revolves around articles, so I’m not storing all possible kind:1s, for instance.\n\nI’m trying to scale it down enough so I don’t have to negotiate with relays for extra access, so I can keep my client resilient to decentralization of relays and do outbox. \n\nOn the other hand, I’ll invariably end up with most traffic going through major relays, so yes, we’ll likely need to coordinate that.",
  "sig": "c8a3c068655179d2f6bbb03a14697553b64ffae993884bcd6b5076a47c69ff4793ac74ecbc3b9b996d19d863e1e975e592b2afe1ea43f6672127bb7c41e3ff80"
}