No: you can see the videos under any OS and any (good) media player! You don't even need VLC: the http://video.google.com/ [google.com] pages contains code like this:
You can simply copy the string (the one that starts with http...), use your favourite language to unquote it (e.g. urllib.unquote() in Python or unescape() in JS) and download the file or play it online with any media player! (mplayer under Linux is perfectly fine!)
P.S.: a greasemonkey script that do the above automagically, anyone?
You can simply copy the string (the one that starts with http...), use your favourite language to unquote it (e.g. urllib.unquote() in Python or unescape() in JS) and download the file or play it online with any media player! (mplayer under Linux is perfectly fine!)
Wow... how... amaz... ing.
Yeah!;-)
P.S.: a greasemonkey script that do the above automagically, anyone?
Keep in mind that the whole impactor crash plus spacecraft flyby will only require a small fraction of a second.
Quoting Rick Grammier, a mission project manager from the Jet Propulsion Laboratory in Pasadena: "If I ran this clip at the speed of the actual encounter, you wouldn't have seen anything. It would have been all over in the blink of an eye."
They have received a brief signal from maybe three ground stations, and the last one was Panska Ves: if this is true then the spacecraft must have reached orbit and not having done only a long suborbital jump to crash in the Pacific.
It's probably in a slightly wrong orbit: this explains the problems in locating and communicating with it.
If in the end this turn out to be a problem with the cheap Russian launcher (probably the upper stage underperformed), maybe the next time can be a good idea to buy a few kilograms aboard an Ariane 5 as an auxiliary payload (just like Smart 1, which was launched together with two big satellites): it's worth every euro of it, and will give them an higher (although highly elliptic) orbit, which is good for a big solar sail to reduce the atmospheric drag.
Anyway: keep your fingers crossed, this may still be a success!
Are you sure to have the "Distributed DB" plugin enabled and running? It requires an open UDP port and when everything is fine you should have a green light icon in the statusbar at the bottom of the window.
They chop up (almost) everything that's longer than a certain length so us poor 80-columners can read the site without having to scroll sideways.
Yeah: they insert a space in any word that is longer than 50 chars. But this is annoying for BT magnet URIs that have a fixed length of 52 chars.
A quick fix of course can be to raise the limit from 50 to 52.
If anyone is interested in understanding what are these URIs: they are a, more or less, standard compliant way to encode the info hash of a torrent. You can distinguish the bittorrent URIs because they contain the string "urn:btih:".
It's possible to convert a magnet URI to the classical hex info hash and viceversa with this small Python script: simply pass the URI or the hash to the command line.
Unfortunately currently they work only in Azureus 2.3+.
So you could burn it to a DVD-R and toss it in your DVD player to watch it on your TV if you like.
This will probably give you the wrong aspect ratio: the workprint rip has a resolution of 352x240 and even when played at 16:9 is slightly distorted. AFAIK the correct aspect ratio for that version is near 2.20:1 (calculated using some spherical or rotating elements on the movie).
Apparently BitTorrent, Azureus and Mainline all use the same protocol.
BitTorrent:
A clever protocol, based on a Kademlia distributed hash table or "DHT", allows clients to efficiently store and retrieve contact information for peers in a torrent.
Azureus:
Azureus uses an implementation of Kademlia for its distributed database.
Kademlia is a type of distributed hash table (DHT). The basic idea behind DHTs is that they are flexible enough to support new users and leaving users while storing and finding information efficiently.
Mainline/khashmir:
Khashmir is a Distributed Hash Table (DHT) based on Kademila and written in Python.
Slashdot Mirror
No: you can see the videos under any OS and any (good) media player!
You don't even need VLC: the http://video.google.com/ [google.com] pages contains code like this:
You can simply copy the string (the one that starts with http...), use your favourite language to unquote it (e.g. urllib.unquote() in Python or unescape() in JS) and download the file or play it online with any media player! (mplayer under Linux is perfectly fine!)
P.S.: a greasemonkey script that do the above automagically, anyone?
Done! You don't even need VLC: the http://video.google.com/ pages contains code like this:
You can simply copy the string (the one that starts with http...), use your favourite language to unquote it (e.g. urllib.unquote() in Python or unescape() in JS) and download the file or play it online with any media player! (mplayer under Linux is perfectly fine!)
Yeah! ;-)
P.S.: a greasemonkey script that do the above automagically, anyone?
Keep in mind that the whole impactor crash plus spacecraft flyby will only require a small fraction of a second.
Quoting Rick Grammier, a mission project manager from the Jet Propulsion Laboratory in Pasadena: "If I ran this clip at the speed of the actual encounter, you wouldn't have seen anything. It would have been all over in the blink of an eye."
To put this in contest: a good solid boost motor has an ISP of 290s and the Hall effect thruster of the Smart 1 spacecraft has an ISP of 1,600s.
A simple option for the first missions can be to do a flyby in the target solar system and transmit data back, just like the first Mars missions.
Check out the latest updates!
They have received a brief signal from maybe three ground stations, and the last one was Panska Ves: if this is true then the spacecraft must have reached orbit and not having done only a long suborbital jump to crash in the Pacific.
It's probably in a slightly wrong orbit: this explains the problems in locating and communicating with it.
If in the end this turn out to be a problem with the cheap Russian launcher (probably the upper stage underperformed), maybe the next time can be a good idea to buy a few kilograms aboard an Ariane 5 as an auxiliary payload (just like Smart 1, which was launched together with two big satellites): it's worth every euro of it, and will give them an higher (although highly elliptic) orbit, which is good for a big solar sail to reduce the atmospheric drag.
Anyway: keep your fingers crossed, this may still be a success!
The original promo video. 9.1 MB, realplayer (works fine with mplayer), funny.
Yeah, but please note that some sites (e.g. torrentspy) publish an equivalent information: the info hash.
You can convert an info hash to a magnet URI and vice versa with this small Python script: simply pass the hash or the URI to the command line.Are you sure to have the "Distributed DB" plugin enabled and running? It requires an open UDP port and when everything is fine you should have a green light icon in the statusbar at the bottom of the window.
"Open location" is fine: insert the magnet URI in the URL field removing the whitespace before the last two chars.
Well, according to the W3C you can put any URI in an <a href="...">, not only URLs.
The real problem is thatHe is not lazy: /. messes up magnet URIs in <a href="..."> really badly!
Yeah: they insert a space in any word that is longer than 50 chars. But this is annoying for BT magnet URIs that have a fixed length of 52 chars.
A quick fix of course can be to raise the limit from 50 to 52.
If anyone is interested in understanding what are these URIs: they are a, more or less, standard compliant way to encode the info hash of a torrent. You can distinguish the bittorrent URIs because they contain the string "urn:btih:".
It's possible to convert a magnet URI to the classical hex info hash and viceversa with this small Python script: simply pass the URI or the hash to the command line.
Unfortunately currently they work only in Azureus 2.3+.Yeah, except that after 30 seconds you have to change the cartridge...
Not so tough: Bram Cohen, has the Asperger's Syndrome, so if you want BitTorrent...
Apparently BitTorrent, Azureus and Mainline all use the same protocol.
BitTorrent: Azureus: Mainline/khashmir: Emphasis mine.