Nostr NIPS 35
NIP-35
Torrents
draft
optional
This NIP defined a new kind 2003
which is a Torrent.
kind 2003
is a simple torrent index where there is enough information to search for content and construct the magnet link. No torrent files exist on nostr.
Tags
x
: V1 BitTorrent Info Hash, as seen in the magnet linkmagnet:?xt=urn:btih:HASH
file
: A file entry inside the torrent, including the full path ie.info/example.txt
tracker
: (Optional) A tracker to use for this torrent
In order to make torrents searchable by general category, you SHOULD include a few tags like movie
, tv
, HD
, UHD
etc.
Tag prefixes
Tag prefixes are used to label the content with references, ie. ["i", "imdb:1234"]
tcat
: A comma separated text category path, ie.["i", "tcat:video,movie,4k"]
, this should also match thenewznab
category in a best effort approach.newznab
: The category ID from newznabtmdb
: The movie database id.ttvdb
: TV database id.imdb
: IMDB id.mal
: MyAnimeList id.anilist
: AniList id.
A second level prefix should be included where the database supports multiple media types.
tmdb:movie:693134
maps tothemoviedb.org/movie/693134
ttvdb:movie:290272
maps tothetvdb.com/movies/dune-part-two
mal:anime:9253
maps tomyanimelist.net/anime/9253
mal:manga:17517
maps tomyanimelist.net/manga/17517
In some cases the url mapping isnt direct, mapping the url in general is out of scope for this NIP, the section above is only a guide so that implementers have enough information to succsesfully map the url if they wish.
{
"kind": 2003,
"content": "<long-description-pre-formatted>",
"tags": [
["title", "<torrent-title>"],
["x", "<bittorrent-info-hash>"],
["file", "<file-name>", "<file-size-in-bytes>"],
["file", "<file-name>", "<file-size-in-bytes>"],
["tracker", "udp://mytacker.com:1337"],
["tracker", "http://1337-tracker.net/announce"],
["i", "tcat:video,movie,4k"],
["i", "newznab:2045"],
["i", "imdb:tt15239678"],
["i", "tmdb:movie:693134"],
["i", "ttvdb:movie:290272"],
["t", "movie"],
["t", "4k"],
]
}
Torrent Comments
A torrent comment is a kind 2004
event which is used to reply to a torrent event.
This event works exactly like a kind 1
and should follow NIP-10
for tagging.
Implementations
Source: nostr-protocol/nips/35.md version: e655247 2024-09-03T20:41:31+03:30