Oddbean new post about | logout
 Just downloading them and processing on memory is already a pain.  
 I'm not suggesting downloading all events from the entire WoT.  I'm just saying that you add WoT limiting to existing filters that were already working fine.  So it will download strictly less.  It's just that the filter would be a huge list that may be too much for relays to handle. So I plan to just leave the REQ filters as they are and filter the results client-side.  But I wanted to see what others have done since many have walked this road already. 
 Yeah, but in order to assemble the massive filter, you have to download all contact lists, which I already don't like doing. It compounds with the massive filter. 

I am building custom feeds for Amethyst and I was wondering if we could build a feed event and then make a REQ by the feed event id that the relay already has. That would be nice. We could then do a follows of follows of follows of follows filter.  
 we do this in several steps, 100 keys/req. Still a pain in the ass, takes quite a long time for big WoT, but easier to handle in the server side. 
 That is interesting. 
 I think that would have to be a DVM.  I couldn't expect all relays to do this potentially complex logic. 
 there are 50k pubkeys in follows of my follows (one hop only).  so ya, its a huge list. 
 is that including duplicates? 
 no duplicates 
 Oh wow