> I spelled your name wrong in the audio, my bad. I got it right in the show notes though 😅.

No problem.

> I mentioned your nhttp project.

You summoned me.

> What is the problem subscription limits and nostr clients/relays?

You see, So in nostr, basically fetching notes is done by opening an subscription (by example, an subscription named "sub1" was requested to relay for notes from an user). The more sub you open, The busier the relay became as it wants to send you live events.

As the result, Relay software implemented a way to limit numbers of subscription which was useful for small server. But because of this limit, There are nostr client that went brutal because of this.

There are cases when a nostr client opening and closing a sub too quickly at every scrolls (the goal was to get rid of sub limitation). Because you opened a sub and then closed it under 5 seconds, This is brutal for some users especially the one that were limited on bandwidth, or even have high ping to a relay.

If you are experienced programmer, Well, Due to TCP nature, You can't simply close an busy sub. Because the packets is still not complete yet, So it's still downloading until it was done. You will need to wait for seconds till it was actually closed, which then you could open another one later on but again, you can't simply close it again if it was busy sub.