my nostr has been quiet for literally like more than a month, i wasn’t seeing npubs / profiles properly resolve, i couldn’t follow threads the whole way back, probably wasn’t receiving dm’s properly etc.
and only now have i realised that nostr.wine had moved to a subscription based model 🤦🏻♂️
solution: relays should be able to communicate some sort of a small custom message / status to clients that are connected
i.e “status: working, daysLeft: 365, broadcast: true, etc, etc”
Hey! Just to be clear, nostr.wine is still a one time fee. Filter.nostr.wine is moving to a monthly paid subscription but all existing users have access till May 2nd.
I saw you already extended so let me know if there was any confusion or you want a refund!
As for reminders: there is nothing in clients yet but #[3] will DM reminders with 14, 7, 3, and 1 day(s) remaining on your account.
So will I’ll get a dm with invoice to pay? Any idea the cost yet? Happy to support this, just missed seeing it was happening.
It will link you to our site. We could do DM invoices but I’m worried about phishing. The readme was updated to include payment terms and a description of the discounts is here: https://nostr.wine/add-time
brilliant! very good idea
hey #[2] 👋🏼 no need for a refund, i love the filter service!!
i think it’s the thing that makes my nostr feed work tbh
after public relays were a bit too much, i switched to only private relays, but without the wine filter service it’s a bit like a ghost town - npubs wouldn’t resolve to legible names until i click on them, same with profile pictures, click on a thread and couldn’t see replies, etc etc
the wine filter seems to fix it all 👍🏼
i’d be interested to see if i could run such a filter service on my own node that i’m setting up though 🤔
Ahhh yes, I understand now. I usually only use .wine relays so I am also heavily reliant on filter to show me missing content. I’m glad you’ve enjoyed it.
We do hope to open source at least parts of it eventually so users can run their own. It’s a bit clunky and in several pieces still atm.
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.
