Note
"Compatibility bring various apps grow together"
This release bring important change with NIP-32 compatibility (kind: 1985). Starting from this release, legacy custom event (kind: 9978) that were used for classification data in nostr-filter-relay has been deprecated.
Legacy support is still available by setting nostr-filter-relay with environment variable as follows:
# (Optional. Default: true) Set whether to publish NIP-32 classification event (kind: 1985)
ENABLE_NIP_32_CLASSIFICATION_EVENT=false
# (Optional. Default: true) (Deprecated) Set whether to publish legacy classification event (kind: 9978)
ENABLE_LEGACY_CLASSIFICATION_EVENT=true
# nostr-filter env variable
USE_NIP_32_EVENT_FORMAT=falseExplanation of NIP-32 structure were documented in NIP32-COMPATIBILITY.md
Check USAGE.md documentation to see more examples on how to use nostr-filter-relay as Nostr users.
All the filtering features can be easily disabled (opt-out) with parameters content=all as shown by this example:
wss://nfrelay.app/?content=all
What's Changed
- feat: NIP-32 compatibility and dependencies update by @atrifat in #23
- docs: NIP-32 compatibility event structure by @atrifat in #21
- docs: NIP-32 usage explanation in nostr-filter-relay by @atrifat in #22
- feat: Max websocket message size setting in nostr-filter atrifat/nostr-filter#32
- feat: Rate-limit support in nostr-filter atrifat/nostr-filter#34
- feat: Relay concurrency limit setting in nostr-filter atrifat/nostr-filter#41
- Detail update for nostr-filter in atrifat/nostr-filter#32 atrifat/nostr-filter#34 atrifat/nostr-filter#36 atrifat/nostr-filter#37 atrifat/nostr-filter#38 atrifat/nostr-filter#39 atrifat/nostr-filter#40 atrifat/nostr-filter#41 or nostr-filter full changelog
- Detail update for nostr-monitoring-tool in v0.7.0
Related Dependencies Update
- feat: Replicate Cog Support for sentiment-analysis-api in atrifat/sentiment-analysis-api#8
- feat: Replicate Cog Support for topic-classification-api in atrifat/topic-classification-api#7