[22:24] <BUGabundo> yoooooooo
[22:24] <BUGabundo> fta: so what's happening with x264?
[22:24] <fta> BUGabundo, read my blog?
[22:25] <BUGabundo> not yet
[22:25] <BUGabundo> only the post on stats
[22:25] <BUGabundo> but I read segphault post
[22:28] <fta> pff
[22:29] <BUGabundo> lol
[22:29] <BUGabundo> link me yours
[22:29] <BUGabundo> or explain in 160 chars :)
[22:30] <fta> it's on planet
[22:30] <BUGabundo> I stop reading planets
[22:31] <fta> BUGabundo, http://ftagada.wordpress.com/2011/01/11/h-264-codec-to-be-dropped-from-chromechromium-html5-video-tag/
[22:32] <BUGabundo> thank you
[22:33] <fta> BUGabundo, btw, i also dented about it before segphault ;)
[22:33] <BUGabundo> I just got online
[23:11] <BUGabundo> fta: afais its not an "user" problem
[23:12] <BUGabundo> dropping a format affects more the producers of content
[23:12] <BUGabundo> then users
[23:15] <JanC> fta: I guess it also means a lot less to pay for Google if they can drop h.246  ;)
[23:15] <JanC> especially considering among those to pay to are Microsoft & Apple AFAIK
[23:40] <fta> JanC, yep, that too
[23:40] <fta> BUGabundo, youtube is the most probably the biggest of all
[23:50] <JanC> fta: I like people in the comments saying things like "we encode 40+ hours of video a *day* to deliver on the web.... no way thats happening with webM."
[23:51]  * JanC thinks Google has about the same to encode every minute or so
[23:51] <BUGabundo> yeah
[23:51] <BUGabundo> they say 35h+
[23:51] <BUGabundo> used to be 24 one year ago