My guess is that most of what you’re running into is due to ...

Cody

npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl

hex

190059aaba176b3f028b43d7055552d2cd028b4842475a48a532c12177af32ca

nevent

nevent1qqspjqze42apw6elq29584c924fd9ngz3dyyy366fzjn9sfpw7hn9jsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcmp4p05

Kind-1 (TextNote)

2026-04-27T07:55:28Z

↳ 回复 Leo Wandersleb (npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6)

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 2...

My guess is that most of what you’re running into is due to the browser’s WebSocket connection limits. Jumble really isn’t well suited for browsing the following feed right now.

You might notice that after loading the following feed, actions like posting, reposting, or reacting start failing with relay connection errors. That’s the browser hitting its limit on concurrent connections.

I’ve been working on packaging Jumble as an Electron app to get around these browser limitations. That should improve things quite a bit.

原始 JSON

{
  "kind": 1,
  "id": "190059aaba176b3f028b43d7055552d2cd028b4842475a48a532c12177af32ca",
  "pubkey": "8125b911ed0e94dbe3008a0be48cfe5cd0c0b05923cfff917ae7e87da8400883",
  "created_at": 1777276528,
  "tags": [
    [
      "e",
      "af176376ecab4d12664b1715a55d72e6a56d41b3462439a49f5694fee38a4a6a",
      "wss://nos.lol/",
      "root",
      "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
    ],
    [
      "e",
      "627f4322e3634c6515dca79730221c2600b55e5b11aeb2a3ed18febd0951b446",
      "wss://pyramid.fiatjaf.com/inbox",
      "reply",
      "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
    ],
    [
      "p",
      "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
    ],
    [
      "client",
      "jumble"
    ]
  ],
  "content": "My guess is that most of what you’re running into is due to the browser’s WebSocket connection limits. Jumble really isn’t well suited for browsing the following feed right now.\n\nYou might notice that after loading the following feed, actions like posting, reposting, or reacting start failing with relay connection errors. That’s the browser hitting its limit on concurrent connections.\n\nI’ve been working on packaging Jumble as an Electron app to get around these browser limitations. That should improve things quite a bit.",
  "sig": "9f5e837b3d9c23a7722982e8b8f4851ea0290f548f77ab36520110e7cfb6ae096c51a1eb754f7b15c3f871830437091146df56a746aac6a03e96c2c8b450e6ff"
}