VP8 implementation in chrome is a bit buggy and periodically crashes a tab - I suspect it doesn't get widely used or these issues would get solved more quickly.
Lets deal with protocol fragmentation by introducing another protocol.
Industry is irrelvant, if your customers are being actively exploited you are or ought to be liable if you don't fix it as fast as possible
Its exactly that kind of stuff that got me into chemistry in the first place
I just tried to find some more info about it and found this page (http://wiki.debian.org/MultimediaCodecs) which doesn't really answer my question, but it amused me how much they're at pains to point out that you might have problems if you use unofficial codecs (3 times in a few cms of text).
At the bottom of that document is http://www.debian.org/legal/patent, which says "Debian will not knowingly distribute software encumbered by patents". But debian apparently distribute mp3 and h264 codecs and I'm completely certain that these are encumbered by patents, which is in direct contradiction to that statement.
So who knows what they're up to?
Have they finally come up with a free solution for media playback? Or have they compromised on their principles?
It irritates me that Microsoft, having consistently failed to innovate a phone that anybody wanted to use, is now able to extract money out of other people's efforts. Its an innovation tax. Don't bother innovating, as failed innovators will help themselves to the profits of your innovation.
The X application that you run remotely has no clue that it is going over an ssh connection. It looks at the DISPLAY variable as normal, then it finds that it points to a particular local port. This port has been opened by ssh which also set up the DISPLAY variable in your shell. ssh -X does the magic but it wouldn't be possible without a network transparent protocol.