NIP-71
Video Events
draft optional
This specification defines video events representing a dedicated post of externally hosted content. These video events are parameterized replaceable and deletable per NIP-09.
Unlike a kind 1 event with a video attached, Video Events are meant to contain all additional metadata concerning the subject media and to be surfaced in video-specific clients rather than general micro-blogging clients. The thought is for events of this kind to be referenced in a Netflix, YouTube, or TikTok like nostr client where the video itself is at the center of the experience.
Video Events
There are two types of video events represented by different kinds: horizontal and vertical video events. This is meant to allow clients to cater to each as the viewing experience for horizontal (landscape) videos is often different than that of vertical (portrait) videos (Stories, Reels, Shorts, etc).
Format
The format uses a parameterized replaceable event kind 34235 for horizontal videos and 34236 for vertical videos.
The .content of these events is a summary or description on the video content.
The list of tags are as follows:
-
d(required) universally unique identifier (UUID). Generated by the client creating the video event. -
url(required) the url to the video file -
ma string indicating the data type of the file. The MIME types format must be used, and they should be lowercase. -
title(required) title of the video -
"published_at", for the timestamp in unix seconds (stringified) of the first time the video was published -
"aes-256-gcm"(optional) key and nonce for AES-GCM encryption with tagSize always 128bits -
xcontaining the SHA-256 hexencoded string of the file. -
size(optional) size of file in bytes -
dim(optional) size of file in pixels in the form<width>x<height> -
duration(optional) video duration in seconds -
magnet(optional) URI to magnet file -
i(optional) torrent infohash -
text-track(optional, repeated) link to WebVTT file for video, type of supplementary information (captions/subtitles/chapters/metadata), optional language code -
thumb(optional) url of thumbnail with same aspect ratio -
image(optional) url of preview image with same dimensions -
content-warning(optional) warning about content of NSFW video -
alt(optional) description for accessibility -
segment(optional, repeated) start timestamp in formatHH:MM:SS.sss, end timestamp in formatHH:MM:SS.sss, chapter/segment title, chapter thumbnail-url -
t(optional, repeated) hashtag to categorize video -
p(optional, repeated) 32-bytes hex pubkey of a participant in the video, optional recommended relay URL -
r(optional, repeated) references / links to web pages
{
"id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>,
"pubkey": <32-bytes lowercase hex-encoded public key of the event creator>,
"created_at": <Unix timestamp in seconds>,
"kind": 34235 | 34236,
"content": "<summary / description of video>",
"tags": [
["d", "<UUID>"],
["title", "<title of video>"],
["thumb", "<thumbnail image for video>"],
["published_at", "<unix timestamp>"],
["alt", <description>],
// Video Data
["url",<string with URI of file>],
["m", <MIME type>],
["x",<Hash SHA-256>],
["aes-256-gcm",<key>, <iv>],
["size", <size of file in bytes>],
["duration", <duration of video in seconds>],
["dim", <size of file in pixels>],
["magnet",<magnet URI> ],
["i",<torrent infohash>],
["text-track", "<encoded `kind 6000` event>", "<recommended relay urls>"],
["content-warning", "<reason>"],
["segment", <start>, <end>, "<title>", "<thumbnail URL>"],
// Participants
["p", "<32-bytes hex of a pubkey>", "<optional recommended relay URL>"],
["p", "<32-bytes hex of a pubkey>", "<optional recommended relay URL>"],
// Hashtags
["t", "<tag>"],
["t", "<tag>"],
// Reference links
["r", "<url>"],
["r", "<url>"]
]
}Video View
A video event view is a response to a video event to track a user's view or progress viewing the video.
Format
The format uses a parameterized replaceable event kind 34237.
The .content of these events is optional and could be a free-form note that acts like a bookmark for the user.
The list of tags are as follows:
-
a(required) reference tag to kind34235or34236video event being viewed -
d(required) same asareference tag value -
viewed(optional, repeated) timestamp of the user's start time in seconds, timestamp of the user's end time in seconds
{
"id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>,
"pubkey": <32-bytes lowercase hex-encoded public key of the event creator>,
"created_at": <Unix timestamp in seconds>,
"kind": 34237,
"content": "<note>",
"tags": [
["a", "<34235 | 34236>:<video event author pubkey>:<d-identifier of video event>", "<optional relay url>"],
["e", "<event-id", "<relay-url>"]
["d", "<34235 | 34236>:<video event author pubkey>:<d-identifier of video event>"],
["viewed", <start>, <end>],
]
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is basically the same intent as @staab 's #933
I think we should just use
kind:15here too with a[ "range", "<start>", "<end>" ]There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think a NIP-33 is a bit of an overkill here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that it would be useful to have both a kind 15 "Seen event" and an independent "View event". The main purpose of the kind 15 would be to clear notifications which makes sense in the context of checking your feed of subscriptions to see if anything new has been posted. But the kind 34237 is intended to indicate a video view, to both allow for users to continue from where they left off as well as allow clients to show a YouTube-like view count for a particular video. This may be useful for creating algorithmic feeds down the line.