> so what you're saying is that if the limit isn't exceeded in the initial results before the EOSE that the subscription is open indefinitely?
No. Not even close to what I'm saying.
```
["REQ", "testing-subs", { kinds: [1], limit: 1 }]
```
means create a subscription, called testing-subs, looking for kinds 1, start with 1 single event you have in your database, then keep going.
Running that query will result in the relay sending you exactly one event, followed by an EOSE to testing-subs, and then sending you new events every time a new kind 1 is published.
If you don't trust my code, despite its simplicity, here's the same result from nak, fiatjaf's (the creator of nostr) official nostr cli tool
you can see that it generates the exact same query I wrote:
and if even that is not proof here is the code on
strfr:
astro:
> ok, but see, i'm a relay dev. i have a much better understanding of protocols than the average client dev
I made this clear a lot, I'm not a good developer, but I am good enough to read the documentation and understand how it's supposed to work.
I know for a fact that I am correct, I have double checked with 5 different relays, they all work the way I said they do