I thought I could just use your 24h implementation and remov...

Leo Wandersleb

npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6

hex

627f4322e3634c6515dca79730221c2600b55e5b11aeb2a3ed18febd0951b446

nevent

nevent1qqsxyl6ryt3kxnr9zhw209esygwzvq94ted3rt4j50k33l4ap9gmg3sprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsydl97xpj74udw0qg5vkfyujyjxd3l706jd0t0w0turp93d0vvungjzghtm

Kind-1 (TextNote)

2026-04-27T07:23:12Z

↳ 回复 Cody (npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl)

What’s the difference between "Pulse" and "24h Pulse"? 🤔 Does "Pulse" load all recent events from your follows? I feel like that might run into some p...

I thought I could just use your 24h implementation and remove the 24h limit. It does a great job (although I'm not sure of that) to find all follows 24h events. It should need a limit, too and go for more if limit is hit. But clanker does a bad job doing the following:

Remove the 24h constraint. At EOSE, remove all authors that already have 10 events from subsequent rounds. Repeat REQ with until:$dateOfOldestEvent. Until you have the newest events of all follows.

Somehow, checking the profiles of follows where no events were found, finds events now, so something is wrong with my relay selection. Somehow, things get really ugly as soon as I ckeck profiles and unfollow users ... Now the numbers start jumping around, the design starts shifting as a consequence of users jumping between some and no events...

原始 JSON

{
  "kind": 1,
  "id": "627f4322e3634c6515dca79730221c2600b55e5b11aeb2a3ed18febd0951b446",
  "pubkey": "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
  "created_at": 1777274592,
  "tags": [
    [
      "e",
      "af176376ecab4d12664b1715a55d72e6a56d41b3462439a49f5694fee38a4a6a",
      "wss://nos.lol/",
      "root",
      "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
    ],
    [
      "e",
      "a6322997db06406737148e41c3abeddfd3c0149541fa685c77588ea216027e0c",
      "wss://relay.primal.net/",
      "reply",
      "8125b911ed0e94dbe3008a0be48cfe5cd0c0b05923cfff917ae7e87da8400883"
    ],
    [
      "p",
      "8125b911ed0e94dbe3008a0be48cfe5cd0c0b05923cfff917ae7e87da8400883"
    ],
    [
      "client",
      "jumble"
    ]
  ],
  "content": "I thought I could just use your 24h implementation and remove the 24h limit. It does a great job (although I'm not sure of that) to find all follows 24h events. It should need a limit, too and go for more if limit is hit. But clanker does a bad job doing the following:\n\nRemove the 24h constraint.\nAt EOSE, remove all authors that already have 10 events from subsequent rounds.\nRepeat REQ with until:$dateOfOldestEvent.\nUntil you have the newest events of all follows.\n\nSomehow, checking the profiles of follows where no events were found, finds events now, so something is wrong with my relay selection.\nSomehow, things get really ugly as soon as I ckeck profiles and unfollow users ... Now the numbers start jumping around, the design starts shifting as a consequence of users jumping between some and no events...",
  "sig": "8ef76e52d9221efacb4134d0d4b6ead43fc8dc31034cb961a7e82a988c8c0c5e056ebddd57682af7b986d52eae30728d4db3974fc5742ff99a4939b99728f027"
}