1M bounty for whoever gets this merged with proper websockets and handling nprofiles/npubs to fetch the profile name. Fetching follower counts can be done with a `COUNT` to relay.nostr.band (or configurable relay as query parameter), but if you can think of something else better to put in there instead of follower counts that will be great.
nostr:nevent1qqsymzd2mgusq390enrj6eeshyjpu0nxaxsd0lu928wj2ee0cfdyhespz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygrwg6zz9hahfftnsup23q3mnv5pdz46hpj4l2ktdpfu6rhpthhwjvpsgqqqqqqsm9xgpp 

 Try licensing. Less dirty that way.
😉 

 bloom filters of the event IDs and the user IDs will help a lot for fast elimination of non-matches

maybe some kind of "current list" event with the account fingerprints - i dunno how good npub entropy is but probably the first 12 bytes zero chance of collisions within one user's follow list, probably 8 bytes is enough - to make actually finding the nprofiles easier 

 Is a bloom filter faster than a hashset or a linked list in this case? 

 are we talking about smt like this?
https://void.cat/d/JXeQTwF6VpjpkU9oXfaCsC.webp 

 #bounty 

 Why block @Sats