Let me know what you think, nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4 nostr:npub1q84c9lheynjl33u6ha5ulfdd25yw0p90w2zqx6f23w6cjrn7w76s373p35 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z, here's the code: https://github.com/nbd-wtf/go-nostr/blob/c37ed1a309e329cd60a0b3218c5570b4ad1587f6/nip77/idsonly.go

nostr:nevent1qqsqqq9xxwmm9sh6e03uzntwht3kfl4pxysr5yj94uvv3ljkzn2hqvqpz4mhxue69uhkzet8d9ejuat50phjummwv5hszrnhwden5te0dehhxtnvdakz7qg3waehxw309ahx7um5wgh8w6twv5hs6lurxg

Reply to this note

Please Login to reply.

Discussion

Do you use the same limits for IDs as you have for full events? Because since there is no `created_at`, if the relay limits in 500 events, its impossible to make a filter that gets the next 500 events. :(

In my tests strfry doesn't impose any limits, which makes this flag very dangerous. On khatru you can often specify a different limit for Negentropy than for normal queries, and it defaults to basically infinite if I remember correctly.

This is the issue