Talk:Firefox3/PRD: Difference between revisions

Talk:Firefox3/PRD (view source)

Revision as of 13:14, 13 January 2007

1 byte added , 13 January 2007

m

→‎ogg theora/vorbis playback

Concerned User

9

edits

Revision as of 13:14, 13 January 2007 (view source) Concerned User (talk \| contribs) No edit summary ← Older edit		Revision as of 13:14, 13 January 2007 (view source) Concerned User (talk \| contribs) m (→‎ogg theora/vorbis playback) Newer edit →
Line 111:		Line 111:

	It would be great if ogg theora playback made it into Firefox 3 :) ... at the FOMS conference where open media developers meet last Thursday and Friday we identified the inclusion ogg theora into firefox as important goal. [http://www.annodex.org/events/foms2007/Main/CommunityGoals] An early version of liboggplay was demoed at the conference. Liboggplay is a small statically linked ogg theora, vorbis and possibly Speex playback library. I will query about logistics in the newsgroup.		It would be great if ogg theora playback made it into Firefox 3 :) ... at the FOMS conference where open media developers meet last Thursday and Friday we identified the inclusion ogg theora into firefox as important goal. [http://www.annodex.org/events/foms2007/Main/CommunityGoals] An early version of liboggplay was demoed at the conference. Liboggplay is a small statically linked ogg theora, vorbis and possibly Speex playback library. I will query about logistics in the newsgroup.

	Security concerns: Quite frankly, both the ogg theora and ogg vorbis codecs aren't particulary popular. So i'm not sure if adding them is worth exposing the end user to the risk of one of those codecs containing security relevant bugs. As far as i know there haven't been any such bugs found yet in these codecs but i suspect that's mostly because they aren't that popular. What efforts has the ogg team gone through to make sure liboggplay is secure?		Security concerns: Quite frankly, both the ogg theora and ogg vorbis codecs aren't particulary popular. So i'm not sure if adding them is worth exposing the end user to the risk of one of those codecs containing security relevant bugs. As far as i know there haven't been any such bugs found yet in these codecs but i suspect that's mostly because they aren't that popular. What efforts has the ogg team gone through to make sure liboggplay is secure?