The magnet links are metadata in a link-like format. They do not point to any resolvable service of any kind really. They just tell the program what the file is using metadata and the client should then go of and find the file based on that information.
Where should it go now? Bram On Fri, 2010-03-12 at 12:49 -0500, Anthony Bryan wrote: > On Fri, Mar 12, 2010 at 9:36 AM, Tatsuhiro Tsujikawa > <[email protected]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hi, > > > > Peter Pöml wrote: > >> Hi, > >> > >> just for fun, I was looking into generating Magnet links, because it > >> became possible to do this easily with MirrorBrain recently (read: some > >> hours ago ;-). I read up on magnet links a bit, and I think that the > >> following might hopefully make some sense: > >> > >> % curl -s > >> "http://go-oo.mirrorbrain.org/stable/linux-x86_64/3.2/ooobasis3.2-ar-impress-3.2.0-9483.x86_64.rpm?meta4"; > >> | grep magnet > >> <metaurl > >> mediatype="magnet">magnet:?xl=991261&dn=ooobasis3.2-ar-impress-3.2.0-9483.x86_64.rpm&xt=urn:sha1:45cbf5e329583f4758680cee6ef940f2a8092379&xt=urn:bith:45cbf5e329583f4758680cee6ef940f2a8092379&xt=urn:md5:aa54080575e6d92019af6c776f314a6f</metaurl> > >> > > > > & should be & ? > > yes, without that all metalinks (3 & 4) will be invalid > > >> > >> However, I have no experience with Magnet links, and I might do something > >> wrong. > >> > >> Is mediatype="magnet" sane? (It's not registered in any way, I think, but > >> I might overlook something). Ant just pointed out in #mirrorbrain on > >> Freenode that mediatype="torrent" should fit better, since they contain > >> the same information as (linked) torrents contain. This makes more sense > >> to me as well now. > >> > > > > I think mediatype="torrent" will fit only when the magnet is urn:btih. > > (Actually aria2 secretly supports this behavior) > > For more general case, other than btih, then I think mediatype="magnet" > > is a good candidate. If client is magnet capable, then it can parse > > magnet and detect its xt it supports. > > <metaurl> is actually a URI to a metadata/metainfo file (like a > torrent, metalink, zsync, or other file) > > magnet links should go in <url> I think, because the metadata is part > of the actual URI and retrieves the actual file, not a metadata file > which has a MIME media type of it's own. > > unless the magnet links actually ARE to a metadata/metainfo file, in > which case it should be <metaurl> > (from what I understand, torrent clients can use magnet links to get > the torrent file: > http://torrentfreak.com/bittorrents-future-dht-pex-and-magnet-links-explained-091120/ > ) > > -- > (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] > )) Easier, More Reliable, Self Healing Downloads > -- You received this message because you are subscribed to the Google Groups "Metalink Discussion" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/metalink-discussion?hl=en.
