bringing the first 3D HTML5 video to the web with Firefox, NVIDIA and Youtube

Starting with Firefox 4, WebM videos encoded with 3D data will be displayed in high-quality stereoscopic 3D using NVIDIA 3D Vision hardware. 3D hardware has moved from movie theaters and into people’s homes through TVs, laptop and desktop machines. 3D video games are in wide use today. And consumer hardware that’s capable of capturing 3D photos and videos is starting to come onto the market. In fact, there are several thousand 3D videos available today on Youtube. And starting today Youtube will transcode and play these videos into the open WebM format with 3D for use with their HTML5 player. This feature is currently only available with Firefox 4. It’s our hope that other browsers will follow and add support for 3D HTML5 video as well.

This is part of our larger effort to bring open video to the web. We’ve been glad to work with NVIDIA and Youtube on this project building the solution entirely on open standards like WebM and HTML5. Our hope is that by lowering the barrier for 3D video on the web, we’ll see more interesting apps being build on open web technologies.

This feature requires that you have 3D Vision hardware. If you do have 3D Vision Hardware, go to youtube.com and search for ‘yt3d‘. Files encoded with 3D have this tag. You will also have to set your 3D mode for the type of hardware you have.

Even if you don’t have the hardware, trust me. This feature is pretty cool. I was able to load up some 3D trailers on youtube and it was pretty amazing to see a little world appear in the video box.

Posted in Firefox, Mozilla, NVIDIA, Open Web, Video, Youtube | 48 Comments

gary taubes at the NYT asks: Is Sugar Toxic?

I haven’t written much on Food recently (or much at all recently) but there’s a great article in the New York Times covering sugar’s possible role in metabolic syndrome and other diseases as well.

The article itself clocks in at 9 pages, but it’s worth reading all the way through.  In particular, reading the full article leads to the last two pages, which contain some possible connections that I had not seen until this article.  Truly scary stuff.

Posted in Food | 7 Comments

our first 24 hour race

Just applied to try to be part of GOIN’ FOR BROKEN 2011, a real 24-hour race. I’m imagining what it will be like to wake up at 3am, climb into a car, and go out on a race track with other foolish people. They run this one 10am-10am. Should be an experience of a lifetime.

Here was my application.

TEAM JUDGEBUSTERS       *
Plantiff                *        IN THE
                        *       SUPREME COURT
v.                      *       FOR
                        *       24 HOURS OF
RENO-FERNLEY            *       LEMONS
RACEWAY                 *
Defendant               *
                        *       CIVIL ACTION: 555
                        *
*  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *

Team Judge Busters, Plaintiff, by Christopher Blizzard, and his attorneys,
sues the defendant, Reno-Fernley Raceway, and in support, states as follows:

PREAMBLE

1. Team Judge Busters, Plaintiff, is a resident of California.
2. Reno-Fernley Raceway, Defendant, is a resident of Nevada.
3. The defendant is currently a resident of Fernley, Nevada.
4. This action arises from a road race, scheduled to occur on May 14, 2011
through May 15, 2011.  This event will not take place on public roads.

STATEMENT OF FACTS

5. This road race is a 24 hour race, without breaks and without mercy.  The
Judge Busters team is currently scheduled to run their very first race at
Sears Pointless, yet sees yet another opportunity for risk and stupidity on
display in the desert wasteland of Nevada.  This dubious opportunity is
enough to raise the interests of these several drivers who will make the journey
to partake in the pointless exercise of chasing other, similarly
intellectually-challenged teams around a track, passing the same point over and
over again, accomplishing nothing and proving even less.

COUNT ONE

Plaintiff, Team Judge Busters realleges and incorporates by reference all those
facts and allegations in paragraphs 1 through 5 above and futher alleges:

6. This action is reckless and dangerous, and only fools are likely to participate.
  a. That Team Judge Busters is populated by said fools.
  b. That should the car hold together, the Team will complete said race.
  c. That Team Judge Busters will drive like non-asshats.

7. All of the Plantiff's losses are their own damn fault, and this racing this is a really
really bad idea.

WHEREFORE, the Plaintiff claims ONE THOUSAND FIVE HUNDRED AND ONE
DOLLARS ($1,501.00) in damages.

Respectfully Submitted,
Christopher Blizzard, Esq., DDS, MD, POS
Posted in Cars, Lemons | 7 Comments

disabling websockets for firefox 4

We’ve decided to disable support for WebSockets in Firefox 4, starting with beta 8 due to a protocol-level security issue. Beta 7 included support for the -76 version of the protocol, the same version that’s included with Chrome and Safari.

Adam Barth recently demonstrated some serious attacks against the protocol that could be used by an attacker to poison caches that sit in between the browser and the Internet.

Once we have a version of the protocol that we feel is secure and stable, we will include it in a release of Firefox, even a minor update release. The code will remain in the tree to facilitate development, but will only be activated when a developer sets a hidden preference in Firefox.

A note for web developers: When a user doesn’t have WebSockets enabled, the WebSocket property will not be on the window object. So object detection should work.

To be clear, we’re still excited about what WebSockets offers and we’re working hard with the IETF on a new WebSocket protocol.

Posted in Firefox, Standards, WebSockets | 41 Comments

websockets – shipping before it’s ready?

Anne from Opera has posted about their support for WebSockets in Opera 10.70. Unfortunately, they will be shipping -76, which is a version of the protocol that will be replaced. And it’s in the official namespace, which means that if you’re going to use WebSockets, you’re also going to have to do UA detection to know which version of the protocol the browser supports. This isn’t good.

Our current plan in Firefox is to ship -76, but with a private namespace. Why? Because we know the protocol is going to change so it’s important for developers to be able to tell which version of the protocol a browser actually supports. We’re leaving it in just for testing. WebSockets should not be considered production yet.

I can’t speak for the Chrome team because I don’t work for Google, but my understanding from talking with the people there is that they will change the protocol in Chrome once a new version of the protocol is out and push it out in one of their releases. (The current editor of the spec, Ian Fette, works on the Chrome team at Google.)

Anne, displaying some unintentional self-parody, says It will be interesting to see if we ever do get rid of -76.. Note that the best way to end up getting stuck with something is shipping it before it’s ready. Just saying.

I’ll be pretty disappointed if we end up with a world in which one browser shipped earlier than it should, it gets added to HTML5 scoring web sites and then it ends up in every other browser for product marketing reasons. And by effect we end up with something that isn’t very good because we were in a hurry.

It’s a protocol. We should spend some time getting it right.

That being said, there has been quite a bit of progress in the working group and many open issues have been settled. The draft somewhat lags behind consensus, but I would expect updates soon.

Posted in Web Standards, WebSockets | 18 Comments

my favorite TED talk

A lot of people like the talks about technology, or science, or environment-changing discoveries, or well-known leaders.

But this is my favorite, and it’s one that I think most people haven’t seen about wisdom, moral courage and leadership.

Posted in Storytelling, Video | 2 Comments

24 Hours of LeMons

Chris (By Shona B)

First, you need to understand that this is a post about racing. Racing cars. I’m a bit of a motorhead and I like things like this so if you don’t care about cars or you think they are dumb then you’re going to want to stop reading now. Go do something else, like polishing your bicycle.*

You’re still here? Good. OK, second thing you need to know is that this is probably different than any race you’ve heard of. This isn’t the 24 Hours of Le Mans, a prestigious endurance auto race held in Europe. This is The 24 Hours of Lemons in which losers, like the author, get together and build a car for less than $500 and then attempt to race it over two long days.

But like most things that are fun in life, there’s more to this race than just the cost of the car. Teams don’t just have to get an old and barely-running crapcan around the track a couple hundred times. They have to do it in style. So when you show up you’re expected to have a theme. And when I say theme, I don’t mean just a nice paint job. You’re supposed to show up in character.

BMW E30s Lined Up (by Ryan Doherty)

The Kill Phil Team (by shonab)

So in reality this is about having as much fun as you can and spending as little cash as you can.

You’d be surprised at home many people show up. There were about 120 teams that showed up for this race – Arse-Sweat-Apalooza 2010 – from all over the west coast, some as far away as Seattle.  Many were returning teams, even running with the same theme as previous races.  But many teams change their themes over time even if they don’t change the car too much.  (The judges encourage this through various means.)

Our team, made up of a few Mozilla people and running with a borrowed car was no exception.  This car had run a previous race, and we had done extensive work on the car ahead of the race.  (Anyone who knows me knows that I spent basically every weekend for the two months before the race in Oakland working on the car.)  It went to the race with new tires, new wheels, a motor that ran much better than in the previous race and a bunch of other improvements.  It also had a new theme.

The theme was good, but it wasn’t good enough to avoid some penalty laps.  Our motor looked too clean and we ended up with about 30 penalty laps – enough to cost us about 10 positions in the race.

All in all we did pretty well.  We finished in the middle of the pack, 63rd out of 121 teams.  We had one real breakdown.  About an hour before the end of racing on the first day our Master Brake Cylinder went out.  Lucky for us, we were driving a very common car and were able to get a spare from another team on the track.  We were back out on Sunday morning with fresh brakes.

Other teams were not as lucky.  Stories of replaced and blown engines abounded, including replacements on-track.  But this is what it means when you show up with a car that cost a maximum of $500.

And on that note, it is a race.  And you’re expected to go.  I was lucky enough to score the fastest lap time on our team, even though our little car didn’t hold a candle to some of the machines out on the track.

It was a great time. Not only because it’s nice to go around a track really fast. But also because we put so much work into the car and we got to see it pay off. You get to drive the car you spent time on. It’s a pretty amazing experience.

So it’s unlikely that this will be the last race. Some friends and I are trolling around, looking for another E30 to convert to race specs. And I’m sure I’ll be posting about it again.

And here are some picture galleries for your enjoyment.

* Actually, I like bicycles a lot. And the people who ride them. But this isn’t about that.

Posted in Cars, Lemons | 4 Comments

new role at mozilla – director of web platform

For the last couple of years I’ve been responsible for our wonderful Evangelism group at Mozilla. We’ve been responsible for a combination of developer relations, standards work and outbound developer-focused communications. If you’ve followed our work on hacks and devmo, especially around the release of 3.5 and 3.6 then you’ve familiar with the pretty amazing work of this team.

But over the last few months I’ve been focused on one aspect of that job more than others – helping to drive the web-facing side of our platform. A big part of that work has been listening to web developers who are building on top of the web and understanding what they need. (This is a big part of the role of the Evangelism group inside of Mozilla.) I’ve also been working closely with Mozilla’s engineering team to help determine what’s important and what’s not. I think that I’ve discovered – and others inside of the project have discovered as well – that having someone doing that full time with a specific focus on the web platform full time is really important. (In the past that role was spread across various parts of the project.)

To that end I’m moving on from leading the Evangelism team and moving to help manage the web-facing side of Firefox full time. It’s easiest to think of this as a product manager for the web.

This is going to be an interesting job, to be sure. It’s entirely built of soft skills: listening closely to web developers, both frontend and backend. Working with the Mozilla community to communicate and understand where the web needs to go next. Working with partners to build great partnerships and products. Working with our user and developer engagement groups on the best way to talk about the web. Maintaining a roadmap for Gecko. And, last but certainly not least, working every day with the people on the ground doing the great work that make Gecko the best platform to advance the web.

I expect that I’ll keep posting on hacks and on this weblog. But expect to see different kinds of questions from me from now on. I expect that I’ll be spending a good bit of my time on what the web will look like 2-5 years from now and what we can do at Mozilla to make that happen. That’s going to require looking for the best ideas that people have and working to make them a reality through the Mozilla project.

The web is a platform that’s still ripe for improvement and change. So I’m looking forward to your feedback and your help.

Posted in Mozilla | 17 Comments

creating cultural change

Posted in Communities, Video | 2 Comments

bucket head

Posted in Samantha | 3 Comments