Better code quality, basically. With each subscription managed separately, we could time them better (sending most important stuff first, relay starts processing then send the rest), we could store the EOSE in the sub object itself instead of one EOSE for all queries involving a user and then having to find the minimum EOSE when more than one user is put together in the same call, etc..  

 im limited out again, was working for a day or so with 925 follows.. now the error is back.

ill ask doug and try to find the performance (or other) implications of the two options.  1) increase strfry hardcoded buffer limit,  2) increase subs (already done but nobody tries it except probably scrapers). 

 It would be nice to raise (10x) the buffer limit on the default strfry setting. I feel like lots of people are running into this issue with lots of different relays out there.  

 yep, i suspect it makes nostr feel artificially ded.  still unsure why im hitting the ceiling and where the sweet spot is that i need to decrease my follows to for it to work.

does amethyst fire off req queries for ALL lists, even when theyre not selected in the ui by chance?

ill let u know what i find out about the buffer vs subs.. 

 It will fire for the feed selected up top. If it is "All Follows" that means all pubkeys + t tags + g tags + communities + chats you might have "joined" it is in your kind 3. 

Here is the code that assembles the Home feed REQ: https://github.com/vitorpamplona/amethyst/blob/main/amethyst/src/main/java/com/vitorpamplona/amethyst/service/NostrHomeDataSource.kt