66,000 ustream viewers and climbing...
This has got to be one of the most publicised things NASA has done for years.
Biting nails right now.
El Reg is live from NASA's Jet Propulsion Laboratory in Pasadena, waiting to see if the Mars Science Laboratory, or Curiosity as it's better known, will land safely or crater the surface of Mars. 8:45pm In an effort to keep people occupied NASA has been bussing in celebrities to keep the assembled press talking. Geek icon Will …
Unlike myself during the much earlier live Q&A session on Ustream. I just had to ask:
"Given the power source, does this mean you'll be nuking the site from orbit? Just to be sure?"
@NASAJPL's response: "No, we won't be dusting off."
Thumbs up for rocket scientists with a sense of humour.
Note to the author...
When posting stuff on the intarweb with an international audience, it would be nice if times where given a timezone, not just left floating. Preferably a timezone that the whole planet can relate to such at GMT or UTC...
Not giving a time zone, or using one which is obscure or meaningful only to one nation is a tad insular.
Even worse when I'm reading this on a .co.uk website, and the times were obviously not from a time zone you would assume for a .uk domain.
Well done ustream for constant stuttering and buffering and for finally dropping out entirely at 10:25pm and returning nothing but 503 errors until 10:32pm, thereby missing the entire period of interest. What a complete waste of time that was; internet live TV events remain as shite as they have been since they first began in the '90s.
Anyone who thinks that the internet is anywhere near ready to replace broadcast media is a gullible asshole who has swallowed a bunch of marketing bullshit.
Sure, they could be responsible for a few dropped packets causing the glitches and buffering while the stream *was* working, but there's nothing they could have done that would have been the cause of NASA's CDN server (mars.jpl.nasa.gov, aka d2cj35nmzi9erd.cloudfront.net = 220.127.116.11 from where I'm sitting) constantly returning HTTP 503 errors for seven solid minutes (not coincidentally at the exact time when it would have been under most load). That could only have been the server itself. (No, my ISP doesn't have a transparent proxy in line.)