To view parent comment, click here.
To read all comments associated with this story, please click here.
Because unlike companies I’m not being paid to do this and my time is extremely limited. I work an insane amount of hours sometimes and I spend my day off doing the podcast. Uploading the files is slow, and using the back end to write and publish the podcast is also slow and clumsy. Producing an OGG alternative would add an hour to the turnaround time, and I’m not willing to add that when there simply isn’t the practical demand yet (I’ve yet to hear someone who physically has no access to any device capable of playing MP3), and that I will get the server to transcode and publish OGG with the OSn5 rewrite.
"Web developers, the choice is yours. Are you ignorant and short-sighted, or are you willing to make a stand for keeping the web open, and finally breaking video loose from its proprietary shackles?"
Sound familiar? I understand that you are volunteering and that time is limited but OSNews looks like its being run by hypocrites when rants are published about other websites using proprietary formats despite the fact the OSNews continues to do the same.
If time is short and you don't have time for both, why not publish Ogg Vorbis only? If you want to give users a cleaner way to transcode to something else you could publish FLAC only. It's getting tiresome to read the several articles dealing with Youtube ignoring patents when OSNews does the same.





Member since:
2008-07-15
Funny, but I can't shake how very similar that statement is to some of the reasons put out by big companies to stay with H.264. How exactly does creating an ogg file greatly increase your work load? It's simple enough to transcode and it's not as though it takes that long. Better yet just save as aiff (you use Garageband) and make an mp3 and an ogg from the same source material.