Linked by Kroc Camen on Thu 28th Jan 2010 17:29 UTC
Permalink for comment 406511
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-11-10
Bingo. You can guess what I'll be doing 2011—removing the MP4s.
I made VfE specifically for the other websites I visit to provide me a means to view their content, including those willing to pay the H.264 licence in the future.
It’s pragmatic, rather than political—so sue me
edit And—I expect people reading the code to be smart enough to make their own decisions. You can’t blame me for developers who decide to encode H.264s. That’s their choice, their actions and nobody else’s.
VfE exists for occasions just like when Loading Ready Run moved to the Escapist, and now, I can’t view their videos any more because they are hidden behind a Flash player instead of QuickTime or YouTube which they used before. The Escapist are already using H.264 files for Flash—I can’t make them make that decision already—but I do wish they were using VfE so that I could _access_ those H.264 files.
The H.264 onus is on the publisher—not on the viewer and that’s the big difference when it comes to the codec issue (where it used to be the onus of the viewer to go get the right app quicktime/real/wmp &c.)
Edited 2010-01-28 19:46 UTC