{"id":"b0fccf566aa79173596dd4870190b1c4805d229acf35b0197f9dbc4c0c01321f","pubkey":"2b39b4ffe62933df970e19366c22c1e092f953f83fcfed754e0f04d5a3b459f9","created_at":1781353189,"kind":30817,"tags":[["d","nip-84"],["title","NIP-84: Highlights"],["summary","Kind 9802, a highlight: the passage someone found worth keeping, pointing back at the event or the URL it was taken from."],["s","draft"],["t","nostr"],["t","nip"],["k","9802","Highlights"],["alt","A specification: NIP-84: Highlights"],["client","openspecs-import"],["published_at","1699359403"],["proxy","https://github.com/nostr-protocol/nips/blob/656cecc7c0a815b6a2b218d3b5d6f078b3f4dbab/84.md","web"],["x","f89567b7e40056638ed5edee4f6b24c8dc142c038d83c061ff4e6db8c179554a"]],"content":"NIP-84\n======\n\nHighlights\n----------\n\n`draft` `optional`\n\nThis NIP defines `kind:9802`, a \"highlight\" event, to signal content a user finds valuable.\n\n## Format\nThe `.content` of these events is the highlighted portion of the text.\n\n`.content` might be empty for highlights of non-text based media (e.g. NIP-94 audio/video).\n\n### References\nEvents SHOULD tag the source of the highlight, whether nostr-native or not.\n`a` or `e` tags should be used for nostr events and `r` tags for URLs.\n\nWhen tagging a URL, clients generating these events SHOULD do a best effort of cleaning the URL from trackers\nor obvious non-useful information from the query string.\n\n### Attribution\nClients MAY include one or more `p` tags, tagging the original authors of the material being highlighted; this is particularly\nuseful when highlighting non-nostr content for which the client might be able to get a nostr pubkey somehow\n(e.g. prompting the user or reading a `<link rel=\"me\" href=\"nostr:nprofile1...\" />` tag on the document). A role MAY be included as the\nlast value of the tag.\n\n```yaml\n{\n  \"tags\": [\n    [\"p\", \"<pubkey-hex>\", \"<relay-url>\", \"author\"],\n    [\"p\", \"<pubkey-hex>\", \"<relay-url>\", \"author\"],\n    [\"p\", \"<pubkey-hex>\", \"<relay-url>\", \"editor\"]\n  ],\n  // other fields...\n}\n```\n\n### Context\nClients MAY include a `context` tag, useful when the highlight is a subset of a paragraph and displaying the\nsurrounding content might be beneficial to give context to the highlight.\n\n## Quote Highlights\nA `comment` tag may be added to create a quote highlight. This MUST be rendered like a quote repost with the highlight as the quoted note.\n\nThis is to prevent the creation and multiple notes (highlight + kind 1) for a single highlight action, which looks bad in micro-blogging clients where these notes may appear in succession.\n\np-tag mentions MUST have a `mention` attribute to distinguish it from authors and editors.\n\nr-tag urls from the comment MUST have a `mention` attribute to distinguish from the highlighted source url. The source url MUST have the `source` attribute.\n","sig":"c68cae6cc7b528ed7a59c0e11a41719cbe3dda070e40d5a4913b7494b814a6f39b0a07e4296ce169aecfb0bc40ff32d35b98f84c84b86c71359df36a395aa8f4"}