using "global feed" was always easy just with CLIENT side SELF-filters/blocks only - user can clean content of their choice only.
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)
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
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
Discussion
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.