nostr-filter-relay v0.3.0 update

"Browse global. Know that mostr exists. Follow lots of people. Nostr is NOT an echo chamber, if you use it right." (Gigi)

https://image.nostr.build/cf5a8104d70e7a5c280a2bbb34ae0048d90d4cccadc125dae29047e1cb9c0c93.jpg

Thank you to our users and OpenSats for supporting this project 🤗.

This release bring new major features, modules updates, several code improvements, security fix, better documentation, and mark the completion of nostr-filter-relay features as follows:
- (New 🚀) Sentiment analysis filtering (Check USAGE.md)
- (New 🚀) Topic classification filtering (Check USAGE.md)
- Language filter
- NSFW/SFW image content filter
- User type filtering (Nostr native user/non bridged user, activitypub/mostr bridged user)
- Toxic comment filter

Feel free to check USAGE.md documentation to see more Examples on how to use nostr-filter-relay.

All filtering features can be easily disabled (opt-out) with parameters content=all :

wss://nfrelay.app/?content=all

https://raw.githubusercontent.com/atrifat/nostr-filter-relay/main/resources/flowchart-nostr-filter-relay.png

One last major issue that will become next development target:
- NIP-32 Label Event Compatibility

What's Changed?
- Topic classification filtering support
- Sentiment filtering support
- Update nostr-monitoring-tool and nostr-filter dependencies
- Documentation of nostr-filter-relay new features
- All detail update for nostr-filter, nostr-monitoring-tool, and other modules were listed in release note link below

#NostrFilterRelay Release Note v0.3.0:

https://github.com/atrifat/nostr-filter-relay/releases/tag/v0.3.0

 

 cc nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycppemhxue69uhhjctzw5hx6ef0qythwumn8ghj7un9d3shjt3s0p3ksct59e3k7mf0qyt8wumn8ghj7mn0wd68ytndd9kx7afwd3hkctctqc4jq nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7qg5waehxw309aex2mrp0yhxgctdw4eju6t0qy3hwumn8ghj7urjdau8jtt90pcx2unfd4jkuapwdah8yetwv3jhytnrdaks0duay6 nostr:nprofile1qqsverg89m7ucem0ewkpfakddqj7ms6hde27k7r292t4acp556szdjcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq32amnwvaz7tm9v3jkutnwdaehgu3wd3skueqknmcfe nostr:nprofile1qqsqxapvypwtdjxcvqcujw7y4xearpyycvkgv43lcr3p3yg29hu65hgpzemhxue69uhkummnw3ez6un9d3shjtnpwpcz7qgawaehxw309ahx7um5wgknqvfw09skk6tgdahxuefwvdhk6tcpzamhxue69uhkvun9deejumn0wd68yvfwvdhk6tc69d7cc nostr:nprofile1qqsqexc7nlhhdjytv0uxv3wuxwahwalsyk0vg8n8fdslflz48akmpcqpzamhxue69uhhxetpwf3kstnwdaejuar0v3shjtcpr9mhxue69uhkymmnw3ezumn0ddhhgctjduh8wmmjdvqs6amnwvaz7tmev9382tndv5yf5jj2 Thank you 🙏 

 Continue the great work 

 Thank you Sherry 🫡 

 can it be integrated with any nostr relay or just strfry or few specific ones? 

 Yes, it can be integrated freely with any backend relay (nostream, nostr-rs-relay, and other relays). We just need to setup relay url config in env variable. 

This repo only integrate several modules which can be replaced and customized individually. 

 love2know thanks will try it out later - seems it sits like proxy layer once config correctly.
 

 Yes, it sits like a proxy relay in front of its backend relay. Let me know your experieces self-host it 👀 

 using "global feed" was always easy just with CLIENT side SELF-filters/blocks only  - user can clean content of their choice only. 

 Yes, it depends on client whether they offer all the features to freely customized their feed settings. This relay can complement any filtering features that were probably not exist yet (language, sentiment, topic, user type, untagged non sfw content, etc) in the client. 

Hopefully, all the features that were offered in nostr-filter-relay fully implemented in the client. 

 👀
nostr:nevent1qqsfvn2tkz0jpmq4g9tyzh24rsn9wwzwj27f7wm2uyjxur5wkee0utgpr9mhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmd9upzq2m8ujqt07va9q6ksj50wfmdsmkmar3336j4eamuel24n30jfaj9qvzqqqqqqy8c6zx8