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> 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. Thinking about the Magnet link regardless of it being in a Metalink or not: Does it make sense to have both xt=urn:sha1 and xt=urn:bith, although both contain the same sha1 hash? I'd like to offer magnet links when ".magnet" is appended to an URL; is there experience if it is possible to redirect to magnet URLs? I.e., the server would reply with a 302 Found and "Location: magnet:?xt=urn:sha1:..." header. Is there any other cool or useful functionality that could be included? Thanks, Peter -- 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.
