mister_monster on Nostr: I am not building a nip-35 client. I do not like the torrent specification in nip-35. ...
I am not building a nip-35 client. I do not like the torrent specification in nip-35. I don't actually need a specification for an event type for this, and IMO most applications seeking to use nostr don't either. I am building what I'm building without submitting a NIP and without any application specific protocol implementations at all. This is something that a user should be able to subscribe to content producers with any existing nostr client and view with existing client software, such as an external torrent streaming application.
I don't like the specification for several reasons, first is that there are application specific tag definitions in the spec. A general torrent spec should not have an IMDB specific tag. It seems this is built with a particular application in mind to support someone's torrent client for piracy (and I'm all for piracy but what I'm building is not a piracy specific tool) and not for generally sharing torrents.
That said, I'm probably going to give users the option to publish their torrents as kind 2003, but in MVP initially, and later by default, notes will be published kind 1.
I don't like the specification for several reasons, first is that there are application specific tag definitions in the spec. A general torrent spec should not have an IMDB specific tag. It seems this is built with a particular application in mind to support someone's torrent client for piracy (and I'm all for piracy but what I'm building is not a piracy specific tool) and not for generally sharing torrents.
That said, I'm probably going to give users the option to publish their torrents as kind 2003, but in MVP initially, and later by default, notes will be published kind 1.