Added detailed breakdown of what the client should do

Added detailed breakdown of what the client MUST do in case of unsupported MIME type
This commit is contained in:
Po 2024-09-01 23:21:45 +03:00 committed by GitHub
parent d65c2e2ac3
commit 9535632ff0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

3
22.md
View File

@ -42,7 +42,8 @@ The list of tags are as follows:
``` ```
> [!IMPORTANT] > [!IMPORTANT]
> Client `MUST` validate its support for **MIME type** and, in case it is unsupported, turn that into a `nostr:naddr1...` link to some client capable of displaying such events according to [NIP-19](../master/19.md). > Client `MUST` validate its support for **MIME type** and, in case it is unsupported, turn that into a `nostr:naddr1...` link (according to [NIP-19](../master/19.md)) to a client capable of displaying such events or a client referenced in the `client` tag.
A stringified JSON of the kind 30031 smart widget would look like this: A stringified JSON of the kind 30031 smart widget would look like this:
``` ```