glad to hear you’re considering open sourcing it (or parts of it at least)
i’d be keen to open it up and have a look at the code if it’s not too daunting, because i’m still curious as to what exactly it does
does it only grab notes from followers, and followers of those followers? and then does it only grab the profile information of those people too?
i’ve seen you’ve updated the explanation on github since i first signed up, so i should probably go have a closer re-read now
It’s a bit more complex than that. We have a large aggregator relay that gathers events from all of our read relays. Filter is a custom websocket that sits in front of of our aggregator and augments user requests to their follows+follows network. There are several additional background parts to maintain and update each users followers, broadcast events, manage paid accounts, and several more. It wouldn’t be practical for an individual to run for themselves without large modifications.
hmmm interesting, how does searching for hashtags work when running the wine filter?
i feel like it’s only returning anything that involves my followers, which is handy in some situations, but in a lot of cases i’d want to search a hashtag and get the full global results (for discoverability)
maybe i’m just misunderstanding how hashtag searches work though? (i’m using damus)
No, we do not augment hashtag searches or anything else (besides global). You can also get our spam filtered full global view (not just your follows+follows) by adding global=all to your websocket url. It’s still experimental, but was a requested feature.
ahhh hah, i might give that a whirl, so that keeps your feed as is, but it makes global just filter for spam and that’s it?
i might just add a relay with and without that new parameter, and then just toggle them on and off individually to test
Yes, but no guarantees on the spam filtering. It’s only a few weeks old.
