From e1a3228486ae139d275cd06fe9ad787232addad6 Mon Sep 17 00:00:00 2001 From: zeSchlausKwab Date: Fri, 18 Jul 2025 14:18:15 +0200 Subject: [PATCH] Remove 'client' tag from stream object requirements in XX.md for clarity and privacy considerations. --- XX.md | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/XX.md b/XX.md index e249b63e..e80f78f4 100644 --- a/XX.md +++ b/XX.md @@ -48,8 +48,7 @@ Radio stations are published as addressable events of `kind:31237`. These events ["countryCode", ""], ["location", ""], ["thumbnail", ""], - ["website", ""], - ["client", "", "", ""] + ["website", ""] ] } ``` @@ -108,7 +107,6 @@ Each stream object MUST include: - `location`: Human-readable location string - `thumbnail`: Station logo/image URL - `website`: Station's official website -- `client`: Client that published the event (format: `["client", "ClientName", "HandlerId", "RelayURL"]`) ### Example @@ -128,13 +126,7 @@ Each stream object MUST include: ["countryCode", "FR"], ["location", "Paris, France"], ["thumbnail", "https://example.com/fip-logo.png"], - ["website", "https://www.radiofrance.fr/fip"], - [ - "client", - "NostrRadio", - "31990:pubkey:handler123", - "wss://relay.example.com" - ] + ["website", "https://www.radiofrance.fr/fip"] ] } ``` @@ -173,7 +165,6 @@ Persistent discussion threads use existing comment protocols such as [NIP-25](25 ### Privacy Considerations -- The `client` tag has privacy implications - clients SHOULD allow opt-out - Station owners can moderate chat/comments by maintaining block lists - Consider rate limiting for chat messages to prevent spam