Great! Tell me please, you have extracted some additional data for events (language, category, etc) — what is your vision on how existing clients could use it? Or do you only expect new clients (or features in existing clients) to handle your relay?
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. I think if this becomes standard then existing clients can query those additional data (currently kind 9978) using certain tag (currently d tag) limited to certain pubkey filter (currently with my bot pubkey). Clients can give certain filters option in their settings for users to be picked (language, category, etc). If there are other data providers then they can pick other data providers (other pubkey) so users have freedom to choose whatever algo/filter method they want.
Before that, i will check whether better use NIP-32 implementation or stay with current implementation. 😅