Very nice, amazing!
Does it (also) act like a proxy? I see you can configure other relays (RELAYS_SOURCE) in the .env so I assume it will fetch events from those?
Hello #nostr, this is my first note, after mostly lurking as silent reader for a while 😄
Happy to introduce my first nostr project, https://github.com/atrifat/nostr-filter-relay , an aggregator filter relay which classify notes/posts into various category. This relay can be used mainly as "Global" relay in nostr clients, helping users to filter their global feed.
Currently, it has already several filtering features (also planned features listed):
- Language detection
- Not SFW or SFW image content detection
- User type filtering (Nostr non-bridged/regular user, activitypub/mostr pub bridged user)
- (Planned) Sentiment analysis
- (Planned) Topic classification
- (Planned) Hate speech detection
Feel free to check "USAGE" docs in Github for more information and examples on how to use the relay.
There is a public demo (beta/test) relay wss://nostr-id-relay.hf.space for those who can't run their own nostr-filter-relay software. Feel free to test the relay, although the performance is not always guaranteed, since this is only a test server.
Discussion
Thank you. Yes, it acts like frontend proxy before forwarding any request into the backend (strfry internal relay). However, RELAYS_SOURCE determines where to fetch/aggregate Nostr events (kind 1) before classifying them into various category and send them into target relay (strfry internal relay). UPSTREAM_WS_URL is the correct one for settings which relay to be the target of proxy. I have run several tools in this docker image, maybe it makes a bit confusing 😅
Yes I get it 🙂 already saw the other services and it makes sense to me Will look into it further later on 👍🏻
Thank you, hopefully the code will be quite easy to read, please bear with me if it is not quite clean 😅