From 5196ac196a9e19cfbb9c6cd16d8081dd137e3572 Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Thu, 1 Feb 2024 20:59:37 -0300 Subject: move `imeta` to NIP-92, add `imeta` tag to README. --- 29.md | 43 ------------------------------------------- 1 file changed, 43 deletions(-) delete mode 100644 29.md (limited to '29.md') diff --git a/29.md b/29.md deleted file mode 100644 index 2a22233..0000000 --- a/29.md +++ /dev/null @@ -1,43 +0,0 @@ -NIP-29 -====== - -Media Attachments ------------------ - -Media attachments (images, videos, and other files) may be added to events by including a URL in the event content, along with a matching `imeta` tag. - -`imeta` ("inline metadata") tags add information about media URLs in the event's content. Each `imeta` tag SHOULD match a URL in the event content. Clients may replace imeta URLs with rich previews. - -The `imeta` tag is variadic, and each entry is a space-delimited key/value pair. -Each `imeta` tag MUST have a `url`, and at least one other field. `imeta` may include -any field specified by [NIP 94](./94.md). There SHOULD be only one `imeta` tag per url. - -## Example - -```json -{ - "content": "More image metadata tests don’t mind me https://nostr.build/i/my-image.jpg", - "kind": 1, - "tags": [ - [ - "imeta", - "url https://nostr.build/i/my-image.jpg", - "m image/jpeg", - "blurhash eVF$^OI:${M{o#*0-nNFxakD-?xVM}WEWB%iNKxvR-oetmo#R-aen$", - "dim 3024x4032", - "alt A scenic photo overlooking the coast of Costa Rica", - "x ", - "fallback https://nostrcheck.me/alt1.jpg" - "fallback https://void.cat/alt1.jpg" - ] - ] -} -``` - -## Recommended client behavior - -When uploading files during a new post, clients MAY include this metadata -after the file is uploaded and included in the post. - -When pasting urls during post composition, the client MAY download the file -and add this metadata before the post is sent. -- cgit v1.2.3