Sorry, I'm kinda wrong here, the stream events API is fine, ...

reya

npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445

hex

584aa091a3560135f33f94e182af84a966584cdfea023290e0d9d3d33be17e16

nevent

nevent1qqs9sj4qjx34vqf47vlefcvz47z2jejcfn075q3jjrsdn57n80shu9sprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgspycgrhlwu3he9ddhq407h7duheqxucn4g3a7zlp7agyzzyz6dvhczcctxq

Kind-1 (TextNote)

2026-05-20T05:32:06Z

Sorry, I'm kinda wrong here, the stream events API is fine, but the problem is the negentropy part in gossip. After removed the negentropy sync and force to use typical stream events API, gossip is became very fast.

Other temporary fix is set timeout for gossip sync very low like this:

GossipConfig::default()
                .sync_initial_timeout(Duration::from_millis(100))
                .sync_idle_timeout(Duration::from_millis(100)),

So I think we should have an option to disable negentropy, also I think it will better if we have an API for client dev manual run gossip fetch for a Public Key

cc nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet , nostr:npub1qqqqqq2stely3ynsgm5mh2nj3v0nk5gjyl3zqrzh34hxhvx806usxmln03

nostr:nevent1qvzqqqqqqypzqynpqwlamjxly44kuz4l6lehjlyqmnzw4z8hctu8m4qsggstf4jlqy28wumn8ghj7un9d3shjtnjv4ukztnnw5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qqsvnzc89keuyl5xyuz8zrnnmvgmq8uv363sn26dfkhynnsrp7f06wckr45wk

Raw JSON

{
  "kind": 1,
  "id": "584aa091a3560135f33f94e182af84a966584cdfea023290e0d9d3d33be17e16",
  "pubkey": "126103bfddc8df256b6e0abfd7f3797c80dcc4ea88f7c2f87dd4104220b4d65f",
  "created_at": 1779255126,
  "tags": [
    [
      "q",
      "c98b072db3c27e862704710e73db11b01f8c8ea309ab4d4dae49ce030f92fd3b",
      "wss://relay.reya.su/",
      "126103bfddc8df256b6e0abfd7f3797c80dcc4ea88f7c2f87dd4104220b4d65f"
    ],
    [
      "p",
      "68d81165918100b7da43fc28f7d1fc12554466e1115886b9e7bb326f65ec4272"
    ],
    [
      "p",
      "00000001505e7e48927046e9bbaa728b1f3b511227e2200c578d6e6bb0c77eb9"
    ]
  ],
  "content": "Sorry, I'm kinda wrong here, the stream events API is fine, but the problem is the negentropy part in gossip. After removed the negentropy sync and force to use typical stream events API, gossip is became very fast.\n\nOther temporary fix is set timeout for gossip sync very low like this:\n```\nGossipConfig::default()\n                .sync_initial_timeout(Duration::from_millis(100))\n                .sync_idle_timeout(Duration::from_millis(100)),\n```\n\nSo I think we should have an option to disable negentropy, also I think it will better if we have an API for client dev manual run gossip fetch for a Public Key\n\ncc nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet , nostr:npub1qqqqqq2stely3ynsgm5mh2nj3v0nk5gjyl3zqrzh34hxhvx806usxmln03 \n\nnostr:nevent1qvzqqqqqqypzqynpqwlamjxly44kuz4l6lehjlyqmnzw4z8hctu8m4qsggstf4jlqy28wumn8ghj7un9d3shjtnjv4ukztnnw5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qqsvnzc89keuyl5xyuz8zrnnmvgmq8uv363sn26dfkhynnsrp7f06wckr45wk",
  "sig": "b85027ae9cca50b045423a9020c4633d60469aa5024018531ab5f7d44ad4ab6704aea7419d4388eef056e45b164706659e6441140e00015d1d342c89eca28620"
}