Slashdot Mirror


YouTube Revamp Imminent?

An anonymous reader writes "YouTube's latest blog post indicated that some changes are on the way. Google has opened up a call to submit and vote on ideas. HTML 5 open video with Free formats has dominated the vote, maintaining over twice as many votes as the next-highest item almost since the vote opened up. You may vote here (Google login required). Perhaps we don't even need to since their blog post comes suspiciously soon after their revised merger with On2. Could these improvements be a completely overhauled YouTube 2.0?"

297 comments

  1. HTML5 for the win? Sorry, that's not a codec. by LostCluster · · Score: 5, Interesting

    There seems to be a rather loud outcry for HTML5 in the idea list. Many of the top ten ideas use that phrase and nothing else of substance.

    There's only one problem. It ain't finished yet. So we've got the same problems 801.11n had a few years ago. It's hard to implement a moving spec.

    This is like the open source proponents who mentioned Ogg Vorbis a few years ago as a solution to DRM, and it's clear now that DRM-free watermarked MP3 is the winner in the marketplace today. Even worse, it's the same people behind it... Ogg's video spec 's used to be called out by name for being used in HTML5 and that's still under debate. Open Source fans including Mozilla support it, while owners of other video codecs of course think they shouldn't be locked out.

    So... really, HTML5 doesn't solve Google's problems with YouTube. Using HTML5 without calling for a codec is like an incomplete function call. You need to say which codec you want YouTube to use, or we could just see HTML5 + Flash on YouTube while other sites use other codecs....and not make much of a change.

    Standards are good... but we're still in a format war over HMTL5 that makes it nearly impossible to implement it right now.

    1. Re:HTML5 for the win? Sorry, that's not a codec. by mysidia · · Score: 5, Insightful

      Open Source fans including Mozilla support it, while owners of other video codecs of course think they shouldn't be locked out.

      Isn't it ironic that owners of other video codecs who are renowned for locking the public out of their formats, by keeping them secret, or trying to charge fees for their use, now don't "want" to be locked out?

      If they want their codec to be one included by an open standard such as HTML5, then the absolute requirement should be that they open their codec's specifications and make implementation of the codec gratis of any royalties, and just as free and open as the HTML recommendation.

      I don't want to exclude any codec who will do that.

      But the standards bodies owe it to the internet to exclude any codec who refuses to do that, and to recognize the popular codecs who will do that, by choosing the most suitable ones for inclusion as a critical element for video-enabled HTML5 renderers.

    2. Re:HTML5 for the win? Sorry, that's not a codec. by FlyingBishop · · Score: 1

      It's not really rocket science. It should work basically like an image. There is the autoplay issue, but Google is more than capable of handling the (minor) headache of serving different content to different browsers.

      The only conceivable issue is that Ogg Theora content will likely be degraded, since it will doubtless be transcoded from H.264.

    3. Re:HTML5 for the win? Sorry, that's not a codec. by Darkness404 · · Score: 3, Interesting

      This is like the open source proponents who mentioned Ogg Vorbis a few years ago as a solution to DRM, and it's clear now that DRM-free watermarked MP3 is the winner in the marketplace today.

      A lot of the reason why people wanted OGG so badly is because OGG easily worked on Linux. In the days before Ubuntu, Fluendo and easy codec installation, finding, installing and using an MP3 codec was generally difficult and legally questionable. Now that it is really easy to install an MP3 codec in most Linux distros, people have toned down on the OGG evangelism for music.

      Ideally, HTML5 standards would use an open, patent-free standard for use with video. The point of standards is to allow different systems to communicate effectively, the fact that it is open is a requirement of any standard meant for benefiting users. Right now, Theora is about the only major codec that seems to fit the bill.

      --
      Taxation is legalized theft, no more, no less.
    4. Re:HTML5 for the win? Sorry, that's not a codec. by Vyse+of+Arcadia · · Score: 4, Insightful

      Standards are good... but we're still in a format war over HMTL5 that makes it nearly impossible to implement it right now.

      I think that, given Youtube's weight, any codec Google chose would probably win the format war.

    5. Re:HTML5 for the win? Sorry, that's not a codec. by maxume · · Score: 1

      For all your rambling, the codec listed in the HTML5 draft matters a great deal less than the codecs present in the major browsers, and for the time being that means that they will continue to serve flash for IE, but they can also serve whatever formats are supported in Firefox, Safari and Chrome (if serving something other than flash actually makes sense).

      --
      Nerd rage is the funniest rage.
    6. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 5, Insightful

      This is like the open source proponents who mentioned Ogg Vorbis a few years ago as a solution to DRM, and it's clear now that DRM-free watermarked MP3 is the winner in the marketplace today.

      Missing the point. Vorbis is not, and never was, about DRM. It's about having a patent-free codec. It's about having a format that works out of the box on something like Ubuntu, legally, anywhere in the world.

      Contrast with MP3 -- it's actually very likely not legal to include mp3 support in open source software at all, at least if you're going to keep it free (as in beer).

      The only technical reason to prefer MP3 to Vorbis is device support. The way to improve device support is to raise awareness about these issues and get people to actually use Vorbis.

      Even worse, it's the same people behind it...

      Who?

      that's still under debate.

      Actually, the debate is pretty much over. HTML5's <video> tag specifies codec and format precisely as much as HTML4's <img> tag specifies image format -- that is, not at all.

      HTML5 doesn't solve Google's problems with YouTube.

      Which problems would those be?

      Using HTML5 without calling for a codec is like an incomplete function call.

      Wow, even worse than BadAnalogyGuy. Really?

      You need to say which codec you want YouTube to use,

      No, I really don't.

      I mean, yes, it might help to do so -- but that's unlikely to get anywhere. There currently isn't a free video codec that matches the proprietary ones, technologically, and even if there was, it seems incredibly unlikely that YouTube would go to the trouble of transcoding all of their video -- again.

      If YouTube were to implement HTML5 support with, say, h.264 in an mp4 container, they'd have to do no transcoding, probably not even re-encapsulating. It would Just Work on Chrome and Safari, and there's no technological reason it couldn't work on Firefox -- only political assholes who refuse to implement such support, even in countries which don't respect software patents. If IE ever decides to support HTML5 at all, I very much doubt that Microsoft doesn't have h.264 licenses. Only Opera really has an excuse here.

      Now, technically, if they went with Theora, it could be supported everywhere -- every browser which supports HTML5 supports Theora out of the box, except Safari, and it's trivial to install a QuickTime plugin. But the question then becomes whether it's worth it for Google to do HTML5 at all, if they have to transcode everything to get the best browser coverage.

      we could just see HTML5 + Flash on YouTube while other sites use other codecs....and not make much of a change.

      Surely you're joking.

      There may be legal hurdles, but any browser that wants to could simply hook into a third-party codec library. On Windows, that's DirectShow. On OS X, it's QuickTime. On Linux, it's GStreamer, Xine, or ffmpeg. All of these support every codec that's even being considered for HTML5, and many more.

      It would basically make it as easy to embed videos as it currently is to embed images. After all, <img> doesn't specify a format -- why aren't you waging a "codec war" about image formats?

      It would also get us the ability to use purely open source software for our web browsing again, or at least for our YouTube -- no need for Flash. It'd also give us the ability to right-click and do something like "save video as", or click+drag a video to our desktop, or email. It'd also greatly simplify anything else which just wants the video -- for example, any sort of set-top box, etc, now only needs a web browser, or even just something that can scrape the YouTube HTML, instead of a web browser and a Flash port.

      Do you honestly believe that HTML5, even without specifying a codec, would change nothing? Do I have to explicitly

      --
      Don't thank God, thank a doctor!
    7. Re:HTML5 for the win? Sorry, that's not a codec. by 0100010001010011 · · Score: 1

      Hardware decoding will dictate where HTML5 goes.

      Broadcom has their Mini PCI-e decoder cards for all 3 OS's. NVIDIA has VDPAU on Linux and something on Windows, ATI has their thing. Flash has preliminary suport in 10.1.

      As far as I know, none of them do hardware decoding of OGG, but do do H.264.

    8. Re:HTML5 for the win? Sorry, that's not a codec. by LostCluster · · Score: 2, Interesting

      Here's Ogg's problem: They want to control their own spec. Get mentioned in HTML5 and they're frozen at whatever version number the spec uses for anything that uses HTML5. If they're not done yet, they're not ready for the W3C's adoption. Do they want the usage or control of their jobs?

    9. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 1, Interesting

      You need to say which codec you want YouTube to use, or we could just see HTML5 + Flash on YouTube

      There is synonymity between HTML5 and dropping Flash based on YouTube's HTML5 Demo which leverages the <video> tag for H.264 content. HTML5 sounds good (or win, I guess) to me.

    10. Re:HTML5 for the win? Sorry, that's not a codec. by Darkness404 · · Score: 0, Troll

      and there's no technological reason it couldn't work on Firefox -- only political assholes who refuse to implement such support, even in countries which don't respect software patents.

      Ok, so how is it going to help Firefox and an open web by implementing that support? First off, how does it decide which version to download? Is the main version going to be the "crippled" version without support or with support of proprietary add ons? What happens if someone downloads Firefox and gets sued because of the patented codecs? I don't think Mozilla wants headlines saying "Patent Troll sues user of Firefox" because already there are some people who think anything other than IE isn't a browser and must be a virus!!111!1!1 And a lot of these people are rather high up in business management and prevent tech guys who know what they are doing from giving their users a decent, secure browser.

      And lets go beyond desktop browsers for a second, how many of us have other devices that have a web browser? Game consoles, music players, cell phones, and even set-top boxes have browsers. If we set a good, patent free standard, their web browsers can have it built in without having to pay for a costly license thus increasing the use of the standard. Think about images, there are a lot of images that would be great as an SVG, but due to some browsers not supporting it (like IE) it has little use. If the video codec specified that videos should be a in a free format, IE would almost have to use a free format if it supported HTML5, or miss out on video sites coded to the standard.

      --
      Taxation is legalized theft, no more, no less.
    11. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      Your argument might make sense if Google cared about web standards. If you run their websites through the W3C validator, you'll see that there's tons of errors.

      The truth is that Google has always been supporting the most recent browsers instead of being standards-compliant. The latest browsers support HTML5, so it would make sense for Google to do the same.

    12. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      Any future updates to encoders should be backwards compatible with the current decoders.

    13. Re:HTML5 for the win? Sorry, that's not a codec. by tomhudson · · Score: 1, Troll

      Standards are good... but we're still in a format war over HMTL5 that makes it nearly impossible to implement it right now.

      I think that, given Youtube's weight, any codec Google chose would probably win the format war.

      "I think that, given Yutube's volume of crap, any codec Google chose would probably be on a blocklist."

      There, fixed it for you.

      (link NSFW)

    14. Re:HTML5 for the win? Sorry, that's not a codec. by LostCluster · · Score: 1

      Yep, so that's a better question to debate than HTML5 over HTML4... what's the best codec available now that they can use?

    15. Re:HTML5 for the win? Sorry, that's not a codec. by LBt1st · · Score: 1

      Not to mention Android and iPhone can also decode H.264. It would be sweet if it was selected as the standard for those and I'm sure other mobile devices as well. No more having clunky apps just to view YouTube and such. Embedded videos would just work, even on your phone.

    16. Re:HTML5 for the win? Sorry, that's not a codec. by Moryath · · Score: 1

      How about: any future updates should forever and for all time get rid of those fucking stupid pop-over ads they stick into the videos.

      Advertise if you want. Do NOT obscure the content while doing so.

    17. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      In the days before Ubuntu, Fluendo and easy codec installation, finding, installing and using an MP3 codec was generally difficult and legally questionable.

      Err, Ubuntu is the only Linux distribution it has ever been difficult to play MP3 files in. Any other Linux distribution I can think of, including the one Ubuntu is based on, has always had MP3 support out of the box.

      So, no, using an MP3 codec has never been generally difficult, unless you happened to be using Ubuntu and it is only legally questionable only for those living in patent-encumbered countries.

    18. Re:HTML5 for the win? Sorry, that's not a codec. by mysidia · · Score: 3, Interesting

      Is Ogg not done?

      A format that is in constant flux, is not stable, and not ready yet.

      Only a mature version of the spec should be used, one that the software industry already has positive implementation experience with.

      Of course HTML5 should mention a specific minimum base version of the Ogg spec.

      Renderers may support future versions of Ogg that validated by the W3C, but the renderer implementation must be backwards-compatible (able to read Ogg files made using an encoder that followed the old version).

      And changes must be forwards compatible, so that a file encoded in the new format can still be properly played by a browser implementing the minimal version of Ogg, at a similar quality level.

    19. Re:HTML5 for the win? Sorry, that's not a codec. by LostCluster · · Score: 3, Interesting

      Now, technically, if they went with Theora, it could be supported everywhere -- every browser which supports HTML5 supports Theora out of the box, except Safari, and it's trivial to install a QuickTime plugin. But the question then becomes whether it's worth it for Google to do HTML5 at all, if they have to transcode everything to get the best browser coverage.

      There we are. You need to tell YouTube to use Theora. As somebody else posted, if YouTube picks a codec, that codec will have enough support to win the format war that's currently raging. If you want to endorse HTML5 go ahead, but please tell them about Theora because that's much more important to them.

    20. Re:HTML5 for the win? Sorry, that's not a codec. by Brian+Gordon · · Score: 2, Informative

      What happens if someone downloads Firefox and gets sued because of the patented codecs? I don't think Mozilla wants headlines saying...

      It's things like this that make me wonder if it's a good idea to front a free project with a real-world rights-owning corporation that's responsible and can be sued. Mozilla's petty squabbling over their control of the Firefox name and logo is already ridiculous enough. Let's not start making less-than-ideal decisions for our software because we're worried about how it will affect The Project.

      Remember this gem? It was judged that getting on the bad side of financial institutions by offering an option for non honoring the annoying "autocomplete=off" attribute that breaks the password manager half the time (even when your wallet is encrypted) is bad for the project.

      If Firefox (or any
      Gecko/Mozilla-based product), is to succeed, it needs the support of major sites
      that end-users are going to use. If banks, etc, blacklist gecko, then those
      users are forced, likely, back to IE (or an older version of Firefox, etc) which
      isn't a situation we want to create at all.

      I don't care if firefox succeeds, while I do care about whether a basic option is present in my most-used piece of software.

    21. Re:HTML5 for the win? Sorry, that's not a codec. by LordLimecat · · Score: 4, Informative

      There's only one problem. It ain't finished yet. So we've got the same problems 801.11n had a few years ago. It's hard to implement a moving spec.

      Apparently not. For those too lazy to follow link, its an addon for Chrome (dev version) that makes youtube videos run in HTML5. It cuts cpu usage in half too.

      Seems to me the best way to proceed is for someone to just do it, and let everyone else try to catch up. Its not like people will stop using youtube.

    22. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 3, Interesting

      Ok, so how is it going to help Firefox and an open web by implementing that support?

      The same way it helps Firefox to implement GIF. Yes, PNG is better, but showing an image, even with questionable legality, is better than showing a "broken picture" icon -- and on the creator side, the more codecs which are supported, the more of a chance people have of just being able to dump their videos on a fileserver and expect people to be able to stream them.

      First off, how does it decide which version to download?

      Use the native libraries.

      What happens if someone downloads Firefox and gets sued because of the patented codecs?

      That's not going to happen -- worst case, Mozilla gets sued. I don't think you can sue a consumer for doing that.

      And again, use the native libraries. On Windows and OS X, you'll have those proprietary codecs out of the box. On Linux, users will either install them (Medibuntu) or they won't.

      If we set a good, patent free standard, their web browsers can have it built in without having to pay for a costly license thus increasing the use of the standard.

      Two problems:

      First, you aren't going to set a good, patent free standard. A good patent-free codec doesn't exist (sorry, but theora is technically inferior). And Apple has actually said they won't support it, Microsoft doesn't, and there isn't any hardware support.

      What's going to happen is, if you refuse to play ball, you will lose, and Firefox will lose market share because of it.

      Second, even if you somehow did, it'd still be nice to be able to use old images in their native format. If I've got a Gif for whatever reason, why should I have to convert it to PNG? At least that's lossless -- what if I have a jpeg, should I be forced to convert that to PNG? And what happens when the next shiny new codec comes along?

      Think about images, there are a lot of images that would be great as an SVG, but due to some browsers not supporting it (like IE) it has little use.

      So?

      Really, who cares? Google Wave doesn't support IE. If IE users really need modern technologies, they can install Chrome Frame.

      If the video codec specified that videos should be a in a free format, IE would almost have to use a free format if it supported HTML5, or miss out on video sites coded to the standard.

      Yes, but you are thinking about this backwards.

      Think of it from Google's perspective. You're apparently hoping that Google will spend thousands of dollars (millions?) on extra hardware to re-encode their videos (again!), as well as extra storage to get the same quality in Vorbis, and then drop their Flash support, thus forcing everyone to upgrade.

      Do you really think they'd take that gamble?

      I mean, if it works, every YouTube user is forced to upgrade to a modern browser. But that's not going to happen everywhere (corporate environments), and everywhere else, you're gambling that the users will want YouTube badly enough to switch browsers, versus just switching to blip.tv, vimeo, dailymotion, revver, etc. Even if it works, it's still likely a significant hit in marketshare from users who either can't or won't make the switch.

      The only way I can see them doing that is if something even crazier happens -- Microsoft supports HTML5 out of the goodness of their heart. But having good support for web standards in IE is actually counter to Microsoft's interests -- the stronger the Web is as a platform, the weaker Windows is.

      Think of it in terms of actual corporations and dollars. It doesn't work.

      Now, suppose the situation were different. If you can actually come up with a patent-free format which is technically better than the proprietary ones, I can definitely see Google taking that gamble, because that actually saves them money in the long term. And

      --
      Don't thank God, thank a doctor!
    23. Re:HTML5 for the win? Sorry, that's not a codec. by afidel · · Score: 1

      And they can continue to stream H.264 to other clients without Flash like Blackberry, iPhone, and even FF on Linux (if you know how to access/rewrite the URL's). Not 100% of content is available this way currently, but that could be fixed and would make the HTML5 simple icing on the cake.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    24. Re:HTML5 for the win? Sorry, that's not a codec. by aztracker1 · · Score: 1

      Actually there was a bit of a format war about .gif, which is why we have .png available. Though, to be honest having support for ogm and mp4+avc (h.264) would probably mean decent coverage overall, which seems to be the two formats with the biggest support. Though MS could pretty easily slip VC1 in there. IIRC MS provides their codec implimentations of VC1 and mp4/h.264 for free (as in beer for windows, osx and linux).

      --
      Michael J. Ryan - tracker1.info
    25. Re:HTML5 for the win? Sorry, that's not a codec. by tepples · · Score: 3, Insightful

      There currently isn't a free video codec that matches the proprietary ones, technologically

      Sure, Theora is no H.264, but it handily beats the H.263 that YouTube currently uses for downlevel Flash Players and comes close to MPEG-4 ASP (e.g. DivX, Xvid).

      there's no technological reason it couldn't work on Firefox -- only political assholes who refuse to implement such support

      You appear to have just called the members of MPEG-LA "political assholes".

      even in countries which don't respect software patents.

      How much would it cost to move Mozilla Corporation and Mozilla Foundation out of the United States?

    26. Re:HTML5 for the win? Sorry, that's not a codec. by tepples · · Score: 1

      The same way it helps Firefox to implement GIF.

      For one thing, it was believed that unlike the H.264 patent, the LZW patent covered only encoding, not decoding. For another, the LZW patent expired in June 20, 2003, whereas Mozilla Firefox became 1.0 on November 9, 2004.

      Use the native libraries.

      There is no guarantee of a native library for H.264 unless the end user has QuickTime installed. The last time I checked, QuickTime did not work in Wine.

      worst case, Mozilla gets sued.

      Mozilla Corporation, headquartered in the United States, refrains from violating United States patents in order not to get sued.

      If IE users really need modern technologies, they can install Chrome Frame.

      Can a Limited User install Chrome Frame, or does it require running the installer as a member of the Administrators group?

      If you can actually come up with a patent-free format which is technically better than the proprietary ones

      YouTube uses an H.263 codec for low-power CPUs and down-level Flash players. Theora is significantly better than that.

    27. Re:HTML5 for the win? Sorry, that's not a codec. by shadowbearer · · Score: 1

      It's hard to implement a moving spec.

        Is there any such thing as a "non moving" specification?

        Especially in the constantly evolving tech world?

        Specs *should* continue to evolve as the technology and theory changes and improves. Especially the open ones. If they don't, they will die of obsolescence.

        That's where open specs are better than closed ones. Everyone can see what is changing, and everyone can contribute. (Cue comments about "closed minded devs don't like my idea XX here; if you don't like what they are doing, fork it. )

      SB

      --
      It's old. The more humans I meet, the more I like my cats. At least they are honest.
    28. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      I think that, given Youtube's weight, any codec Google chose would probably win the format war.

      how about WMV through Silverlight

    29. Re:HTML5 for the win? Sorry, that's not a codec. by jonwil · · Score: 4, Interesting

      With Google's purchase of ON2, maybe the answer is for Google to release for free On2 VP6 or On2 VP7 or something and then make that the primary non-flash codec for Google.
      Google can then make VP6 or VP7 or whatever (whichever one is file-size and quality competitive with h.264) the main codec for YouTube.

    30. Re:HTML5 for the win? Sorry, that's not a codec. by CSMatt · · Score: 1

      If YouTube were to implement HTML5 support with, say, h.264 in an mp4 container, they'd have to do no transcoding, probably not even re-encapsulating. It would Just Work on Chrome and Safari, and there's no technological reason it couldn't work on Firefox -- only political assholes who refuse to implement such support, even in countries which don't respect software patents. If IE ever decides to support HTML5 at all, I very much doubt that Microsoft doesn't have h.264 licenses. Only Opera really has an excuse here.

      Really? What exactly is Opera's excuse? Not enough revenue? I doubt that. They probably aren't making much on their desktop browser, but their mobile browsers, combined with their deal with Nintendo to provide their technology for the DS and Wii, should make them more than enough to secure a license with MPEG-LA.

      Firefox, however, can not provide AVC support because of legal hurdles. I haven't read the MPL, but I know that the GPL and the LGPL have an all-or-nothing stance about patents. Either MPEG-LA needs to allow all instances of Firefox, including the downstream versions and forks, a license for AVC, or the project is not allowed to secure one at all. What happens if Mozilla gets MPEG-LA sanctioned AVC support for the upstream version only depends on whether they hold the copyright for all of their code. If they do, then anyone who distributes Mozilla's browser further must remove the codecs or risk a license violation (assuming the MPL has a similar patent clause), effectively making it proprietary for anyone who doesn't know how to, or doesn't want to, alter the browser code. If Mozilla doesn't hold all of the copyright to the browser, then they themselves are in violation of the license, and are ironically prohibited by copyright law from distributing their own browser.

      Google can take a rather unique approach to this problem. Chrome has AVC and Theora support, but Chrome is actually proprietary, licensed under the Google TOS. The free Chromium code on which it is based, however, does not contain any AVC support.

    31. Re:HTML5 for the win? Sorry, that's not a codec. by bennomatic · · Score: 1

      There was indeed a war about GIFs, but the point of the GP poster was that we don't need to worry about it now. You just specify and the browser supports all the majors.

      I remember when Compuserve, excited that the genie seemed to have gotten out of the bottle and everyone was using GIFs on the web, tried to extract licensing fees from hundreds of shareware/freeware software authors who had implemented the specificaiton. You're right that PNG came out of that era because the market spoke, and Free made a good enough stand that PNG is at least equal in standing with GIF and JPG today.

      So the point is do we want to go through the same drama with video formats? The end goal is the same: just specify the file name in a <video> tag and let the browser automagically display it. But to get to that end goal, it may be necessary to have a few commercial licensing wars to get some serious effort behind Free standards like Theora so that the proprietaries relent and release their products in at least a free context if not a Free one.

      --
      The CB App. What's your 20?
    32. Re:HTML5 for the win? Sorry, that's not a codec. by bennomatic · · Score: 3, Funny

      You appear to have just called the members of MPEG-LA "political assholes".

      Was that wrong? :)

      --
      The CB App. What's your 20?
    33. Re:HTML5 for the win? Sorry, that's not a codec. by Denis+Lemire · · Score: 1

      I'll gladly put up with YouTube's implementation of ads over the alternative - they can be closed at any time. They are far more tolerable than most other video sites that force you to watch an ad before you can view the intended video clip, now THAT'S annoying!

      It would, however, be a nice compromise if they used the ad overlays only on clips being embedded in 3rd party sites and placed ads elsewhere on their page when the videos are being viewed directly at youtube.com.

    34. Re:HTML5 for the win? Sorry, that's not a codec. by alvinrod · · Score: 2, Interesting

      Ideally yes, but for everyone with a smart phone or other device that can't afford to waste CPU (And by extension battery life.) on decoding video when it has a perfectly good H.264 hardware decoder, Ogg is not a good solution.

      Linux desktop market share is maybe 1% at most. Linux actually has a good showing in the mobile phone space, but these devices all include H.264 hardware decoders so they don't run into the same issues as desktop Linux.

      The only place Theora makes any real amount of sense is on the desktop and Linux is largely an also ran in that space at the current time.

    35. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      That would be a very Microsoft thing to do.

    36. Re:HTML5 for the win? Sorry, that's not a codec. by Arthur+Grumbine · · Score: 1

      "I think that, given Yutube's volume of crap, any codec Google chose would probably be on a blocklist."

      (link NSFW)

      Although your link is not suitable for work, it is pointedly relevant to the discussion at hand.

      --
      Now that I think about it, I'm pretty sure everything I just said is completely wrong.
    37. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 4, Informative

      Oh come on. What on earth speaks against this:
      <video>
          <source="elephanteatspoop.ogv" type="video/ogg" />
          <source="elephanteatspoop.mp4" type="video/mp4" />
              Get a decent browser.
              <object type="application/x-shockwave-flash" ...>
                    <param name="src" value="player.swf?file=elephanteatspoop.mp4" />
                        No video for you.
              </object>
      </video>
      Usable right now, plays in almost all browsers. Of course you can always make it more complicated to include edge cases, but I don't like that. It's good to push people to update their browsers and get rid of opaque insecure plugins.

    38. Re:HTML5 for the win? Sorry, that's not a codec. by tangent3 · · Score: 1

      Ideally, HTML5 standards would use an open, patent-free standard for use with video. The point of standards is to allow different systems to communicate effectively, the fact that it is open is a requirement of any standard meant for benefiting users. Right now, Theora is about the only major codec that seems to fit the bill.

      Theora is actually based on patented VP3. However, the source code has been BSD'ed and from Wikipedia, "On2 also made an irrevocable, royalty-free license grant for any patent claims it might have over the software and any derivatives, allowing anyone to use any VP3-derived codec for any purpose."

    39. Re:HTML5 for the win? Sorry, that's not a codec. by Shimmer · · Score: 3, Insightful

      Using HTML5 without calling for a codec is like an incomplete function call.

      That doesn't make any sense to me. The <IMG> tag doesn't specify a particular format (JPEG, GIF, PNG, etc.). Why should the <VIDEO> tag specify a format?

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
    40. Re:HTML5 for the win? Sorry, that's not a codec. by moosesocks · · Score: 3, Interesting

      Actually, people who know a thing or two about video codecs tend to dislike Ogg because it isn't a particularly good codec. Its original owners, On2, open-sourced the product, because it was a 10-year-old technology that couldn't compete with any modern product.

      Coincidentally, the internet's benevolent overlords, Google, are in talks to purchase On2, who own the IP to a few codecs that are considerably more modern than Theora (supposedly competitive with H.264 and VC-1). The idea of Google open-sourcing its newly-acquired property is certainly within the realm of possibility, especially if they can squeeze it into the HTML5 spec.

      If YouTube only offers HD content using the new codec, there will be significant impetus for users to switch to HTML5-compliant browsers, or install plugins that enable similar functionality.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    41. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      Err, Ubuntu is the only Linux distribution it has ever been difficult to play MP3 files in. Any other Linux distribution I can think of, including the one Ubuntu is based on, has always had MP3 support out of the box.

      You must not have been using Linux for very long.

    42. Re:HTML5 for the win? Sorry, that's not a codec. by pclminion · · Score: 4, Insightful

      "Done?" I don't think you understand this "technology" thing.

    43. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      Youtube is doing pre-roll ads now, just fyi. Maybe only us heavy users see them.

      And before you pull their chain too much, remember that YouTube is a money-losing division of the Internet's largest advertising service. If its in their best interest, they will run the fucking ads!

    44. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      There is no guarantee of a native library for H.264 unless the end user has QuickTime installed

      Flash is a native H264 library, and if you don't have it, you aren't using YouTube.

      Point being, the fallback situation is no worse than situation normal.

    45. Re:HTML5 for the win? Sorry, that's not a codec. by IntlHarvester · · Score: 1

      Actually, IMO you completely misread the result of the GIF battle. The upshot was nobody cared about the IP issues, except the GNU/Free software types. Everyone else's software worked with GIFs just fine, and they just waited until the patents expired. The only thing PNG had going for it adoption-wise was superior features like transparency.

      Final score: 1 IP Overlords, 0 GNU/Hippies

      So yes, you can go through the same drama with video formats. The question is, do you have the stomach to wait it out 15 years before declaring victory? Meanwhile the average goatporn.com video viewer is looking for .. um instant gratification.

      --
      Business. Numbers. Money. People. Computer World.
    46. Re:HTML5 for the win? Sorry, that's not a codec. by sowth · · Score: 2, Interesting

      From what I've seen, and I did look into the matter a great deal, mp3 decoding (playing) hasn't really been an issue, either because Franhougher (I don't remember how to spell it) doesn't bother to sue anyone who makes software mp3 players or their claimed patent on it doesn't exist / isn't valid.

      The problem is with mp3 encoders. Sometime around the late 1990s the company started suing open source developers until they stopped making any encoders. The only project which survived was GNU Lame, but apparently only because they had the legal backing and they declared their program for "educational and research" purposes.

      This is why Ogg Vorbis gained traction. Open source developers didn't have to worry about being sued when using this format. Also note mpeg 4 video may have similar problems. The group which handles licensing (I believe called MPEG-LA) has repeatedly said they want to charge per file created, not just per encoder.

      It could get really expensive if they decide to do this. This is also why Ogg Theora is important. Not necessarily to get everyone to use it, but for an alternative in case you can't afford or don't want to pay license fees. Some video game companies use ogg vorbis because there is some high flat fee for the license of games. I think it was $30,000(US)/game when I checked. Not a small amount at any rate.

      If you need to encode for your mp3 devices, from what I understand (IANAL) the patent for mpeg layer 2 has run out, so you don't have to worry about royalties. The project toolame encodes layer 2. I know it is on debian and the source should be easy to find. It is older codec, so doesn't compress as well.

      But then from my observations in sound and compression, mp3s are inferior to ogg vorbis. mp3 is just used because every device supports it and everyone is used to it. Some company (same one?) came out with a "mp3 pro" format, but no one used it and no one cared. Probably for the same reason as vorbis, but also because it required licensing fees as well.

      So I am not really sure anyone will notice or care about any issues with layer 2 anyway. I notice a little, but only because I try to get my files really small (below 64kbps if possible)

    47. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      Fuck no. Yeah, I know Ubuntu is the only thing that made the universe livable for you and your kind, but it's really not like that.

      MP3 playback has historically been trivially available on Linux, thanks to a free-of-charge patent license extended to any and all playback software distributed free-of-charge. It was Red Hat et al. with their CYA legal teams who made things difficult for their users, but even then it was trivial to find non-crippled builds of all your media software.

      The reason people want Vorbis is the more dubious licensing situation on the encoding side (note that this is utterly irrelevant when discussing what codecs digital media should be distributed). But encoding has *also* been trivially available, just not necessarily legal if you live in an evil patent-happy nation.

    48. Re:HTML5 for the win? Sorry, that's not a codec. by rhyder128k · · Score: 1

      Finally a suggestion that Novell can get behind!

      --
      Michael Reed, freelance tech writer.
    49. Re:HTML5 for the win? Sorry, that's not a codec. by dotgain · · Score: 2, Informative
      Been using Linux since '95, and plaing MP3s on it since '99. Basically well before Ubuntu has been along. Slackware -> RedHat -> Mandrake -> Debian -> Gentoo and finally to MacOS 10.5

      No, it's never been particularly awkward getting .mp3 files to play. Much as plenty of other things about running on Linux have bugged me, absolutely no problems in decoding every single codec of audio, even the more obscure .mpc, for free.

    50. Re:HTML5 for the win? Sorry, that's not a codec. by smash · · Score: 1
      Another reason vorbis didn't take off is that when encoded at a half reasonable bit-rate, MP3s are "good enough" quality for most people.

      So, the choice is re-rip and re-encode their entire music collection with vorbis - and lose compatibility with most of their hardware players for some minor quality improvement at the same bit-rate, or just encode at a higher mp3 bit-rate in the first place.

      Given the cost of storage these days (even flash on mobile phones and the like) its a bit of a no brainer.

      Thats the boat I'm in anyway - i can't be arsed re-encoding everything and losing compatibility while I'm at it....

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    51. Re:HTML5 for the win? Sorry, that's not a codec. by vadim_t · · Score: 1

      Actually, IMO you completely misread the result of the GIF battle. The upshot was nobody cared about the IP issues, except the GNU/Free software types.

      Oh, they cared, they just didn't make a lot of noise over it.

      The patent was in the encoder. The people who cared about that were the ones who were making programs that encoded .gif files, which would be companies like Adobe, who didn't have that much trouble shelling out the $5000 or so the license was. For the "free software types" it was of course more problematic.

      The only thing PNG had going for it adoption-wise was superior features like transparency.

      You're forgetting support for more than 256 colors. Hardly anybody uses GIF these days, even without the patents, 256 color images look like crap.

    52. Re:HTML5 for the win? Sorry, that's not a codec. by BikeHelmet · · Score: 1

      Seems like the best way to go. Open-sourcing VP7 would probably save them more money (in the long run) than licensing H.264.

    53. Re:HTML5 for the win? Sorry, that's not a codec. by mesch.t · · Score: 0, Offtopic

      "Done?" I don't think you understand this "technology" thing.

      I do!

    54. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      I've been using Linux since the late nineties. The only media files that have ever been a problem to play are Microsoft proprietary media files. Heck, even DVDs play out of the box on anything that's not Ubuntu.

      To stay on the topic of MP3, I distinctively remember using mpg123 on Debian back then, when the current release of Debian was called 'Potato'. Potato also contained XMMS, which also played MP3s. Potato was released in 2000.

    55. Re:HTML5 for the win? Sorry, that's not a codec. by IrquiM · · Score: 1

      Linux desktop market share is maybe 1% at most.

      Lies! It's 80% in my household!

      --
      This is blinging
    56. Re:HTML5 for the win? Sorry, that's not a codec. by Corporate+Troll · · Score: 1

      Franhougher (I don't remember how to spell it)

      Fraunhofer. Even if you'd try to read your version phonetically, it would be incorrect. Just saying.

    57. Re:HTML5 for the win? Sorry, that's not a codec. by fedcb22 · · Score: 4, Informative

      Ogg isn't a codec. Theora is the codec here... Ogg is merely a container format, designed to be used with Theora as video and Vorbis as audio.

    58. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      Is that phonetically as a German or English speaker?

    59. Re:HTML5 for the win? Sorry, that's not a codec. by Lennie · · Score: 1

      100% in mine. I also have a TV based on Linux and DVB-player based on Linux and carnavigation-device based on Linux and a mobile-phone based on Linux (N900 from Nokia uses Maemo and is based on Debian actually). Most of the websites I visit are running on Linux.

      So from my point of view I think Linux is doing pretty good marketshare wise.

      --
      New things are always on the horizon
    60. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      Standards are good... but we're still in a format war over HMTL5 that makes it nearly impossible to implement it right now.

      I think that, given Youtube's weight, any codec Google chose would probably win the format war.

      Standards are good... but we're still in a format war over HMTL5 that makes it nearly impossible to implement it right now.

      I think that, given Youtube's weight, any codec Google chose would probably win the format war.

      Well, youtube is the reason that flash really took off. Before that it was mainly used by shitty web developers with more training in graphic design than usability. We had emb, and java video which both sort of sucked. Right now we're reaching suckiness levels once again because flash video sucks up so much processor usage. Frankly, it's amazing what adobe is doing. Usually only an antivirus suite would be able to make a brand new amazing machine seem like a turd.

      If youtube went HTML5, the only reason flash wouldn't die a quick death is if there was a luddite revolt. But youtube can take a page from facebook there. Change the standard and hold your ground. People will scream bloody murder at first, but it will eventually die down.

    61. Re:HTML5 for the win? Sorry, that's not a codec. by richlv · · Score: 1

      If YouTube only offers HD content using the new codec, there will be significant impetus for users to switch to HTML5-compliant browsers, or install plugins that enable similar functionality.

      that's a very good point. google seems to be trying hard to deal with msie, so that might be another nail in the nailgun (haha).

      too bad the voting server did not survive slashdotting :)
      "Error contacting server"

      another ideas i'd like to see are :
      + ability to download videos (i'm on a slow gprs and not being able to download them makes it almost impossible to watch);
      + more supported upload formats. i tried to upload videos encoded with several codecs to youtube, they all failed. ended up at blip.tv, they had no broblems decoding and converting the videos.

      can't add/search for them on the site right now...

      --
      Rich
    62. Re:HTML5 for the win? Sorry, that's not a codec. by FictionPimp · · Score: 1

      As long as you don't want PNG transparencies, then you have to hope their not using IE.

    63. Re:HTML5 for the win? Sorry, that's not a codec. by AndrewNeo · · Score: 1

      Actually YouTube seems to keep the source file that was uploaded, because they were able to go back and re-transcode everything when HQ (h264) was introduced. I'm sure if they need to transcode to Vorbis it'd take a while but they could do it.

    64. Re:HTML5 for the win? Sorry, that's not a codec. by FlyingBishop · · Score: 1

      The trouble is that H.264 is very likely to be the source. My Droid records in H.264.

      You're highly unlikely to find a portable that records in Theora. It doesn't even merit a mention as an Android core media format

      This is obviously just Android, but I'm fairly sure it's representative of the industry's choices.

    65. Re:HTML5 for the win? Sorry, that's not a codec. by wvmarle · · Score: 1

      There has always been a lot of talk on /. about RedHat not playing mp3 out of the box, supposedly for patent reasons.

      I have never had such an issue using non-US distros (mainly Mandrake/Mandriva, now also Ubuntu). And all those software patents are very much a US-only issue

    66. Re:HTML5 for the win? Sorry, that's not a codec. by bill_mcgonigle · · Score: 1

      + ability to download videos (i'm on a slow gprs and not being able to download them makes it almost impossible to watch);

      hit pause, watch the progress bar finish, and then look at: /tmp/Flash*

      I have to do this on my netbook, not because of my network connection, but because Flash Player takes my entire CPU and does maybe 2 FPS, whereas mplayer will show me the files normally with about 20% CPU.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    67. Re:HTML5 for the win? Sorry, that's not a codec. by bill_mcgonigle · · Score: 1

      It cuts cpu usage in half too.

      Then there's a strong pro-environment reason to make the switch. "Sorry Adobe, we can't support continued burning of that much coal for your un-optimized decoder."

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    68. Re:HTML5 for the win? Sorry, that's not a codec. by richlv · · Score: 1

      ah, but with my gprs longer videos fail to download completely. if i then try to resume downloading by placing position marker near the location it has stopped, often it discards all the data before the marker (at least in the visual player).

      there is one thing preserving sanity, if i'm bothered enough, though : http://code.google.com/p/get-flash-videos/

      --
      Rich
    69. Re:HTML5 for the win? Sorry, that's not a codec. by bill_mcgonigle · · Score: 1

      The tag doesn't specify a particular format (JPEG, GIF, PNG, etc.).

      Your 'etc.' belies the difficulty. Maybe IE also support .bmp, but that's about it.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    70. Re:HTML5 for the win? Sorry, that's not a codec. by bill_mcgonigle · · Score: 1

      Fraunhofer [wikipedia.org]. Even if you'd try to read your version phonetically, it would be incorrect. Just saying.

      Spelling -> Phoenetics is a many-to-one mapping.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    71. Re:HTML5 for the win? Sorry, that's not a codec. by bill_mcgonigle · · Score: 1

      ah, but with my gprs longer videos fail to download completely.

      Is your ISP killing long connections? Might be worth debugging - I don't think YouTube is doing this.

      YouTube mid-stream resume is certainly often broken, though. Another good reason for them to get out from under Flash Server.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    72. Re:HTML5 for the win? Sorry, that's not a codec. by SD-Arcadia · · Score: 1

      On2, which rapidly releases new spec generations, is currently at VP8 and this is supposed to compete with h.264. AFAIK no one has seen an actual VP8 encoder released to the public, so the comparativ quality is unknown.
      The secret about vido codecs is that the implementation and ongoing optimization is more important than the spec itself anyway. Just look at how far XVID has come despite being based on a 10 year old standard. Similarly, Theora was based on VP3, but it is extremely tuned and updated to this day. So Theora is already closer to h.264 (although not on par) than anything from On2 up to VP7 at the moment. VP7 was comparable to h.264 when the h.264 implementations sucked (circa 2005), but so was XVID! since then h.264 implementations, especially x264 has made strides, eclipsing VP7 (and XVID etc).
      The moral of the story is that even if VP7 is made open source, it is only comparable to Theora quality anyway, I doubt there is enough room for improvement in that spec to compete with h.264. VP8 probably has more potential, but all we have ar On2's claims and (biased) demonstrations so far. VP8 open sourced + Google pouring in development effort could produce the breakthrough in 1-2 years, who knows.. But nothing from On2 is the holy grail ATM.

      --
      https://dalgamotor.wordpress.com/ - Elektronik beyinlere ozgurluk asisi (Turkish)
    73. Re:HTML5 for the win? Sorry, that's not a codec. by 5KVGhost · · Score: 1

      Seems to me the best way to proceed is for someone to just do it, and let everyone else try to catch up. Its not like people will stop using youtube.

      Yeah, people here keep saying that, but it's wrong. HTML5 video won't be a viable alternative for at least a year or two.

      If my mother-in-law's browser suddenly stops working on YouTube, she's not going to go download an HTML5 compliant browser, or click through four layers of "ARE YOU SURE?" warnings on her existing browser to install some mystery plugin. She'll just get angry at YouTube for breaking her cute kitten videos and find some better site with videos that actually work.

      I think Flash has been key to YouTube's success. Almost everyone already has a version installed and it works (to some degree) almost anywhere, including on many embedded and handheld devices. Many, many, many other sites use Flash video. They're not using AVI or Quicktime, or any of the other clumsier video formats that never achieved critical mass on the web.

      HTML5 fanboys aside, Flash is the best real-world alternative if you want your video to be viewable by a lot of people.

    74. Re:HTML5 for the win? Sorry, that's not a codec. by tuffy · · Score: 1

      IE8 (and possibly IE7) handles PNG transparency just fine. IE6 did not. But if people are still using IE6, that's the least of their problems.

      --

      Ita erat quando hic adveni.

    75. Re:HTML5 for the win? Sorry, that's not a codec. by jones_supa · · Score: 1

      If my mother-in-law's browser suddenly stops working on YouTube, she's not going to go download an HTML5 compliant browser, or click through four layers of "ARE YOU SURE?" warnings on her existing browser to install some mystery plugin. She'll just get angry at YouTube for breaking her cute kitten videos and find some better site with videos that actually work.

      Maybe there could be a middle ground? Detect if a browser supporting HTML5 video is found, and if not, fall back to Flash. Simple.

    76. Re:HTML5 for the win? Sorry, that's not a codec. by silent_artichoke · · Score: 1

      Can a Limited User install Chrome Frame, or does it require running the installer as a member of the Administrators group?

      You have some good points, but this one threw me off. Why does this matter? If you are a Limited User, the computer is not yours to do with as you wish anyway. Ask the admin to install it for you, but they have the right to say no. If it's your computer, why wouldn't you have admin rights (su. sudo, Run As Administrator, etc.) even if you normally run under a normal or limited user account?

    77. Re:HTML5 for the win? Sorry, that's not a codec. by sjstrutt · · Score: 1

      It doesn't and it shouldn't. The problem is that browser makers can't decide which codecs to support.* A current list of which browsers support which codecs is here: http://diveintohtml5.org/video.html#what-works

      *I still don't believe this is much of a problem though. You can specify a fallback format if the browser doesnt work with your preferred video format.

    78. Re:HTML5 for the win? Sorry, that's not a codec. by tepples · · Score: 1

      Ask the admin to install it for you, but they have the right to say no.

      Because more sites currently use Flash than HTML5, admins are more likely to install Flash Player than HTML5 Playe^W^W Chrome Frame for their users.

      If it's your computer, why wouldn't you have admin rights

      A lot of computers don't come with root. This is common when the computer is not a PC but a mobile device, a set-top device, etc. Several of these specialized devices use the equivalent of the Software Restriction Policy or AppLocker that Windows provides, and the only entity with legitimate admin privileges on, say, a Wii console is Nintendo. Even some devices running free software use such policies; Richard Stallman has referred to this practice as tivoization after its use in TiVo DVRs.

    79. Re:HTML5 for the win? Sorry, that's not a codec. by FictionPimp · · Score: 1

      It half works. It is not just fine. In fact quick google for IE8 png transparency shows tons of issues people have.

      It was supposed to be fixed in IE7, but in practice it was not all that great there either. For example, you can't use a transparent png in a background.

    80. Re:HTML5 for the win? Sorry, that's not a codec. by paimin · · Score: 1

      I knew, and yet I clicked anyway. Damn you!

      --
      Facebook is the new AOL
    81. Re:HTML5 for the win? Sorry, that's not a codec. by ozmanjusri · · Score: 1
      + ability to download videos (i'm on a slow gprs and not being able to download them makes it almost impossible to watch);

      The downloadhelper plugin will fix that for you.

      --
      "I've got more toys than Teruhisa Kitahara."
    82. Re:HTML5 for the win? Sorry, that's not a codec. by silent_artichoke · · Score: 1

      Because more sites currently use Flash than HTML5, admins are more likely to install Flash Player than HTML5 Playe^W^W Chrome Frame for their users.

      When I brought this up, I was thinking of someone's work computer. At that point, if there is a legitimate business need for Chrome Frame, they will install it. It might take an order from Corporate, but they will install it. If there is no business need, then they have no obligation to make sure you can watch Youtube on your work PC.

      A lot of computers don't come with root. This is common when the computer is not a PC but a mobile device, a set-top device, etc. Several of these specialized devices use the equivalent of the Software Restriction Policy or AppLocker that Windows provides, and the only entity with legitimate admin privileges on, say, a Wii console is Nintendo. Even some devices running free software use such policies; Richard Stallman has referred to this practice as tivoization after its use in TiVo DVRs.

      I admit I was thinking only of a PC, but in these cases, you are dependent on the maker of the system to provide a software update to handle HTML 5, Chrome Frame, etc. anyway. You would not be able to install anything at all that they don't want you to have. In this case, it is up to the consumers to raise hell with Nintendo or anyone else to add support. Or you can replace the software on the system, such as running Linux on your PS3.

      FWIW, I do agree with you. This stuff should be installed on a per-user basis in their home folder/profile. Just because I install AdblockPlus or TwitterFox doesn't mean that everyone on this computer will want to use them.

    83. Re:HTML5 for the win? Sorry, that's not a codec. by Leolo · · Score: 1

      While the justification might be bad, honouring autocomplete=off ALL THE TIME is the only right thing to do. Doing otherwise would be misguided.

    84. Re:HTML5 for the win? Sorry, that's not a codec. by nine-times · · Score: 1

      There's only one problem. It ain't finished yet. So we've got the same problems 801.11n had a few years ago. It's hard to implement a moving spec.

      It's not a huge problem, really. When most people are talking about HTML5, they're just talking about the embedded video improvements, which I believe are already implemented somehow in all the major browsers except IE. People have already come up with code that allows websites to try to stream h264 via HTML 5 if possible, if not fall back to Theora via HTML 5, and if that doesn't work fall back to Flash.

      So yes, there is a format war, but Google can either choose to support one format (which might make a big difference in that war) or choose to support all of the formats. I've been hoping that they'd release some of the newer formats from On2 and perhaps allow the whole format war to get settled, but we haven't seen any sign of that yet.

      For anyone who doesn't know, the format war is between Ogg Theora, which is open source and patent-free, and h264, which offers better quality (at least according to many people) and wider hardware support but is patent encumbered. Ogg Theora is based on an old format from a company called On2, but On2 has newer/better formats which are considered to be equal in quality to h264. Google recently bought On2, and there were rumors that they might be planning to open source the encoders/decoders and wave all patent licensing fees, which might settle the issue decisively.

    85. Re:HTML5 for the win? Sorry, that's not a codec. by Sax+Maniac · · Score: 1

      You don't even have to click the freakin' widget! I scroll my screen with the keyboard. As soon as a Flash object scrolls *under* the mouse (which are basically everywhere), it proceeds to eat the keystrokes, and I can scroll no more. It cannot tell the difference between a mouse that moves over the area to decide I am going to interact, it's merely sufficient for something to scroll underneath it. This should be a two-second fix.

      So many things do this now, that I have to carefully "park" the mouse over the damn scrollbar in order to scroll normally!

      --
      I can explanate how to administrate your network. You must configurate and segmentate it, so it can computate.
    86. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      This is true, however you can be pretty sure that JPEG is supported by all browsers.

      Unfortunately the case for the AUDIO or VIDEO tag is different.
      In the audio case I found that Safari supports MP3 and WAV, Firefox supports OGG and WAV, Chrome supoprts OGG and MP3 while Opera supports WAV...

      This is very unfortunate if for e.g. you want to add a short audio notification sound to an AJAX appliation. You need to provide your sound in 3 formats (and also as Flash for compatibility), and rely on the canPlayFile() call on the Audio() object.

      IMHO we do not need a standard codec IF there is a usable universally supported one. In other cases the standard is required for the sake of applications.

    87. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      I think that, given Youtube's weight, any codec Google chose would probably win the format war.

      I'd like to think so, but just don't think it is true. Important players/components in the video over the Web market include:

      • porn purveyers
      • Hulu
      • iTunes Store
      • Netflix
      • Windows
      • OS X
      • other broadcast networks' Web sites

      YouTube lone is no longer the only player that matters. If Netflix and Hulu both chose the same format and it worked well on Windows and OS X, that might be enough to win the war. The iPhone is not to be neglected either as everyone wants to be delivering video to that market, but Apple has more control over it than other device and OS providers do. MS can't really prevent users from downloading software to watch YouTube over the internet via any format that is winning. Apple can prevent the same for iPhone users.

    88. Re:HTML5 for the win? Sorry, that's not a codec. by Anonymous Coward · · Score: 0

      Your 'etc.' belies the difficulty. Maybe IE also support .bmp, but that's about it.

      Safari on OS X supports everything Quicktime does, tiff, PDF, whatever you want to embed.

    89. Re:HTML5 for the win? Sorry, that's not a codec. by LordVader717 · · Score: 1

      The answer to the format war? Free Theora Porn!

    90. Re:HTML5 for the win? Sorry, that's not a codec. by GooberToo · · Score: 1

      Linux desktop market share is maybe 1% at most.

      Could of sworn I remember reading the number is actually closer to 3% and likely under represented, with Apple holding something like 10%. And these numbers are fairly old.

      Meaning, assuming my memory is correct, Linux's numbers today are likely to be 5% and still drastically under represented.

    91. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      For another, the LZW patent expired in June 20, 2003, whereas Mozilla Firefox became 1.0 on November 9, 2004.

      Mozilla Firefox, if you recall, was the isolation of the web browser that was already present in Mozilla itself, which was released in 1998.

      There is no guarantee of a native library for H.264

      All modern commercial OSes have an H.264 decoder, at a minimum.

      unless the end user has QuickTime installed.

      And iTunes is very popular, for those OSes which aren't modern.

      Mozilla Corporation, headquartered in the United States, refrains from violating United States patents in order not to get sued.

      Which is why it was listed as a "worst case". What troubles and irritates me is that the Firefox developers seem to actively be campaigning against the sort of cooperation I'm talking about -- they don't want it to be easy for anyone to fork Firefox and add h.264, or to do exactly what I'm talking about -- tie it to the local media framework, and prompt the user to download codecs.

      The stupidly simple solution is to at least make them pluggable -- even if you don't go the extra mile to plug into existing frameworks that exist for this very purpose, at least make it possible for the user to install additional codecs into the browser. But even this was flat rejected the last time I submitted it as an enhancement request.

      Can a Limited User install Chrome Frame, or does it require running the installer as a member of the Administrators group?

      Why does it matter?

      YouTube uses an H.263 codec for low-power CPUs and down-level Flash players.

      And they also use H.264 for HD videos, all the way up to 1080p.

      Theora is significantly better than that.

      Yes, it's better at something for which it's also a terrible choice. That is, on a low-power CPU, you can get h.264 hardware-accelerated, and h.263 And do you really think someone with a down-level Flash player is going to have an HTML5-enabled or otherwise Theora-friendly setup?

      I suppose you might have a point if you're saying Theora is less CPU-intensive than h.263, but I can't actually find any meaningful comparisons, other than claims it's less CPU-intensive than h.264, which is what we're comparing it with.

      --
      Don't thank God, thank a doctor!
    92. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      Actually there was a bit of a format war about .gif [gnu.org], which is why we have .png [wikipedia.org] available.

      There are two key points here.

      bennomatic covered one already: The browser supports everything, and you don't have to worry about it. I can do this now for downloaded videos -- no matter what it is, I just open with VLC or mplayer, and it works. The only reason I can't do it for web videos is Firefox is being pissy about it, and Chrome actually has a fairly serious bug in their Linux video playback.

      The other point is that PNG was actually much, much better than GIF. There was no way you could reasonably consider using GIF instead of PNG for anything that wasn't animated, other than browser support. So people did it anyway, and browser support followed. If this was the case, then yes, YouTube should support Theora and thus try to force IE to evolve.

      The problem is, it's actually technically worse. H.264 licenses aren't cheap, but they're worth it to people who need to store and serve a lot of video.

      --
      Don't thank God, thank a doctor!
    93. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      Sure, Theora is no H.264, but it handily beats the H.263 that YouTube currently uses for downlevel Flash Players

      Which is worthless here. Why do you think YouTube is doing that, if, indeed, they're still doing that?

      Duh -- to support people who won't (or can't) upgrade their Flash player.

      Now, what makes you think those people would be able to play Theora in any sense? If they can install a new browser, they can just as well install Chrome, which supports h.264. If they can install a new Flash player, they've got h.264.

      Just what market does this make sense for?

      You appear to have just called the members of MPEG-LA "political assholes".

      No, I just called the Mozilla Foundation "political assholes".

      How much would it cost to move Mozilla Corporation and Mozilla Foundation out of the United States?

      Not relevant -- they don't provide any framework or support, and in fact work against, any efforts that might be made outside the United States to develop a less-crippled Firefox. In particular, they flatly refuse to make codecs pluggable in any way, let alone native libraries like DirectShow or QuickTime.

      --
      Don't thank God, thank a doctor!
    94. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      Firefox, however, can not provide AVC support because of legal hurdles.

      Sure they could, but that's not what I'm suggesting.

      I haven't read the MPL,

      Here's a summary:

      Unlike strong copyleft licenses, the code under the MPL may be combined with proprietary files in one program ("Larger Work"). For example, Netscape 6 and later releases were proprietary versions of the Mozilla Application Suite, by adding the proprietary AIM and other parts. The MPL treats the source code file as the boundary between MPL code and proprietary parts...

      There is thus absolutely nothing legally stopping someone from adding h.264 to Firefox. It would just no longer be Free Software.

      But here's the kicker: They already provide a plugin interface. That's how we have Flash. But they refuse to provide any kind of plugin architecture for HTML5 codecs.

      Most users already have some h.264 decoder, legally or otherwise -- all modern commercial OSes come with them. So there's no legitimate reason for Firefox to refuse to do this -- it's entirely Church of GNU people insisting that everything has to remain Free Software.

      Google can take a rather unique approach to this problem. Chrome has AVC and Theora support, but Chrome is actually proprietary, licensed under the Google TOS. The free Chromium code on which it is based, however, does not contain any AVC support.

      Chromium hooks into ffmpeg. I haven't tried it recently, but I remember h.264 working.

      --
      Don't thank God, thank a doctor!
    95. Re:HTML5 for the win? Sorry, that's not a codec. by Simetrical · · Score: 1

      There's only one problem. It ain't finished yet. So we've got the same problems 801.11n had a few years ago. It's hard to implement a moving spec.

      <video> is interoperably implemented in Firefox, Safari, Chrome, and Opera. The core aspects of the spec are not moving. Details are still being worked out (e.g., recent discussions about autobuffer control), but the spec is definitely implementable.

      Standards are good... but we're still in a format war over HMTL5 that makes it nearly impossible to implement it right now.

      Nonsense. YouTube can serve H.264 via <video> if supported, and via Flash if not supported. That could be done immediately. If anything is holding them back, it's probably lackluster browser implementations: so far only Firefox 3.6 supports fullscreen, for instance. Spec maturity is not the problem here, and the format problem isn't an issue either (since they'll have to use Flash for fallback anyway for old browsers).

      --
      MediaWiki developer, Total War Center sysadmin
    96. Re:HTML5 for the win? Sorry, that's not a codec. by dave87656 · · Score: 1

      There are comparison videos available. You can see some slight differences, IMO, but you really have to run them side by side (or back to back) to notice.

    97. Re:HTML5 for the win? Sorry, that's not a codec. by dave87656 · · Score: 1

      Youtube carries some weight. Perhaps by endorsing Theora more devices will be sold which produce it at least for youtube mode.

    98. Re:HTML5 for the win? Sorry, that's not a codec. by dave87656 · · Score: 1

      Any other Linux distribution I can think of, including the one Ubuntu is based on, has always had MP3 support out of the box.

      I can't speak for all distributions but the OpenSuSE and Fedora versions I've seen over the years didn't have easy support of MP3.

      So, no, using an MP3 codec has never been generally difficult, unless you happened to be using Ubuntu and it is only legally questionable only for those living in patent-encumbered countries.

      Which countries are NOT patent-encumbered?

    99. Re:HTML5 for the win? Sorry, that's not a codec. by richlv · · Score: 1

      it's not killing them on purpose - sometimes i have an open connection for days. but sometimes it just sucks, resets connect (which means a new ip -> all ssh and related connections broken).

      with a normal download option i could just leave wget nicely getting me the content and watch it later, without annoying interruptions.

      --
      Rich
    100. Re:HTML5 for the win? Sorry, that's not a codec. by bill_mcgonigle · · Score: 1

      with a normal download option i could just leave wget nicely getting me the content and watch it later, without annoying interruptions.

      Gotcha - shorter download windows, plus HTTP resume, right?

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    101. Re:HTML5 for the win? Sorry, that's not a codec. by richlv · · Score: 1

      well, yes, exactly :)
      a video of some 5 minutes can take up to 30 minutes to download on a bad day. it can have 10 or more connect resets inbetween. youtube player hears lots of curses from me if i _really_ want to see it - usually i just close it.

      --
      Rich
    102. Re:HTML5 for the win? Sorry, that's not a codec. by jseale · · Score: 1

      Is Ogg not done?

      Ogg and its brethren are NEVER done, that's the whole idea behind open source. YouTube would take to these open source technologies like a 5-year old would take to vegetables, as in NOT! LOL

    103. Re:HTML5 for the win? Sorry, that's not a codec. by sowth · · Score: 1

      Thanks. I couldn't remember the spelling and searches were useless because I wasn't spelling it correctly.

    104. Re:HTML5 for the win? Sorry, that's not a codec. by Corporate+Troll · · Score: 1

      What stopped you from searching for "mp3" on wikipedia? It's right there in the second paragraph.

    105. Re:HTML5 for the win? Sorry, that's not a codec. by dangitman · · Score: 1

      Isn't it ironic that owners of other video codecs who are renowned for locking the public out of their formats, by keeping them secret, or trying to charge fees for their use, now don't "want" to be locked out?

      Not really, unless you have some radically different definition of "irony" than the rest of the world (excluding Alanis Morrisette) does.

      --
      ... and then they built the supercollider.
    106. Re:HTML5 for the win? Sorry, that's not a codec. by mysidia · · Score: 1

      I think it does.. for years, they have kept their formats locked out by keeping them secret or requiring licensing for them.. ... and now they find themselves in a situation where they don't want the next generation open web standard to lock them out :)

      Irony, according to WP:

      (from the Ancient Greek eirneía, meaning hypocrisy, deception, or feigned ignorance) is a situation, literary technique, or rhetorical device, in which there is an incongruity, discordance, or unintended connection with truth, that goes strikingly beyond the most simple and evident meaning of words or actions. [...]

      In certain kinds of situational or historical irony, which occur outside works of fiction, a certain factual truth is highlighted by some person's complete ignorance of it, or belief in the opposite of it-- ...

      such ironies are often more evident, or more striking, when viewed retrospectively in the light of later developments which make the truth of past situations obvious to all.

      Irony of fate (cosmic irony) The expression “irony of fate” stems from the notion that the gods (or the Fates) are amusing themselves by toying with the minds of mortals with deliberate ironic intent....

      In history:

      n 1974 the US Consumer Product Safety Commission had to recall 80,000 of its own lapel buttons promoting "toy safety", because the buttons had sharp edges, used lead paint, and had small clips that could be broken off and subsequently swallowed.
      Importing cane toads to Australia to protect the environment created worse environmental problems for Australia.....

    107. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1

      Mozilla's petty squabbling over their control of the Firefox name and logo is already ridiculous enough.

      How is this petty and ridiculous? Mozilla needs to protect their logos and trademarks. That they are doing that also protects users because they know that if it says "Firefox", it will be a real Mozilla product. Organizations enforcing their trademarks is a good thing.

      Mozilla needs to live in the real world, not just some fairy tale.

      --
      Clever signature text goes here.
    108. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1

      What exactly is Opera's excuse? Not enough revenue? I doubt that. They probably aren't making much on their desktop browser

      The desktop browser is about 1/3 of Opera's total revenue. Opera's desktop revenue has more than doubled each quarter for the last few years.

      Opera's "excuse" is that they have always been fighting for a open and patent-free web, and they intent to continue to do so, I guess.

      Also the H.264 licensing costs are only going to increase in the coming years. They are already planning on charging more from 2011.

      --
      Clever signature text goes here.
    109. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1

      Most users already have some h.264 decoder, legally or otherwise -- all modern commercial OSes come with them. So there's no legitimate reason for Firefox to refuse to do this -- it's entirely Church of GNU people insisting that everything has to remain Free Software.

      This is obviously nonsense. Mozilla is aiming to reach beyond the desktop. You won't be able to hook into a decoder on all those smaller platforms out there. You are arguing that H.264 should be able to dictate what devices people use! Also, H.264 licensing will only get more expensive in the future.

      --
      Clever signature text goes here.
    110. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      Mozilla is aiming to reach beyond the desktop. You won't be able to hook into a decoder on all those smaller platforms out there.

      Many of them already have decoders, also -- in hardware -- something Theora doesn't have at all, at any price.

      You are arguing that H.264 should be able to dictate what devices people use!

      No, I am arguing that if we're going to standardize on a codec, it should at least be a state-of-the-art codec, which Theora isn't.

      More generally, I am arguing that we should not standardize on a codec yet.

      But like it or not, that's the reality right now. Some devices have hardware h.264 decoders, so if you want to reach them, you encode in h.264. If you want to consume YouTube on a handheld device, it might be wise to invest in a hardware h.264 decoder. And so the cycle continues.

      I don't like it, but in less than 15 years, the patents will expire, and h.264 will be open. The same can be said for whatever the codec du-jour is.

      I mean, let me get this straight -- are you arguing that handheld devices should suck more bandwidth, or display lower-quality movies, while forcing all video hosting services to transcode their videos -- again -- to a lower-quality codec, all so that the handheld manufacturers don't have to pay for an h.264 license? Not that it's the only license they have to pay, mind you...

      --
      Don't thank God, thank a doctor!
    111. Re:HTML5 for the win? Sorry, that's not a codec. by Brian+Gordon · · Score: 1

      they know that if it says "Firefox", it will be a real Mozilla product

      Are you seriously suggesting looking at the branding on the About screen as a way to verify you have genuine Mozilla software?

      If you're downloading it from mozilla.org then it's a real Mozilla product. Branding doesn't mean anything.

    112. Re:HTML5 for the win? Sorry, that's not a codec. by dangitman · · Score: 1

      But these companies have always acted in their own self-interest. So wanting openness from others, while not wanting to give openness to others is not irony, just standard business practice.

      --
      ... and then they built the supercollider.
    113. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1

      Are you seriously suggesting looking at the branding on the About screen as a way to verify you have genuine Mozilla software?

      I'm seriously suggesting that protecting a brand is a good thing for the consumer because the consumer will know that anything which uses that brand is from that company/organization. It's not just about the about screen, it's about the whole branding.

      --
      Clever signature text goes here.
    114. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1

      Many of them already have decoders, also -- in hardware -- something Theora doesn't have at all, at any price.

      But it's trivially easy to do. In fact, there's no license cost at all, and with major players like Mozilla on the desktop and mobile browser leader Opera pushing it in the mobile market, there's a real reason to support it.

      No, I am arguing that if we're going to standardize on a codec, it should at least be a state-of-the-art codec, which Theora isn't.

      Theora is more than good enough. And you are indeed arguing that private, commercial entities should be able to dictate what we use where. With closed, proprietary, costly technology like H.264, corporations are basically dictating what devices you are supposed to access online content from.

      I mean, let me get this straight -- are you arguing that handheld devices should suck more bandwidth, or display lower-quality movies, while forcing all video hosting services to transcode their videos -- again -- to a lower-quality codec, all so that the handheld manufacturers don't have to pay for an h.264 license?

      The quality isn't notiecably lower, and any cost is more than made up for due to the ever-increasing H.264 licensing costs.

      --
      Clever signature text goes here.
    115. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      But it's trivially easy to do.

      Trivially? I mean...

      In fact, there's no license cost at all,

      Is the R&D cost for developing this really going to be lower than a license cost for a hardware design that already exists?

      with major players like Mozilla on the desktop and mobile browser leader Opera pushing it in the mobile market, there's a real reason to support it.

      Nope, you're still missing a major component -- content.

      Theora is more than good enough.

      Tell that to Google. Again, we are talking about a major investment in real hardware to store larger files to keep the same amount of quality.

      you are indeed arguing that private, commercial entities should be able to dictate what we use where.

      You'll note in my original post that I said that Google is unlikely to choose an inferior codec. I didn't say what I would prefer that Google do, only what I suspect they will do, regardless of feedback.

      You are also conflating one outcome of a suggestion I've made with the purpose of the suggestion. For example:

      With closed, proprietary, costly technology like H.264, corporations are basically dictating what devices you are supposed to access online content from.

      First, have you ever seen a corporation refused access to H.264? It costs money, but it's not "dictating" devices any more than the use of ARM is letting ARM dictate what devices you can use. Even OpenMoko used ARM.

      But you almost seem to be deliberately missing my point. I am not claiming that I would prefer H.264. I am only claiming that it's ludicrous to suggest that the standard should dictate a format, or that a browser should refuse to support a format (even as a plugin), because of temporary legal restrictions.

      Imagine where we'd be now if similar steps had been taken with <img> -- if some genius had "standardized" us on PNG, declaring it to be "good enough", and in particular, refusing to support GIF. Aside from the fact that GIF can be animated, and PNG still hasn't settled on a standard for animation (with poor browser and tool support for each of the options), there's also the need for lossy compression, like JPEG.

      And on top of all that, there's the usefulness of being able to simply upload an image in whatever format you've got and expect it to display properly.

      You seem to be arguing one size fits all, because you desperately don't want to allow even the possibility of a proprietary codec entering the mix. In the short term, I agree with your goal, and I'd rather not have proprietary codecs involved, at least until their patents expire. In the long term, forcing everyone to transcode to a single codec hurts adoption of the standard today, and its long-term viability.

      The quality isn't notiecably lower,

      Surely, you must be joking.

      I mean, here's the very first hit from a Google search for "h.264 vs theora", which also brings up another problem: Dirac. Suppose Dirac gets their act together and becomes a viable alternative. Should Firefox have to be patched?

      Wouldn't it be better if Firefox would simply automatically pick up Dirac, as soon as people install the codec for whatever their OS media framework is?

      --
      Don't thank God, thank a doctor!
    116. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1
      Wow, do you work for the H.264 guys or something?

      Yes, it's trivial to support Theora, not to mention no licensing costs. H.264 costs money today, and will cost even more from 2011.

      As for content, duh. See what the actual Slashdot story is all about?

      For Google, it's probably cheaper to pay slightly more for Theora storage than the outrageous cost of H.264 in the future.

      The point with control is that smaller platforms/companies won't easily be able to pay the insane prices the owners are going to charge.

      BTW, that last link of yours is from 2007. Using Theora 1.0. Epic fail on your part.

      All you seem capable of is spreading FUD and lies against Theora.

      --
      Clever signature text goes here.
    117. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      Wow, do you work for the H.264 guys or something?

      Nope. As I've repeatedly said, I wish things were otherwise here. I like open formats. I prefer Vorbis, or better yet, Flac, for audio. Unfortunately, Theora just isn't there yet for video.

      Please, try to understand that it's possible for someone to actually share your values, yet disagree with you on a factual issue. The fact that I realize Photoshop is generally better than Gimp doesn't mean I'm suddenly an astroturfer for Adobe. The fact that I realize Mumble is better than Ventrilo doesn't mean I'm suddenly a Free Software religious zealot.

      Do you see how that works? I actually look at the available evidence and make up my own mind, instead of just believing what I want to believe.

      Yes, it's trivial to support Theora,

      Great! Have some chipset designs for me?

      No?

      Then please explain how it's "trivial" to add hardware support for Theora.

      not to mention no licensing costs.

      I'm a bit tired of repeating myself here...

      No licensing costs is great. The question is whether it actually offsets the cost of implementing Theora. You haven't addressed this, you've just handwaved it as "trivial".

      As for content, duh. See what the actual Slashdot story is all about?

      And did you see the several points in my last post alone in which I pointed out why Google is unlikely to choose Theora? Chicken and egg scenarios aren't fair, but they are reality.

      For Google, it's probably cheaper to pay slightly more for Theora storage than the outrageous cost of H.264 in the future.

      Citation needed.

      And it's not just storage. It's storage and bandwidth, and their consumers' bandwidth -- it's mobile users paying more in data fees, too.

      The point with control is that smaller platforms/companies won't easily be able to pay the insane prices the owners are going to charge.

      Nor will they be able to develop custom hardware targeted at Theora, will they? No, they'll be taking what they can from the lowest bidder -- which means they'll be looking for stuff that's already mass-produced and has a fair amount of competition.

      BTW, that last link of yours is from 2007. Using Theora 1.0. Epic fail on your part.

      Provide a better one, then, because every comparison I can find favors h.264 on quality per bit.

      All you seem capable of is spreading FUD and lies against Theora.

      I'll paypal you $5 if you can show me actually lying.

      --
      Don't thank God, thank a doctor!
    118. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1

      Unfortunately, Theora just isn't there yet for video.

      Says who? The fact is that most people only need something that's "good enough".

      Great! Have some chipset designs for me?

      No, but as I said, it would be trivial to do it. And no license fees of course.

      Nor will they be able to develop custom hardware targeted at Theora, will they? No, they'll be taking what they can from the lowest bidder -- which means they'll be looking for stuff that's already mass-produced and has a fair amount of competition.

      That will be expensive for them. It will be cheaper to go for Theora. Especially when the licensing terms are tightened from 2011.

      Provide a better one, then, because every comparison I can find favors h.264 on quality per bit.

      That won't be noticeable to most people, and besides, it only needs to be good enough. Picture quality is one of the last things people are looking for. Usability, price, etc. are much higher on the list. Just look at how VHS won over BetaMax, Super CD never took off, YouTube became the most popular site despite having probably the crappiest quality for a long time... Quality doesn't matter a lot of the time, and Theora is more than good enough.

      --
      Clever signature text goes here.
    119. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      The fact is that most people only need something that's "good enough".

      We were originally talking about Google, and I've identified at least a few quality levels for which Theora makes less than no sense.

      Have some chipset designs for me?

      No, but as I said, it would be trivial to do it.

      Then do it.

      I had to learn the hard way, but you don't get to say something is "trivial" until after the fact.

      And no license fees of course.

      You keep hammering this point, and it's a good point, but how important is it, really? In particular, how do the license fees stack up against the cost of hiring a developer to design Vorbis or Theora hardware?

      they'll be looking for stuff that's already mass-produced and has a fair amount of competition.

      That will be expensive for them. It will be cheaper to go for Theora.

      Please, provide some numbers. I'm very skeptical of this assertion, but you don't back it up at all.

      Again: These things are already mass-produced in a market with a fair amount of competition. Both of these things drive prices way down, and that's ignoring the cost of R&D. Usually R&D vs licensing is no contest, unless there's something very wrong with what you're going to license.

      Quick question: Do you drink OpenCola? If not, why not? Especially, if you drink Pepsi, why do you? Think about how much you pay for a "license" of Pepsi (or Coke, etc) versus OpenCola ingredients.

      That won't be noticeable to most people,

      First of all: Obviously, Google thinks it's noticeable. You don't think they've done their research when selecting the bitrate for h.264? If a drop in quality for the same amount of space/bandwidth really "wouldn't be noticeable", why wouldn't they drop quality, use h.264, and save some space/bandwidth?

      Second: On which stream are we talking about? Are you going to claim that Theora is "good enough" for everything from mobile devices on up to 1080p?

      Picture quality is one of the last things people are looking for.

      That depends very much which "people" we're talking about -- and again, this is your opinion versus Google's, and Google is rolling out 1080p. After all...

      Quality doesn't matter a lot of the time,

      If quality really doesn't matter, why is Google rolling out 1080p?

      If quality does matter "sometimes", why would Google use Theora on some videos, and h.264 on others? It'd have to be enough to drop them down below the license cap, which seems unlikely.

      --
      Don't thank God, thank a doctor!
    120. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1

      Quick question: Do you drink OpenCola?

      There's a difference between the web and a soft drink. If you really want a closed, proprietary web, ask Microsoft to resurrect their old Microsoft Network.

      If quality really doesn't matter, why is Google rolling out 1080p?

      I said "a lot of the time". It only needs to be good enough.

      --
      Clever signature text goes here.
    121. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      There's a difference between the web and a soft drink.

      Yes, that's why it's called an analogy. Or why is it that you don't think this is a good analogy?

      ask Microsoft to resurrect their old Microsoft Network.

      MSN is alive and well, last I checked, though probably not in the form you're thinking of.

      I said "a lot of the time".

      And I'm asking you to clarify which times.

      It only needs to be good enough.

      Unless there's something better -- and again, you need real numbers to back up your claim that the licensing costs are worse than additional storage and bandwidth.

      --
      Don't thank God, thank a doctor!
    122. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1

      The web needs to be open. Trademarks do not. That's why your Cola analogy sucks.

      I'm not referring to the MSN web site, I'm referring to the closed Microsoft Network years ago.

      Quality hardly matters at all. Just look at how VHS won over BetaMax, how Super CD never took off, and how YouTube became the dominant video site despite other sites having much better quality video.

      --
      Clever signature text goes here.
    123. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      The web needs to be open. Trademarks do not. That's why your Cola analogy sucks.

      It's not only a trademark, but the formula itself. The web keeps us informed; food keeps us fed, and literally is us. Why doesn't food need to be open?

      Quality hardly matters at all. Just look at how VHS won over BetaMax, how Super CD never took off,

      Yes, you keep repeating this. And yet, while adoption has been slow, we do have Blu-Ray, HDTV in general, and 1080p on YouTube -- and we also have Google themselves saying Theora isn't usable for exactly the same bitrate issues.

      You are handwaving away a real problem by saying it "doesn't matter", and then wondering why people continue to choose proprietary codecs -- and will continue to do so, until open codecs improve. Maybe Dirac?

      --
      Don't thank God, thank a doctor!
    124. Re:HTML5 for the win? Sorry, that's not a codec. by bennomatic · · Score: 1

      The patent was in the encoder

      Thank you for clarifying for "IntlHarvester". I can't believe I left that out. You have it exactly right.

      --
      The CB App. What's your 20?
    125. Re:HTML5 for the win? Sorry, that's not a codec. by hkmwbz · · Score: 1

      It's not only a trademark, but the formula itself. The web keeps us informed; food keeps us fed, and literally is us. Why doesn't food need to be open?

      Because it doesn't prevent someone else from making food.

      Yes, you keep repeating this. And yet, while adoption has been slow, we do have Blu-Ray, HDTV in general, and 1080p on YouTube -- and we also have Google themselves saying Theora isn't usable for exactly the same bitrate issues.

      Indeed, adoption has been slow. Even the massive push to increase adoption has kept adoption dragging along at a slow pace. You can't ignore all the clear examples of quality not really mattering, and your single flawed example of "quality mattering" actually proves my point.

      You are handwaving away a real problem by saying it "doesn't matter", and then wondering why people continue to choose proprietary codecs -- and will continue to do so, until open codecs improve.

      People choose them because there hasn't been a push for anything else. Now we have something good enough for streaming on the web, and it has some major players using it, such as Mozilla and Google.

      --
      Clever signature text goes here.
    126. Re:HTML5 for the win? Sorry, that's not a codec. by SanityInAnarchy · · Score: 1

      Why doesn't food need to be open?

      Because it doesn't prevent someone else from making food.

      It does, however, prevent someone else from making Pepsi.

      --
      Don't thank God, thank a doctor!
  2. YouTube 2.0? by Anonymous Coward · · Score: 1, Funny

    More like YouTube Beta.

    1. Re:YouTube 2.0? by LostCluster · · Score: 1

      I wonder if they'll make the new version of the site invite-only for a few years.

    2. Re:YouTube 2.0? by russlar · · Score: 1

      More like YouTube Beta.

      YouTube is owned by Google, it'll always be Beta.

      --
      Anybody want my mod points?
  3. Google talk by LostCluster · · Score: 3, Interesting

    Google seems to have a policy of talking about new ways to do things, and not making changes suddenly. Afterall, YouTube is the dominant video sharing site right now, and they don't want to let an open source format make them risk their status. So, it looks like HTML5 is going to get a good kick from Google telling them "Hey, we'll use whatever you tell us... but you've got to finish the spec first!" We'll see what this does to that.

    1. Re:Google talk by icebraining · · Score: 1

      If Google only had Youtube involved, that could be the case, but they have Android phones, so they'll have to support a codec that they're phones can decode in hardware.

    2. Re:Google talk by Anonymous Coward · · Score: 0

      That's gonna be a real problem counting that mr. hixie - the sole editor of html5 spec - is a google employee.

    3. Re:Google talk by Simetrical · · Score: 1

      Google seems to have a policy of talking about new ways to do things, and not making changes suddenly. Afterall, YouTube is the dominant video sharing site right now, and they don't want to let an open source format make them risk their status. So, it looks like HTML5 is going to get a good kick from Google telling them "Hey, we'll use whatever you tell us... but you've got to finish the spec first!" We'll see what this does to that.

      Google employs Ian Hickson, the editor of HTML5. He quite literally wrote the entire spec (>1000 pages of complete.html) single-handedly, and personally reads and acts on all feedback. He makes all decisions about the spec unless maybe he's overruled by the HTML Working Group Decision Process, which has happened a grand total of once so far, and that on a purely editorial issue (microdata being a separate spec). Google doesn't need to give anyone "a good kick" when they're the ones writing the spec. They have eight HTMLWG members, too.

      (Of course, if Google didn't employ Hixie he'd probably just do the exact same thing but employed by someone else. But they still do employ him.)

      --
      MediaWiki developer, Total War Center sysadmin
    4. Re:Google talk by pankkake · · Score: 1

      their phones.

      --
      Kill all hipsters.
  4. Exactly one concern by JoshuaZ · · Score: 1, Interesting

    Whatever they do, make sure everything is back compatible with pre-existing stuff. In particular, they need to make sure that whatever they do 1) doesn't break already existing embedded videos and 2) doesn't result in changes to what links are valid for existing videos. 2 is harder than it might seem since the video URLs they use are complicated with multiple forms able to go to the same video. Breaking either 1 or 2 would damage a lot of the internet and also just annoy a lot of people.

    1. Re:Exactly one concern by LostCluster · · Score: 1

      Google's good at supporting previous versions, they've done it a lot with AdWords/AdSense. They supported CPM ads for a long time (and maybe still do?) for existing customers even after mandating that all new users go CPC.

    2. Re:Exactly one concern by scdeimos · · Score: 1

      I don't think 1 or 2 will be as big an issue as you think.

      Buying On2 so that Google can get access to the VP7 and VP8 codecs isn't going to be a magic pill that transforms YouTube overnight - they've still got a whole bunch of video content in VP3 and MP4/H.264 format and it's only going to decrease in quality if they try to transcode it to VP7/8. What you'll likely see is new videos getting encoded in VP7/8 as they're uploaded and fallback to VP3/H.264 transcodings as required by end-user's codec installations.

      Of course, Google being Google, it's possible that they'll just open source the VP7/8 codecs after some period of time (they'll likely want to cash-in on some of the royalties for 12 or 18 months first) and then VP7/8 codecs will be available for all sorts of embedded applications (smart phones, media centers, etc.) in addition to desktop computers.

      This may happen more quickly than 12-18 months if Google wants to use VP7/8 as the default codec on Android, allowing smoother video playback over 3G networks.

      None of this will make On2 shareholders any happier - they already feel they're getting shafted with the Google offer equating to about 60c/share.

    3. Re:Exactly one concern by yuhong · · Score: 1

      Not to mention the naked short selling too.

    4. Re:Exactly one concern by Daengbo · · Score: 1

      You know, if you make an accusation like that, you really need to back it up with some kind of evidence, perhaps a link. Otherwise, you're just a troll.

    5. Re:Exactly one concern by jaminJay · · Score: 1

      They also will want to keep their branding and commonly-understood control mechanisms in place. Dropping Flash for HTML5, for example, will complicate this matter: it will be trivial for embedded video to be controlled with different interfaces, which will annoy some users, who will blame the company whose watermark appears on said video (YouTube) and not the UX designer (embedding site).

      --
      Leela: "Is all the work done by children?" Alien: "No, not the whipping."
  5. Youtube is stunningly bad by Anonymous Coward · · Score: 5, Insightful

    At all things interface.

    1) YouTube: look up the term "aspect ratio". One would think somebody at Google would have heard of this. Many of their videos are uploaded in the wrong ratio. Let us override the specified ratio so we can watch videos in the correct proportions.

    2) Multiple monitor support. It turns out that some people these days have more than one monitor. Some of these people might want to do something else with their computers while using one to watch a full screen video. So don't minimize the full screen video unless we tell you to. Bonus points for supporting more than one screen of video.

    3) The More From and Related Videos boxes should scale to take advantage of big screens, both horizontally and vertically. Since often one is searching for other videos in a series, put them in some kind of order-- alphabetical would be a nice option.

    1. Re:Youtube is stunningly bad by dnwq · · Score: 2, Informative

      on 2), multiple monitor support - that is an Adobe Flash issue, not a Youtube issue.

    2. Re:Youtube is stunningly bad by HeronBlademaster · · Score: 1

      2) Multiple monitor support.

      While I agree that it's really annoying, that's Adobe's fault, not Google's.

      It's fine to throw blame around, just make sure it lands in the right lap.

    3. Re:Youtube is stunningly bad by freaker_TuC · · Score: 1

      Multiple monitor support

      Oh yes, vote me in on this one.. Very annoying on my laptop when watching videos in the meantime..

      Any keystroke brings the video player back to normal size .. drives me nuts!

      --
      --- I am known for the ones who want to find me on the net. Is that a privacy risk or a privilege? One might wonder..
    4. Re:Youtube is stunningly bad by MadUndergrad · · Score: 5, Insightful

      Adobe Flash is a Youtube issue.

    5. Re:Youtube is stunningly bad by Daengbo · · Score: 1

      Not if YouTube moves to HTML5 video.

    6. Re:Youtube is stunningly bad by zippthorne · · Score: 1

      Adobe flash has many issues.

      For instance, the right click menu for changing the flash settings offers an option called "hardware acceleration" Yet, the CPU usage is evidently much higher for simply switching to full-screen. What exactly is the hardware accelerating if it doesn't even use hardware scaling?

      Neat trick for linux users: use the scroll wheel screen zoom function in Compiz instead of the website's "full screen" button to save battery juice on laptops or get away lighter CPUs.

      --
      Can you be Even More Awesome?!
    7. Re:Youtube is stunningly bad by Anonymous Coward · · Score: 0

      Not if YouTube moves to HTML5 video.

      Which I doubt since google is evil.

    8. Re:Youtube is stunningly bad by grepya · · Score: 1

      Adobe flashes yo'tube. Issue.

    9. Re:Youtube is stunningly bad by dargaud · · Score: 1

      YouTube: look up the term "aspect ratio"

      Which is why I love Media Player Classic on Windows where it's very easy to adjust the aspect ratio.

      --
      Non-Linux Penguins ?
    10. Re:Youtube is stunningly bad by Terrasque · · Score: 1

      There is a hack to make Flash stay fullscreen when it lose focus, but that involves some hex editing (or trusting someone providing a patch)

      More info : http://lifehacker.com/5419028/keep-flash-videos-in-full-screen-on-dual-monitors

      --
      It's The Golden Rule: "He who has the gold makes the rules."
    11. Re:Youtube is stunningly bad by MBGMorden · · Score: 1

      So problems are only problems until they are solved? Gotcha.

      Thanks for the insight man!

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
  6. Any move away from flash video is fine by me by AbRASiON · · Score: 5, Insightful

    I loathe it with all my being, please for the love of god do this, somehow!

    1. Re:Any move away from flash video is fine by me by maxume · · Score: 5, Funny

      Have you considered drinking?

      --
      Nerd rage is the funniest rage.
    2. Re:Any move away from flash video is fine by me by LostCluster · · Score: 4, Insightful

      You get the point. Flash is a patent-encumbered format that is slowing down the growth of YouTube... new players are coming out that don't want to implement flash such as TiVo and iPhone, so YouTube has got to re-encode videos to play on this, and that's a mess they'd rather have a better solution to.

      So, really it's a codec war. If there's something more universally accepted than flash... please stand up.

    3. Re:Any move away from flash video is fine by me by Anonymous Coward · · Score: 0

      flash is slowing down the growth of youtube?

      er, youtube is big and growing all the time, i thought that was obvious...? whiffy assertions like that need evidence.

      a large part of the reason for this growth is the fact that the plugin used (flash) is utterly ubiquitous. no?

      the fact that nvidia is about to release cards that can accelerate flash video (useful feature for netbooks) will surely only help flash cement its place. the fact that flash vid on youtube is now capable of hidef is another thing that most people around here choose to ignore, rather conveniently.

    4. Re:Any move away from flash video is fine by me by AbRASiON · · Score: 0, Offtopic

      Looks like the schoolkids (digg users?) have found /. guys, time we impliment a whitelist system.

    5. Re:Any move away from flash video is fine by me by Anonymous Coward · · Score: 0

      So, really it's a codec war. If there's something more universally accepted than flash... please stand up.

      ASCII?

    6. Re:Any move away from flash video is fine by me by ducomputergeek · · Score: 2, Informative

      Flash is the container. The Codec is H.264. .mov is the quicktime container. The Codec is often H.264. .mkv is a container, the Codec is often DivX.

      Container formats != Codec.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    7. Re:Any move away from flash video is fine by me by moosesocks · · Score: 1

      I don't give a crap about patent-encumbered codecs.

      However, it does mildly trouble me that my dual-core mac cannot play a 320x240 video without stuttering, as does the fact that VLC's crappy reverse-engineered codec can play the same FLV file 20-30x more efficiently.

      Given that modern PCs have supported processor throttling for several years now, I have to imagine that the environmental impact of all the extra CPU cycles wasted due to Flash must be staggering.

      I welcome Silverlight if only for the reason that it at least bloody works, and has a halfway-decent free implementation. It might be a trap, but it's a trap that works.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    8. Re:Any move away from flash video is fine by me by Anonymous Coward · · Score: 1, Informative

      So, really it's a codec war. If there's something more universally accepted than flash... please stand up.

      While real life wars are bad, this kind of war is a good one since it drives innovation, evolution and kills off a huge chunk of Flash in the process.

      I don't outright HATE Flash, it is great as a container file for games and other such things.
      It is still entirely possible for a JavaScript file to contain all this information as well*, but the major issue with that is the fact that JavaScript has no decent "preloader" support, or generally bandwidth measurement of any kind. (correct me if i am wrong)
      The only kinds i have seen have been hacked together with 2 languages usually, and that just isn't good enough.
      Until JavaScript has in-built support for this, all the Flash games out there will never move over.

      * The best solution for file storage would be compressed binary strings in the source (near the bottom of course), which are decompressed then base64'd and set as a source.

      Embedding them in to the page is also partially an issue.
      If you embed it in a page, you'd need to detect where it is in the page to replace the insides of the script.
      But that is now a problem, the insides of that script are non-displayable.
      Now you're going to have to write it in a way to insert the JS file contents before or after the script tag. That can lead to messy times.
      Or you could set a DIV somewhere with the ID and constraints, then put the script call in HEAD, more markup but it works.

      All of this is just simply more complicated than Flash is. And more complicated than it needs to be, too.
      You do some stuff, save it as one file, it can be embedded in to any page with one EMBED / OBJECT call.
      Support for embedding JS files in the same way would be nice. (I need to try this, seems like it would work)

    9. Re:Any move away from flash video is fine by me by maxume · · Score: 1

      What makes you think the codecs used by VLC are crappy and reverse engineered?

      --
      Nerd rage is the funniest rage.
  7. Google I love you. by starbugs · · Score: 3, Interesting

    YouTube usable without flash.
    My only reason for using a proprietary OS.

    1. Re:Google I love you. by zoloto · · Score: 1

      If that's really the only reason let me introduce you to youtube-dl, found here: http://bitbucket.org/rg3/youtube-dl/wiki/Home . It certainly beats installing flash on my desktop (linux) so firefox can view the file. I use it like this: ./youtube-dl -b -t $url. The bash script is "/usr/bin/youtube-dl.sh -b -t %1" so you can do "$ youtube $url" ;)

    2. Re:Google I love you. by ianare · · Score: 4, Insightful

      What do you mean? I'm watching youtube on my open source OS right now.

    3. Re:Google I love you. by some_guy_88 · · Score: 3, Informative

      Also. Totem, the default movie player in Ubuntu, comes with a plugin to search and watch YouTube videos out of the box. No flash required (although I think you need to install a codec).

    4. Re:Google I love you. by Philip_the_physicist · · Score: 1

      ISTR seeing a greasemonkey script around which replaces the flash object with an embedded mp4 video. I have also seen bookmarklets around which do the same thing manually.

    5. Re:Google I love you. by cpghost · · Score: 1

      FreeBSD/amd64 here. Using OpenSolaris in a VirtualBox to access YouTube or other Flash-infested sites. Of course, there's also youtube-dl + mplayer, when I'm in a hurry and don't bother starting a whole emulation environment. Still, it would be GREAT if Google provided a Flash-less version of YouTube!

      --
      cpghost at Cordula's Web.
    6. Re:Google I love you. by chammy · · Score: 1

      Hell, I'm watching it on an open source OS without flash

    7. Re:Google I love you. by starbugs · · Score: 1

      All these ideas make you be able to watch youtube videos.

      But they all require you to either install a proprietary player on an open OS, or download the material (thereby violating the youtube terms of service).

      I will look into totem, I'm not sure if it can stream from youtube (instead of playing a download).

  8. Likely to be x264 by nemesisrocks · · Score: 2, Insightful

    Youtube has a large (and ever-increasing) following on mobile devices -- iPhone, Symbian, etc. These low-powered devices are generally able to play video using hardware acceleration.

    One guess as to which codec is likely to have more widespread hardware acceleration.... Youtube is unlikely to alienate mobile users by picking Ogg Vorbis.

    On the up-side; since Internet Explorer is unlikely in the near future to support HTML5 (let alone <video>), I predict that if Youtube does go the HTML5 path, there will still be a Flash fallback.

  9. I'm curious by Whuffo · · Score: 4, Insightful

    How many of you logged in and voted? Out of those, how many looked at the address bar to determine if you were on a Google site?

    1. Re:I'm curious by baka_toroi · · Score: 1

      Firefox autosuggested my password, so I didn't have to check the URL.

    2. Re:I'm curious by tomhudson · · Score: 1

      Good point. Too bad it the whois says it's owned by google. I'd love for it to have been a trojan site.

    3. Re:I'm curious by Anonymous Coward · · Score: 0

      It used Google's SSL based login for going to the account from a Google domain, so it is as legit as one can hope for.

    4. Re:I'm curious by Lemming+Mark · · Score: 1

      I logged in and voted and I didn't bother to check whether the site was owned by Google; but then I don't really use my Google account for anything, so it's not a highly-valued token for me.

    5. Re:I'm curious by afidel · · Score: 3, Informative

      The linked site was not a Google URL, the login page was a Google page with proper SSL certificate (and yes I did check to see if any of the obvious fake SSL cert techniques had been used)

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  10. I have an idea by ClosedSource · · Score: 4, Insightful

    What about improved content? Junk is still junk even if delivered via open standards.

    1. Re:I have an idea by localman · · Score: 1

      One man's junk is another man's favorite video of the week.

      Also note that the addition/removal of a million videos you don't like doesn't have any effect at all on the number of videos you like.

      Content filtering is a bad idea.

      Cheers.

    2. Re:I have an idea by qwertyatwork · · Score: 1

      Not a fan of cat videos eh?

  11. Oh please oh please oh please by Idiot+with+a+gun · · Score: 0, Flamebait

    I have been calling for Flash to be killed with fire for a long time. It's by far the worst internet technology still in use. It even beats out ActiveX (possibly even for vulnerabilities too!). I strongly hope google does this.

  12. Youtube quality police ? by freaker_TuC · · Score: 4, Insightful

    It's their job to get all content online ; It's your job to filter through all the junk ... .. Not theirs .. We don't need a Youtube quality police; just like we don't need any fashion police.

    --
    --- I am known for the ones who want to find me on the net. Is that a privacy risk or a privilege? One might wonder..
    1. Re:Youtube quality police ? by ClosedSource · · Score: 2, Insightful

      "It's your job to filter through all the junk"

      From a business perspective, we are youtube's "product". If that product isn't delivered to advertisers, it will fail. So yes, to be successful for Google, it's their job to deliver the content we want.

    2. Re:Youtube quality police ? by Trepidity · · Score: 1

      Since YouTube's the most-visited video site on the internet by far (and one of the most-visited sites of any kind), I don't see any evidence that they're failing to deliver the content people want.

    3. Re:Youtube quality police ? by Anonymous Coward · · Score: 0

      wait...what?

      If you want improved content, try uploading some.

      It's not google's fault if they're short on documentaries and heavy on the "dude getz kicked in da balls lulz".

    4. Re:Youtube quality police ? by Jesus_666 · · Score: 1

      I'd assert that any video with a nonzero view count is not junk. It's fulfilling its purpose of having someone look at the ad.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    5. Re:Youtube quality police ? by ClosedSource · · Score: 1

      "Fault" has no meaning in this context. It's just business.

      Besides, if I wanted to perform charity work, I'd pick something more important than making Sergey and Larry a bit richer.

  13. Ogg is out for technical reasons by gig · · Score: 4, Insightful

    Google already said that they can't do YouTube in Ogg because the Internet does not have enough bandwidth. The back end of YouTube is MPEG-4 H.264. No matter what format you upload your video in, it's converted to H.264 and that is the primary copy. The upcoming YouTube redesign has also been revealed to be essentially porting the mobile version of YouTube to the desktop. That means HTML5 and MPEG-4, which is what mobiles all use.

    An ISO MPEG-4 audio video player is already built into EVERYTHING, there is no opportunity to change it now. Blu-Ray, set-top boxes, smartphones, iPod and other media players, GPU's, Adobe Flash, Apple QuickTime, iTunes, game consoles, Safari, and Chrome all have H.264. If you don't publish MPEG-4, you might as well send your video encrypted with AES-256 and don't send the key. Nobody can play it if it's not MPEG-4. Ogg is a hobbyist format, suitable for ripping your CD/DVD onto a Linux box and watching them yourself, not suitable for sharing. Sharing requires that you use the community codec, which is what MPEG is all about for 20 years now.

    Also, aside from the players, there is the whole professional toolchain of cameras, recorders, editing suites, encoders, servers. All of it is MPEG-4 because it's the standardization of QuickTime and that was already built into all the tools. Tools that supported proprietary QuickTime were upgraded fairly easily and quickly to support open ISO MPEG-4. Audio video is bigger than the Web. Audio video standardization is more successful than Web standardization. The idea that the W3C is going to tell Pixar and Dolby and such how to make audio video is insane. Tim Berners-Lee invented the World Wide Web, not the entire world.

    And if we want to close one eye to professional content producers, we can open the other to amateurs who have, for example, a Flip camcorder that creates MPEG-4 H.264, or an iPhone camcorder that creates MPEG-4 H.264 and emails clips right from the iPhone. Users are not going to do a round trip through a PC so they can convert that MPEG-4 to Ogg before they share it. Especially not when all their video players have H.264 in their hardware already. That is why an iPod can play more hours of MPEG-4 H.264 than many laptops: the iPod has an "MPEG-4 CPU" so to speak, a dedicated chip that decodes the video with maximum efficiency. It doesn't have a big general purpose CPU like a PC. Multiple codecs is an AUTHORING side thing, not a consumer side thing. You use various codecs on a workstation to get your editing done, you don't demand that the consumer have a dozen codecs in their video player, it's not practical. The community agrees on one consumer codec and we all use it, just like CD/DVD, and everybody wins. Not the Linux community, the free software community, or the Web community ... the audio video community: MPEG.

    This whole debate happened 10 years ago already. You're way too late to change the consumer audio video standard to something other than MPEG-4 H.264/AAC. And you certainly can't change it to something that isn't at least technically superior. Consider that Adobe Flash was the de facto HTML4 video player that is being replaced by the audio and video tags and associated JavaScript API's in HTML5. The video codec in Flash is ISO MPEG-4 H.264/AAC for some years now. The Web is already an ISO MPEG-4 player in HTML4. It will continue to be in HTML5 because that's the format all the video is stored in. Including YouTube, iTunes, Blu-Ray, and all the movies people are shooting with their camcorders.

    In short, Ogg is out for technical reasons: it requires too much bandwidth, it doesn't exist in the players, it doesn't exist in the cameras, it doesn't exist in the editing tools, it is not in the game at all.

    1. Re:Ogg is out for technical reasons by AlexMax2742 · · Score: 1

      Beautifully put.

      --
      I'm the guy with the unpopular opinion
    2. Re:Ogg is out for technical reasons by Urza9814 · · Score: 5, Insightful

      Half of your argument is that things are recorded in MPEG-4 and people aren't going to convert before uploading. But that doesn't matter. Youtube _already_ converts your video when you upload if it's in the wrong format. Hell even if it's in the right format I think they still convert it to make sure it's the right size and bitrate and such. So why does it matter if they're converting MPEG-4 into MPEG-4 or MPEG-4 into Ogg?

    3. Re:Ogg is out for technical reasons by LostCluster · · Score: 3, Insightful

      The resulting file size. YouTube already helped spark Internet speed increases because we were "clogging the tubes" with MPEG-4 video implemented in Flash. Ogg's file size is larger, so it requires more bandwidth. Do you want more usage caps?

    4. Re:Ogg is out for technical reasons by Johnny+Loves+Linux · · Score: 1
      I don't agree with your point of view.

      An ISO MPEG-4 audio video player is already built into EVERYTHING, there is no opportunity to change it now

      So? I don't see any reason why you can't just upgrade to a video player that can play Ogg Theora.

      Ogg is a hobbyist format

      I could be wrong but console game makers use Ogg Vorbis for their audio files. Maybe not all of them, but I was pretty sure Lego Star Wars does.

      there is the whole professional toolchain of cameras, recorders, editing suites, encoders, servers.

      I and anybody else who uses Linux have a toolchain as well. It's called Linux. I mean what's so hard about taking funky video made by Joe User and then hitting it with ffmpeg2theora? So what if their toolchain isn't Linux? It's not as if it can't be transcoded to Ogg Theora.

      The idea that the W3C is going to tell Pixar and Dolby and such how to make audio video is insane.

      W3C concerns itself with web standards. It's up to Pixar and Dolby to decide if they want to comply with the web standards published by W3C. This doesn't have anything to do with why Ogg Theora can't be used by Google which is neither Pixar nor Dolby for that matter.

      You use various codecs on a workstation to get your editing done, you don't demand that the consumer have a dozen codecs in their video player, it's not practical.

      Sure I can. Step 1: Install Debian. Step 2: apt-get install "world". Done. Or, to make it more simply, if people don't want to use Linux, how about just downloading mplayer or vlc? They run just fine on Windows and Apple as well. I mean it's not as if Adobe doesn't require people to *download* a plugin so that you can watch flash videos? Why is it reasonable for Adobe to be able to "force" people to download a flash plugin, but it's not reasonable to expect people to download mplayer or vlc to watch all sorts of video codecs?

      That is why an iPod can play more hours of MPEG-4 H.264 than many laptops

      I could be confused but I thought you could make ipods play Ogg Theora when running Linux on them. And it's not as if Apple, Inc. couldn't make a firmware update to the ipod OS so it can Ogg Theora.

      This whole debate happened 10 years ago already.

      No it didn't. Ogg theora wasn't around 10 years ago.

      You're way too late to change the consumer audio video standard to something other than MPEG-4 H.264/AAC. And you certainly can't change it to something that isn't at least technically superior.

      If I remember correctly mp3 is a standard that;s been around for 25 years? That was pushed by consumers, not manufacturers, especially not the likes of RIAA. Manufacturers had to scramble to provide support for a format that enough care wanted. I don't see how your argument changes that fact: if enough consumers demand it, then manufacturers who want to make a profit will provide a way. As to whether or not it's superior, I don't think flash was superior when youtube.com started using, and even if you don't agree, consider betamax vs. the VHS format. The inferior format won. So it's not a given to assume technically superior formats must win everytime, not saying that Ogg Theora is a superior or inferior format.

      it requires too much bandwidth,

      You keep going on about bandwidth. Do you think that Ogg Theora has worse compression than the flash that's being used now? Why then do you keep going on about it? Ogg Theora doesn't have to the best compression of all the video codecs. It just has to be good enough. And I haven't seen a convincing argument yet that it doesn't.

    5. Re:Ogg is out for technical reasons by alvinrod · · Score: 1

      It matters because the smart phones, iPods, and other small devices that are becoming a major way that people consume content don't have Ogg Theora hardware decoders. These devices do have H.264 hardware decoders and won't have to use the CPU to decode and playback the video, saving a lot of battery life.

      As far as I know, there aren't even any Theora hardware decoders in existence, or if there are they aren't being mass produced. There's also not a lot of point in making one either as Ogg isn't a widely used video codec so that hardware won't see much use. Do you see the vicious cycle that's been formed? Even if someone were to mass produce the chips and someone else were to actually include them in their hardware, by the time they reach any fragment of market share, the rest of the world will have moved on to H.265.

    6. Re:Ogg is out for technical reasons by Anonymous Coward · · Score: 0

      Sigh. All your arguments are flawed and more than a little naive.

      But let's ignore that. Let's have a reality check. If YouTube ends up streaming Ogg it means that you were right all along. Ask yourself, do you really believe that will happen? Do you really believe that your opinion will change Google's mind and they will start using Ogg?

      I didn't think so.

      I am sorry, kid. We all want the world to be better at some point in our lives, but then we grow up and pour ourselves a stiff drink.

    7. Re:Ogg is out for technical reasons by cecom · · Score: 1

      What you said :-)

    8. Re:Ogg is out for technical reasons by Idiot+with+a+gun · · Score: 1

      MPEG-4 is still patent encumbered. So if we switch to it, we aren't really gaining that much. How about we finally go to audio/video standards that people can use without worrying about being sued?

    9. Re:Ogg is out for technical reasons by Idiot+with+a+gun · · Score: 1

      Maybe, combined with some legal pressure, our ISPs would actually start upgrading their backbone, and delivering on their promises (or promising more reasonable things).

    10. Re:Ogg is out for technical reasons by Anonymous Coward · · Score: 0

      Bullshit.

      You clearly haven't got a clue about video encoding, if you did then you'd know that most people tell their codecs to produce video with a specific bits per second (Youtube uses 350kbit/s); it doesn't mean jack if the format is Theora or MPEG4-ASP or H.264, the only difference is the quality of the picture that comes out when it's decoded.

    11. Re:Ogg is out for technical reasons by Idiot+with+a+gun · · Score: 1

      That's patently false. Even among lossless codecs there can be a drastic difference in sizes with the same bit rate. A great example of this is WAV vs. FLAC. FLAC is lossless, so all data is preserved (just, represented differently), yet it can be 30-50% smaller than WAV on music. And things get even more complicated when you start looking at lossy codecs (like many video codecs) that are willing to throw away "useless" data.

    12. Re:Ogg is out for technical reasons by BondGamer · · Score: 1

      Everyone has already switched to MPEG4, that was the entire argument. The market has already determined that MPEG4 is the best out there and everyone is running with it. Until something comes along that blows MPEG4 away in most aspects, there is not going to be a change. Just because it isn't open source does not make it a bad pick.

    13. Re:Ogg is out for technical reasons by indi0144 · · Score: 0, Flamebait

      So true, sadly, FOSS zealots will continue with the circle jerk moaning and screaming because their pet codec it's not on par with something THAT IS USED IN THE *REAL WORLD* by people and big business DOING *MONEY* WITH IT. Admit it, OGG failed, get over it and move on.

      Do you really want aunt Betsy to return to IE6 after trying and failing to use Firefox on youtube? After all.. IF ITS WORKING WHY FIX IT? right?

      I hope you get moded up to 11

    14. Re:Ogg is out for technical reasons by tsj5j · · Score: 3, Insightful

      The above author clearly did not read the post fully, for it's clearly not "half-his-argument". The main argument is that Youtube probably can't/won't convert their existing video collection, which is likely t be huge. The second argument is that many viewing devices only support H264. The third argument is that OGG uses more space and hence bandwidth, increasing pressure on ISPs and depleting your bandwidth cap faster. The fourth argument is that it's already a standard adopted by many commercial devices, with shooting devices being one of them. Well, sure, YouTube can convert them all, but isn't that a huge waste of CPU cycles on their part? No point insisting on a format that cannot deliver in performance, compatibility and popularity.

    15. Re:Ogg is out for technical reasons by Anonymous Coward · · Score: 0

      WAV is typically raw, uncompressed data. Sometimes you want your audio that way.
      FLAC is lossless, that means lossless compression.
      And: The size of a multimedia file in bytes is the product of the bit rate (in bit/s) and the length of the recording (in seconds), divided by eight. Unless this is VBR we're talking about, then we'll have to look at the average bit rate.

    16. Re:Ogg is out for technical reasons by Anonymous Coward · · Score: 0

      The bit rate of FLAC is smaller than the bit rate of the source wav.

    17. Re:Ogg is out for technical reasons by Perky_Goth · · Score: 0, Flamebait

      You fucking nitwit, she won't be able to use Firefox because Firefox can't implement H264 and still be free software. That's why we want OGG.
      Idiot.

    18. Re:Ogg is out for technical reasons by BikeHelmet · · Score: 2, Informative

      FYI, ogg is a container. Like .avi and .mp4

      You're talking about Theora (video) and Vorbis (audio)

      Vorbis appears to be superior to everything but the most optimized AAC encoders - at least at semi low bitrates employed in streaming. Youtube sounds about like 40kbit vorbis. (really bad) But that also means they could shave almost 100kbit off their stream bandwidth by using it rather than mp3. The downside is it takes twice as long to encode.

      Theora is another story. H.264 is so superior it's ridiculous - but if Google open sources VP7, there would be some real competition.

      Youtube has few of the H.264 optimizations enabled, but once you crank everything to the max in x264, it's a thing of beauty. I've been experimenting with it a lot recently - it's amazing what it can do with 512kbits available.

    19. Re:Ogg is out for technical reasons by Skapare · · Score: 1

      Things can change. There is enough bandwidth NOW (wasn't a few years ago). The real problem is Vorbis just isn't stable as a standard, yet. They need to push to get a stable "Vorbis V1" and put future work into "Vorbis V2". Youtube can simply offer the option of video formats based on the HTTP headers in the request. Seems to me based on what you say, we only need TWO formats, anyway ... one for corporate profits and one for the people.

      --
      now we need to go OSS in diesel cars
    20. Re:Ogg is out for technical reasons by Skapare · · Score: 1

      Converting the existing videos is not the issue. That can be done slowly. Converting new videos is where it's at. The obvious solution is for YT to offer the videos in TWO formats: the most efficient format, and the most efficient open format. Let the HTTP headers automatically determine that with the Accept statement, and provide a fallback via some Javascript on the page that allows selecting the preferred format in case something is not working. There should also be such a selection for reducing the video resolution, too (e.g. "show me only low definition because my ISP sucks and can't handle HD"). Don't worry about converting all the old videos. Convert the popular ones and put a link in the template to let people ask for a conversion on less popular ones. I'm sure there's a ton of videos out there no one watches anymore.

      --
      now we need to go OSS in diesel cars
    21. Re:Ogg is out for technical reasons by donatzsky · · Score: 1

      And here I thought that 128kbps meant 128 kilobit per second. Mind telling me what it actually means then?

    22. Re:Ogg is out for technical reasons by gr8_phk · · Score: 1

      Even if someone were to mass produce the chips and someone else were to actually include them in their hardware, by the time they reach any fragment of market share, the rest of the world will have moved on to H.265

      The same chicken-and-egg problem that locks out OGG also blocks migration to H.265. OTOH if Google opens up VC7 they can use it on YouTube today and develop hardware for their own phones next year. BTW, video is always reencoded for phones today anyway, so the web can and will go to whatever format is appropriate for it.

    23. Re:Ogg is out for technical reasons by MBGMorden · · Score: 1

      Uncompressed WAV and FLAC do not have the same bit rate (FLAC doesn't even have a specific bitrate IIRC). "Bitrate" is exactly what it sounds like - the number of bits required per second to store the stream.

      160Kbps is 160Kbps. There may be some SLIGHT differences in final file size due to the actual container and metadata, but the stream itself will be the same size. The differences will increase a bit if you're talking average bitrate instead of constant bitrate, but not much.

      I think what you MAY have been inferring your data from is that some lossless codecs can sound better than others even at the same bitrate, but that's a seperate issue. 128Kbps AAC for example typically sounds a little better than 128Kbps MP3, but size-wise, they're the same.

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
    24. Re:Ogg is out for technical reasons by Fwipp · · Score: 1

      Sure, Ogg theora *works* on a jailbroken iPhone. But it's dog slow, because it's not hardware accelerated. That's not something you can fix with a firmware update.

    25. Re:Ogg is out for technical reasons by Anonymous Coward · · Score: 0

      What does not exists is a brain inside of your skull :( You call the MPEG is a community codec!!! How wrong and foolish you are! MPEG is a patented codec and Theora is a free of patents codec for public to use. Do you provide us the patent coverage for MPEG for us to use MPEG? By using MPEG without patent coverage is breaking law. Using Theora does not break law. See this to understand your bandwidth lie: http://people.xiph.org/~greg/video/ytcompare/comparison.html

    26. Re:Ogg is out for technical reasons by SomeKDEUser · · Score: 1

      It depend for whom or what. For exemple, if google were not in the business of having as much content as possibe upoaded to the cloud so they can monetize retrieval, then purely technical questions such as bandwidth would predominate.

      On the other hand, google thrives from the extension of services and media on the network. And knows, from experience, that a foundation of open standards is best to foster explosive growth. So they might well go for ogg just to prevent another company (adobe) from holding a deadlock in a critical market.

      From the user's point of view, of course, it is clear that locked standards are a disaster. Just think of ms-doc: the network effect killed the competition more efficiently than any underhanded tactic of microsoft themselve.

      So from your point of view, as a user, a locked format is a terrible choice. From google's point of view, it is a tradeof. But why you would support it, unless you were the google employee responsible for optimising bandwidth usage, is beyond me.

    27. Re:Ogg is out for technical reasons by Anonymous Coward · · Score: 0

      Theora. You mean Theora, not ogg. Ogg is a container like avi and mkv.

    28. Re:Ogg is out for technical reasons by indi0144 · · Score: 1

      I'm sorry I was a dick on that comment but you are wrong too, you may have OGG after all it's good to have options but if H264 it's going to be used as standard I know someone would make the license almost free, or at least Google can help Mozilla to deal with the license fees, in the end it's cheaper to Google (youtube) to sponsor H264 license fees for the mere sakes of helping reduce their bandwidth.

      Anyway I was complaining, as was the GP, about MPEG-4 H254 AAC BEING A STANDARD ALREADY WITH HARDWARE SUPPORT on most recent GPUs so theres no point in continuing the flamewars about OGG vs. H264, I know we can hack something onto our Firefox so we can choose OGG, but for the sakes of the ALMIGHTY MARKET it's death jim, and maybe we can just concentrate on finding alternatives or bitching to the MPEG consortium so the license for the open source browsers can be gratis.

      We all should be happy that in the future we can move on from Flash video, OSS got that by the hand of HTML5 but the codec it's proprietary, whatever, __you just can get it all__, it pisses me off when people act like 12 years old spoiled girls.

      Note that I didn't answer to you idiot and nitwit insults, in part because I deserve them, after all we may speak the same lengua. carry on.

    29. Re:Ogg is out for technical reasons by tsj5j · · Score: 1

      That is alot of extra cost (conversion = cpu + time), hacks (tracking what are converted and which aren't) and HTTP tricks (which not all mobiles/desktop browsers report correctly).

      Let me remind you that YouTube is not making Google profit (IIRC).
      Any sensible corporation would choose a route that is more maintainable and at a lower cost.

    30. Re:Ogg is out for technical reasons by Perky_Goth · · Score: 1

      Fair enough, I was a bit dim as well.
      What I see as an issue is that HTML supporting H264 means Firefox can either support HTML5 or be free software, not both. It's much worse than having to rely on Flash, at least that's a plugin you can install in any browser. Now imagine telling people that Firefox needs this extra thing that someone somewhere is going to code, that's not going to win over anyone.
      Basically, I'm pissed that everything is getting very, very closed all over again and thanks to stupid IP laws there's nothing to be done about it other than breaking the law repeatedly to do what we want with what we buy (FF is free; what it runs on is not, hence the material aspect).
      God knows how this will be fixed.

    31. Re:Ogg is out for technical reasons by Anonymous Coward · · Score: 0

      Youtube could keep current video's in h.264 and future videos in Ogg (thedora), converting upon demand. Problem solved.

      ps. ogg will not go away, just like Linux. Better to support it now then wait for it to byte you in the tail.

    32. Re:Ogg is out for technical reasons by hkmwbz · · Score: 1

      Licensing H.264 from 2011 will cost you according to usage. Bandwidth and storage will keep getting cheaper, but licensing costs for H.264 will continue to increase. Do the math.

      --
      Clever signature text goes here.
    33. Re:Ogg is out for technical reasons by hkmwbz · · Score: 1

      Let me remind you that YouTube is not making Google profit (IIRC).

      This makes it even more important to get away from the ever-increasing H.264 licensing costs. Things are looking bleak from 2011 when they will tighten the grip.

      --
      Clever signature text goes here.
  14. Users are stunningly bad by LostCluster · · Score: 2, Informative

    1) YouTube: look up the term "aspect ratio". One would think somebody at Google would have heard of this. Many of their videos are uploaded in the wrong ratio. Let us override the specified ratio so we can watch videos in the correct proportions.

    Can we also fix the "Tilt yer Head" series of videos? This isn't Google's problem... it's a PEPKAC situation. Users fail.

    2) Multiple monitor support. It turns out that some people these days have more than one monitor. Some of these people might want to do something else with their computers while using one to watch a full screen video. So don't minimize the full screen video unless we tell you to. Bonus points for supporting more than one screen of video.

    Again, not YouTube's problem. Your browser is doing this for you. They need to fix it.

    3) The More From and Related Videos boxes should scale to take advantage of big screens, both horizontally and vertically. Since often one is searching for other videos in a series, put them in some kind of order-- alphabetical would be a nice option.

    Again, user error. If it's a series, it should be uploaded in order. Go to the user's page. Related episodes sorts the series by content, not sequence. More form this user gives you the most recent episodes. If you want the back catelog, you want the user page.

    1. Re:Users are stunningly bad by tepples · · Score: 2, Insightful

      If it's a series, it should be uploaded in order.

      That's not always possible, especially in the case of videos that get replaced with a newer video containing revisions.

    2. Re:Users are stunningly bad by JoshuaZ · · Score: 1

      It would be a very tiny bit of code for the uploader to tag a set of videos as going in a certain order independent of the order uploaded.

    3. Re:Users are stunningly bad by Graff · · Score: 1

      it's a PEPKAC situation. Users fail.

      PEPKAC eh? Sure you don't mean that it's a PEBKAC problem - Problem Exists Between Keyboard And Chair?

      You fail. ;-)

  15. DMCA Reform by DarkHelmet · · Score: 5, Insightful

    How about calling for reform of the DMCA system on YouTube?

    Currently, it's possible for a content creator to have his or her video taken down for copyright infringement from what is functionally an anonymous party. While YouTube's DMCA claim form DOES ask for name, phone number and address, none of these items are verified before YouTube goes ahead and takes these videos down.

    Because of this, there's a lot of False DMCA action on the site from people who are only interested in suppressing others viewpoints.

    Since people on slashdot for the most part care about Freedom of Speech, I urge you all to upvote the DMCA reform issue on there.

    Thank you.

    --
    /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
    1. Re:DMCA Reform by Doug52392 · · Score: 1

      Start sending fake DMCA notices? If no one thinks its a problem except a bunch of basement-dwelling nerds, the problem won't go away until someone shows the braindead masses who browse youTube that there is a problem.

    2. Re:DMCA Reform by LostCluster · · Score: 3, Informative

      Google's doing what the DMCA requires... what would be nice is if they had to provide proof they hold a copyright on something, and therefore reveal their identity so false claims could be taken to court.

    3. Re:DMCA Reform by slikk · · Score: 1

      The problem here is the DMCA law. YouTube is basically following the law that if they receive a DMCA request, they must follow it and take down the videos.

    4. Re:DMCA Reform by Smidge204 · · Score: 1

      Sending fake DMCA claims is itself against the law. This is part of the problem - it's not just people effectively getting censored by some random fuckwit, it's that YouTube's current system actually facilitates violating the DMCA from the side of the claimant. There is absolutely zero accountability and filing a counterclaim exposes the victim's personal information to the accuser. Entire accounts can be permanently suspended by filing multiple false DMCAs against it in quick succession but there is absolutely no ramification for the account that does so, even if every single claim is challenged and shown to be false.

      As for trying to show there's a problem, there's already a group trying to prod YouTube into action and I've been trying (admittedly with great difficulty so far) to catalog abuses as I become aware of them.
      =Smidge=

    5. Re:DMCA Reform by Smidge204 · · Score: 1

      Making fraudulent DMCA claims is ALSO against the law. YouTube is also allowing people to violate the DMCA by allowing anonymous, fully automated, no-accountability reporting of content.

      =Smidge=

    6. Re:DMCA Reform by Cruciform · · Score: 2, Informative

      If it's another user waving the false flag of DMCA for one of their own YouTube submissions, can't they just be told to bugger off using the following section from the terms of service?:

      You also hereby waive any moral rights you may have in your User Submissions and grant each user of the YouTube Website a non-exclusive license to access your User Submissions through the Website, and to use, reproduce, distribute, display and perform such User Submissions as permitted through the functionality of the Website and under these Terms of Service.

      Between that and fair use for critique/parody, you'd think that the DMCA could only be justified when the user has uploaded copyrighted content that didn't belong to the complainant in the first place.

    7. Re:DMCA Reform by rozeboosje · · Score: 1

      The DMCA issue has been a huge problem for at least 2 years now. That, and the way people have been abusing the site's Flagging system. see http://www.censortube.eu/ Of course there are problems with the DMCA law itself, but that is another fight in an entirely different arena. YouTube, in the mean time, could have made a few relatively minor changes that would have eased the pain of this abuse considerably, whilst still conforming to the requirements of the law. For example, when it comes to DMCA claims it is, of course, required by law to take down the video whilst claimant and recipient sort out their dispute in court, but there is no legal requirement for the "strikes" that YouTube imposes automatically on the recipient of any DMCA claim. THAT is an internal matter of how the site is operated. YouTube could, quite easily, implement a policy in which DMCA claims that are NOT accompanied by confirmed personal details of the claimant will not proceed beyond taking down the video. No strikes. No penalties against the YouTube account of the recipient. And they could also implement a minor change to their procedures that would ensure that personal details sent to them in a COUNTER claim are only forwarded to a confirmed physical location such as a home address, thus ensuring that a recipient of a false DMCA claim can proceed to sue the claimant if they refuse to follow on the claim by legal proceedings - something they committed to when they made the original claim, or report the claimant for committing perjury - something they had to indicate they understood when they made the claim. The problem with the current YouTube implementation of the DMCA system is the lack of accountability imposed on the claimant. Similarly, flagging can be handled differently. YouTube claim that they review all flags, so in what follows I will argue on the basis that humans in YouTube WILL review flagged content. At the moment it's too black and white. If a flag is rejected, nothing will happen, if it's upheld, you receive a strike against the account. It would not be too hard to implement a system in which flaggers could opt to accept accountability for their decisions, and punitive action (i.e. strikes against the account) is only taken if flags are made by people who do so. Anonymous flags may still be upheld, but can at most result in a take down of an individual video. Again, not a HUGE change in procedure, but one that takes the "anonymous coward" element away. Etcetera.

    8. Re:DMCA Reform by CGordy · · Score: 1

      Although making fraudulent DMCA claims is against US law, I have yet to hear of the US government successfully extraditing anyone from a foreign country to face charges - making a false declaration under US law may not even be a crime in some countries. As American companies appear to be required to honour DMCA claims from foreign entities, it seems like an obvious loophole.

      This happened a few years ago to the Chaser (an Australian satirical TV show). Wikipedia article here - scroll down to the section titled "YouTube video removal".

      YouTube's major advantage is its brand recognition - it is basically synonymous with online video. When the DMCA system is abused by mass takedown notices, people are encouraged to find alternatives, eroding the YouTube = online video association.

      In effect, the law disadvantages media sharing companies with data domiciled in the US - it requires sites to implement a cost effective system to deal with DMCA requests, and the only way to do this seems to be to automatically honour them all.

      Disclaimer: IANAL

    9. Re:DMCA Reform by Smidge204 · · Score: 1

      It's not so much that I blame YouTube for the DMCA flagging system - I understand fully that it is the only reasonable way to comply with the law. (And clearly the law itself needs revision, but that's another topic)

      However, getting too many DMCAs filed against you results in automatic suspension of your account. There is NO penalty for filing a false DMCA.

      Filing a claim and filing a counterclaim results in exposing your personal information to the other party, but it is absolutely trivial to falsify this information when filing a notice, making the process essentially anonymous (or even malicious if you implicate someone else). I don't know if you have the same opportunity to falsify your identity when counterclaiming... though you probably do.

      The bottom line is the current system greatly favors those who want to abuse the system over those on the receiving end, while not really benefiting legitimate DMCA cases either way.

      In fact it was just the past week that someone (allegedly) filed about 200 false DMCAs in total with absolutely no ramifications for it at all... at least from YouTube. Without getting too specific some of the affected users managed to get in touch with the guy's parents and shut him down that way. It shouldn't have to come to that.

      I say allegedly because I haven't been able to verify them all...
      =Smidge=

    10. Re:DMCA Reform by alexo · · Score: 1

      Making fraudulent DMCA claims is ALSO against the law.

      No, it is not.
      When you make a DMCA claim, you swear, under penalty of perjury, that you are the copyright holder, or authorized to act on behalf of the copyright holder, of the work that you claim is being infringed. That is the only claim that, if false, can result in penalties. See example.

      For example, say you upload to youtube a video of your CongressCritter shagging a hamster. Said CS gets wind of it, realizes that this may harm their reelection plans, and submit a DMCA notice stating that your video infringes on their PhD thesis "Hamsters as an Alternative Fuel Source". They swear under penalty of perjury that they are the copyright holder of HaaAFS, which is true, but face no penalties for falsely claiming that your video infringes on it.

      This is exactly what the content distributors wanted and it is one of the things that make the DMCA such a bad law.

      Disclaimer: IANAUSCitizen, IANEvenAUSResident.

    11. Re:DMCA Reform by Smidge204 · · Score: 1

      A false DMCA claim is not the same as a baseless DMCA claim.

      A false DMCA claim is when you file a complaint without actually owning any of the intellectual property involved. You are NOT the copyright holder and therefore it IS perjury.

      A baseless DMCA claim is when you DO own the intellectual property involved, but the DMCA is not applicable. (e.g. the fair use clause)

      One is fraud and perjury, the other is just being a dick about it. There's a difference.
      =Smidge=

  16. DMCA Notices on youtube by DJLuc1d · · Score: 2, Insightful

    Don't forget how out of hand the DMCA notices have gotten. Videos that are clearly fair-use are have their entire audio tracks wiped out, even when audio is a major component of the video.

  17. Updates: Automated responses. by Anonymous Coward · · Score: 2, Funny

    Google will announce automated comment generation as a new feature, citing users' complaints that it is too time consuming to type out grammatically incorrect sentences and spam.

  18. Uh oh by the+brown+guy · · Score: 3, Funny

    ""Slashdot -style comment moderation and filtering."
    trreeves, Portland, OR - "

    He must be new here...or have no idea what /. is about

    I suggested More porn...

    --
    Orbis terrarum est non altus satis
    1. Re:Uh oh by Bob+The+Cowboy · · Score: 1

      I suggested more porn...

      You must not be new here.

  19. They should ditch comments entirely by Nimey · · Score: 5, Insightful

    Youtube is a byword for horrifyingly stupid and banal comments. The best Youtube comments still make Slashdot seem like a collection of Nobel prizewinners.

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
    1. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      You can always disable comments on your videos.

    2. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      so much for 'full of mischief'

    3. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      Video posters can disable comments on their videos if they want, I've seen several that have done that.

      As far as the comments section itself goes though, it is better then you think, it just depends on which video you watch. Videos on highly technical subjects like a Google engineer lecturing on Distributed Computing Architecture can have interesting comments pointing out problems for instance. On the other hand, a video about evolution will attract young-earth creationists posting head-meets-desk worthy comments.

    4. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      You obviously haven't seen /b/ on 4chan.

    5. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      Popular videos attract bad comments. Niche videos attract on-topic, interesting comments.

    6. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      you're a fa g.

    7. Re:They should ditch comments entirely by BoppreH · · Score: 1

      Well, it's always useful to find out what the music playing in the video is.

    8. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      Youtube is a byword for horrifyingly stupid and banal comments. The best Youtube comments still make Slashdot seem like a collection of Nobel prizewinners.

      Yes, us is good!! :)

    9. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      /b/ is deliberately like that--it's the whole point.

    10. Re:They should ditch comments entirely by eigenstates · · Score: 1

      Laying odds that one comment appearing on /. belonged to a Nobel Prize winner... 3 to 1.

      --
      quis custodiet ipsos custodes
    11. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      /b/ has no point. Stop forcing the meme.

    12. Re:They should ditch comments entirely by Anonymous Coward · · Score: 0

      Youtube comments make even 4chan comments look highly intelligent. 4chan has more trolls, more assholes, and is more disgusting, but youtube manages to beats them at stupidity.

  20. Improved login system? by jrozzi · · Score: 1

    It would be nice if they simply revamped their login system. Right now I have an older "unlinked" google account and every time I try to login with it I get an infinite redirect loop. Yes, I cleared my cookies and the problem occurs on Firefox, Google Chrome, and Internet Explorer. I used to be able to login fine just a few weeks ago. What does it take to get support from YouTube with login troubles? Is anyone else experiencing login issues?

    1. Re:Improved login system? by ais523 · · Score: 1

      I managed to somehow create two Youtube accounts with no password (as in, it prompted me for the username, but never for the password). Kind-of obviously, I can't log into them. In the end, I had to try a different browser (I think Konqueror worked).

      --
      (1)DOCOMEFROM!2~.2'~#1WHILE:1<-"'?.1$.2'~'"':1/.1$.2'~#0"$#65535'"$"'"'&.1$.2'~'#0$#65535'"$#0'~#32767$#1"
  21. Theora and Vorbis bitstreams are frozen by tepples · · Score: 5, Informative

    And changes must be forwards compatible, so that a file encoded in the new format can still be properly played by a browser implementing the minimal version of Ogg, at a similar quality level.

    And in fact, both Theora and Vorbis have bitstream formats that are frozen in just the manner you suggest. Old decoders can decode new streams, even those produced by the newer "Thusnelda" and "AoTuV" encoders.

  22. I have 2 recommendations by GodfatherofSoul · · Score: 1

    First, come up with a way to detect duplicate videos. I'm so tired of thieves recopying videos and siphoning off hits from the original content provider. Second, I'd love for a way to find my past comments. There's currently no way to do this. Yes, there's a lot of idiocy on YouTube but I love browsing videos for laughs and even the commercials have been kept to a respectable limit. People get to post stupid, funny, cute, and creative movies that normally only family members or friends would get to enjoy.

    --
    I swear to God...I swear to God! That is NOT how you treat your human!
    1. Re:I have 2 recommendations by Nimey · · Score: 1

      You did post that to the suggestions page, didn't you?

      Tell me you're not one of those people who piss and moan about bugs on various fora but never submit a bug report.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    2. Re:I have 2 recommendations by GodfatherofSoul · · Score: 1

      You did post your suggestion to my suggestion box didn't you?

      --
      I swear to God...I swear to God! That is NOT how you treat your human!
    3. Re:I have 2 recommendations by Smidge204 · · Score: 1

      Re: Duplicate videos

      If the video is legitimately your creative content, you would be justified in filing a DMCA notice against people who re-upload your content without permission. It's even an option in the web form ("My YouTube video was reuploaded by another user").

      If the video you uploaded is not your property to begin with, or you had no permission to post it, then you're SOL. Whatever right (or lack thereof) you had to post it, they have as well.

      If you're just a third party, then the best you can do is notify the original uploader. It's up to them to enforce their property rights.

      Re: Searching for your own posts

      Yeah, they would be kinda nice... a history of comments would be useful providing it was (at least as an option) kept private.
      =Smidge=

  23. The homepage. by Akira+Kogami · · Score: 5, Insightful

    How about they fix the bloated, slow-to-load youtube.com homepage and replace it with something clean and simple like the Google homepage?

    1. Re:The homepage. by imakemusic · · Score: 1

      Just add youtube to your search bar. It's even faster that way.

      --
      Brain surgery - it's not rocket science!
    2. Re:The homepage. by TheReal_sabret00the · · Score: 1

      Or add a keyword, I seldom use my search bar, all of the useful searches are keyword searches for my address bar: google wiki slang dict youtube

    3. Re:The homepage. by TOGSolid · · Score: 1

      "How about they fix the bloated, slow-to-load youtube.com and replace it with something clean."

      Fixed that for you.
      Youtube has been progressively getting more and more buggy as they keep screwing with it. The only thing on my wishlist for it is that they just fix the damn site. It's gotten so bad that me and a few other friends who do video work are wondering why they even bother having a loading bar on their videos anymore.

    4. Re:The homepage. by Anonymous Coward · · Score: 0

      Check out "Feather". They are advertising it on the main page. It's a minimalist, fast-to-load version of youtube. No Javascript I believe.

    5. Re:The homepage. by Akral · · Score: 1

      They already have that.
      It's called YouTube Feather.

      --
      Don't worry, be happy!
  24. How about a repeat button ? by parallel_prankster · · Score: 1

    So that I can keep playing the same music videos over and over and get to work instead of coming back to youtube every 5minutes and pressing play.

  25. Stop being basement nerds by Mr_Plattz · · Score: 2, Insightful

    After going to vote, it's extremely obvious that slashdot crowd has taken reign over this voting page.

    Can you PLEASE STOP posting specific highly technical changes that the average user will not understand.

    Sure, blabber on about H.6969 decoding formats while you're in your basement with your friends. BUT LISTEN PEOPLE. If you want Google and Youtube to change, and change for the good of the Open Source and Freedom of speed world, lets keep our suggestion to "Use HTML5 for video, not flash". or something similar. The next "please use \this\ codec" I'm going to vote no.

    All I want is to be able to download a free and open source Linux distribution, Install it and watch a video on Youtube. Couldn't care less if it's HTML412.80211g or H.2342333(revision9).

    1. Re:Stop being basement nerds by selven · · Score: 1

      That's the thing. You can't download a free and open source Linux distribution, install it and watch a video on Youtube. For legal reasons that will go away if Youtube switches to Ogg/Theora/Vorbis/HTML5, Ubuntu cannot include the ability to watch YouTube videos in a default installation, you need to download ubuntu-restricted-extras to do that. Many people probably have a text file of sudo apt-get install commands that they copy in and run after every installation, but for the non-technical users you're talking about it's quite a big problem.

    2. Re:Stop being basement nerds by Doug52392 · · Score: 1

      The sad thing is, what the fuck are you going to watch with your fancy HTML5-compliant capitalist copyright Nazi video "sharing" site we call YouTube? The only actual "user-generated" content on that garbage site consists of one-minute "vlogs" from idiots who think they're cool because they say "fuck" "gay" and "faggot" after every word.

    3. Re:Stop being basement nerds by selven · · Score: 1

      Lots of instructional videos and lots of political videos get uploaded on there, and probably a lot more. There's lots of perfectly good original content on Youtube, you just have to filter out the crap.

  26. How about by Anonymous Coward · · Score: 0

    How about a way to contest bullshit Flags on your videos, or better yet, the bullshit Warnings on your account that occured due to not being able to contest bullshit Flaggings? You can get flagged for nudity for showing a bit of sideboob, but it's apparently okay for Columbia Pictures to host Blue Lagoon completely uncensored. Some fucking accountability for YouTube's administration and some CONSISTENCY in how they enforce rules is all I fucking ask for.

  27. Parent is a blatant lie. by serviscope_minor · · Score: 5, Informative

    From OGG theora home page:

    The bitstream format for Theora I was frozen Thursday, 2004 July 1. All bitstreams encoded since that date will remain compatible with future releases.

    Theora 1, like MPEG1, MPEG2, MPEG4, H.263, H.264 and so on is fozen and finished. The bitstream will never change.

    --
    SJW n. One who posts facts.
    1. Re:Parent is a blatant lie. by dangitman · · Score: 1

      Thursday, 2004 July 1

      That's some really fucking weird date formatting. What's up with that?

      --
      ... and then they built the supercollider.
    2. Re:Parent is a blatant lie. by hkmwbz · · Score: 1

      The encoder is frozen, but the decoder was released as 1.1 recently with massive quality improvements over 1.0. Or something like that.

      --
      Clever signature text goes here.
  28. H.263 for playback on downlevel Flash Player by tepples · · Score: 1

    Flash is a native H264 library, and if you don't have it, you aren't using YouTube.

    YouTube still encodes video in H.263 for playback on downlevel Flash Players like the one in Wii's Internet Channel.

    1. Re:H.263 for playback on downlevel Flash Player by RailRide · · Score: 1

      I was under the impression that YouTube was using H.264 for everything since early 2009. I found out about the changeover after I noticed my videos were showing really choppy framerates that weren't present on my pre-2009 videos. The effect was quite noticable since most of my uploads are of model trains (my YT username is the same as here if you want to examine them), and long continuously-moving objects tend to highlight shaky framerates..

      Dinking around on Wikipedia revealed the changeover to H.264, and further searches revealed the consensus that H.264 is considered to be very CPU intensive (I'm using a 2Ghz Celeron laptop running XP). Employing as a basis some early tricks to get stereo sound before YouTube officially supported it), I began encoding my uploads to mimic the previous YouTube format (Flash video with H.263 compression/MP3 audio, and a combined audio/video bitrate under 350KB/s). The results?

      (1) The videos were viewable within a minute or so of upload completion, instead of spending several minutes as "Processing--Please wait".

      (2) The framerate issues are not evident on the uploads using the pre-2009 parameters.

      Although I haven't downloaded those videos to confirm it, this suggests to me that the H.264 conversion was skipped. I don't know how long this tactic will work, but for now, I continue to format new uploads this way.

      ---PCJ

  29. Google using naked video on youtube? I doubt it. by Concern · · Score: 1

    It would also get us the ability to use purely open source software for our web browsing again, or at least for our YouTube -- no need for Flash. It'd also give us the ability to right-click and do something like "save video as", or click+drag a video to our desktop, or email. It'd also greatly simplify anything else which just wants the video -- for example, any sort of set-top box, etc, now only needs a web browser, or even just something that can scrape the YouTube HTML, instead of a web browser and a Flash port.

    Is there a solution for all of Google's overlay features and customer spying- i mean, statistics and market intelligence capabilities, in this scenario you envision?

    I'm assuming anything that prevents i.e. second by second reporting of how much of the video you watch, or current and future in-frame advertising capabilities, is pretty much a non-starter.

    They may not be "evil," but they are in the ad business.

    --
    Tired of Political Trolls? Opt Out!
  30. Re:IMMA CHOKE YOUR DICK WITH MY MOMS by Anonymous Coward · · Score: 0

    Youtube is a byword for horrifyingly stupid and banal comments. The best Youtube comments still make Slashdot seem like a collection of Nobel prizewinners.

    dude u talk leik a fag. get teh fuk of /. bitch. u r fuking cancerz!

  31. Improve performance by jwhitener · · Score: 1

    I don't care what ends up being used as long as it is open source and has improved performance over flash.

    My sister needed a cheap laptop to do some work at home, so without much research, walked into a BestBuy and purchased one. Playing Hulu shows on it is very choppy. Whatever video format is used should at least play smoothly on computers sitting on store shelves, or at least scale well enough to handle a wider range of hardware.

  32. Re:Google using naked video on youtube? I doubt it by SanityInAnarchy · · Score: 1

    Is there a solution for all of Google's overlay features

    What do you mean by this?

    customer spying- i mean, statistics and market intelligence capabilities

    Sure, they assume most people will be watching it through a YouTube page. Even if you only grab the naked video, though, they still get your cookies and your IP.

    I'm assuming anything that prevents i.e. second by second reporting of how much of the video you watch,

    I'm sure they can live without that -- though again, they'd be assuming most people would watch it through the web player.

    or current and future in-frame advertising capabilities,

    You can already avoid all of the above by using a video downloader. You can also avoid them on any website using an adblocker extension -- yet Google says they welcome adblockers, think they are good for the Web.

    And think about it -- if it was really so ludicrous that they'd do this,

    • Why does Gmail allow ad-free IMAP access?
    • Why does YouTube not use any kind of DRM, or at least Adobe's Streaming Server? (Seriously, it's not that hard to download naked videos now.)
    • Why does Google welcome adblockers, despite owning Doubleclick?
    • Why does Google offer many entirely ad-free services? Last I checked, GOOG-411 had no ads, and I doubt there are any on Google Voice.

    As a user, why would I use the HTML version? Simple: First, it's easier for me to remove ads than in the Flash version, if I'm not going to download it. Second, I'm lazy -- much lazier to stream than to download. Third, sometimes the annotations are actually worth reading, or sometimes I want to comment -- all of that's right there, versus having to go find the page again after downloading.

    --
    Don't thank God, thank a doctor!
  33. Re:Google using naked video on youtube? I doubt it by Concern · · Score: 1

    What do you mean by this?

    Words in boxes can be laid over the video for periods of time that the user selects.

    Presumably there are current and future advertising possibilities to this, beyond just allowing users to scribble on their content.

    Sure, they assume most people will be watching it through a YouTube page

    I'm sure they can live without that

    I'm not.

    Youtube currently provides detailed data about the behavior of viewers within the video - including their main interactions with the player. I'm just guessing here, but an open source codec playing a naked video seems highly unlikely to report back to somewhere about how many seconds the viewer watched, or where they hit pause, or what they rewound and watched again.

    Flash will happily do it, and whatever else it's programmed to do. More to the point, virtually every flash player in wide use does do this.

    Advertisers are accustomed to having this information - and they care about it, because they get little other equivalent, fine-grained feedback about how viewers like the content.

    You can already avoid all of the above by using a video downloader.

    Right, but users of those are like linux users - a minority. Small enough to be a rounding error, frankly.

    Google may be wise enough to know that they can't force savvy users to do anything, there is no point in trying, and it doesn't matter anyway.

    Why does Google offer many entirely ad-free services?

    You're saying that google cares so little about ad revenue on what they do that they may ditch flash anyway.

    You may be right. They certainly offer an extraordinary amount of "pro bono" web services.

    Let's make a bet. I think they disappoint everyone on HTML5, and on top of that, you will see them finding more ways to monetize what they currently give away for free.

    The only way I see it going the other way is if HTML5 video had feature parity with Flash. Or Google made it so. Then you might see it adopted on Youtube.

    --
    Tired of Political Trolls? Opt Out!
  34. On the note of content by rdnetto · · Score: 1

    I think it's a shame that the submitter failed to notice that the 2nd most common response was with regard to the DMCA. Apparently a lot of uploaders are unhappy about that fact that their videos get taken down by false DMCA claims. It seems that DMCA and HTML5 form ~90% of suggestions/complaints.

    --
    Most human behaviour can be explained in terms of identity.
  35. YouTube playlists by tepples · · Score: 1

    They already have such a bit of code. It's called a "playlist", as seen here.

  36. Rewrite video to object by tepples · · Score: 1

    they don't provide any framework or support, and in fact work against, any efforts that might be made outside the United States to develop a less-crippled Firefox.

    Because Mozilla frankly doesn't need to. That's the job for an extension that rewrites <video> elements with type video/mp4 in pages into <object> elements that call the built-in QuickTime plug-in for anyone who has iTunes installed. Apple could even include such an extension in the QuickTime plug-in's installer.

  37. Re:Google using naked video on youtube? I doubt it by SanityInAnarchy · · Score: 1

    Words in boxes can be laid over the video for periods of time that the user selects.

    Ah, the annotations. Trivial to do in HTML5.

    Youtube currently provides detailed data about the behavior of viewers within the video - including their main interactions with the player. I'm just guessing here, but an open source codec playing a naked video seems highly unlikely to report back to somewhere about how many seconds the viewer watched,

    Yes, you are obviously just guessing, and you're dead wrong.

    The codec doesn't do the reporting, that's true. Neither does h.264. It's the Flash that does the reporting.

    HTML5 has fairly sophisticated Javascript integration. There's absolutely nothing stopping client-side Javascript from reporting exactly the same statistics back to Google.

    Flash will happily do it, and whatever else it's programmed to do.

    Right. Flash doesn't just magically do this, you have to program it to do so -- just as Google did, and just as they'll do with HTML5.

    More to the point, virtually every flash player in wide use does do this.

    What makes you think Google just picked up a Flash video widget off the shelf? They wrote their own -- which makes the process exactly the same in HTML as it would be in Flash.

    Right, but users of those are like linux users - a minority. Small enough to be a rounding error, frankly.

    Frankly, about the same as you'd get with right-click and save-as -- and more than you think, I would guess. In particular, anyone who "mirrors" a YouTube video, or includes clips of others' YouTube videos in their own, if they do it intelligently, they do it by snatching with something like Video Downloader.

    Google may be wise enough to know that they can't force savvy users to do anything, there is no point in trying, and it doesn't matter anyway.

    Exactly my point.

    You're saying that google cares so little about ad revenue on what they do that they may ditch flash anyway.

    No, I'm saying they get plenty of ad revenue from "normal" users. There's really no reason to think they'd get less by sticking Vorbis in a <video> tag.

    I'm saying that you're right, they don't really care about people using something like a video downloader, so they'll care about as much about the fact that an HTML widget could enable the same thing, only with far less of a kludge.

    Let's make a bet. I think they disappoint everyone on HTML5,

    They already have an HTML5 player. Not a very good one, but it exists.

    and on top of that, you will see them finding more ways to monetize what they currently give away for free.

    Yes, they generally do that, but tastefully, as they realize that if they turn into, oh, ign.com, they'll only drive the adoption of ad blockers. It's in their best interest to not overly annoy users.

    The only way I see it going the other way is if HTML5 video had feature parity with Flash.

    Every single one of the features you mentioned, yes, it does. Combine it with SVG, and the differences become even smaller and more boring.

    --
    Don't thank God, thank a doctor!
  38. Re:Google using naked video on youtube? I doubt it by Concern · · Score: 1

    Ah, the annotations. Trivial to do in HTML5.

    Good to know.

    Yes, you are obviously just guessing, and you're dead wrong.

    OK, that's cool.

    The codec doesn't do the reporting, that's true. Neither does h.264. It's the Flash that does the reporting.

    Duh.

    HTML5 has fairly sophisticated Javascript integration. There's absolutely nothing stopping client-side Javascript from reporting exactly the same statistics back to Google.

    Well OK then.

    What makes you think Google just picked up a Flash video widget off the shelf?

    Nothing.

    There's really no reason to think they'd get less by sticking Vorbis in a tag.

    Certainly not if there's feature parity with the existing solution.

    They already have [youtube.com] an HTML5 player. Not a very good one, but it exists.

    Given what you describe of HTML5's APIs, then we might see more of it after all.

    Every single one of the features you mentioned, yes, it does. Combine it with SVG, and the differences become even smaller and more boring.

    Actually this sounds quite nice; you've got me interested to the point where I'll be giving HTML5 a much closer look. I hope you can forgive me for being shocked that the standards bodies had anything so substantial or useful up their sleeves. If the browser itself can finally out-Flash Flash, and we can finally kick that buggy pile of crap to the curb, then the next round of drinks is on me.

    Then again, even if MS can't think of a good reason not to implement the standard, won't they still make IE incompatible just out of spite?

    --
    Tired of Political Trolls? Opt Out!