I know that opera relies on its own libffmpeg.so to play html5 stuff like mp3, mpeg4, h264/5, webm, aac, ogg etc and, due to licence reasons, it can not play many popular ones (mp3, h264/5 etc) as seen on html5test.com. This is what causes problems on sites like twitter, facebook, soundcloud etc and, in turn, complaints from the users.
If the user is lucky to use a distro like ubuntu which packages chromium-codecs-ffmpeg, he installs them and opera uses that libffmpeg.so and automatically gets better html5 support.
What if he is unlucky like me on debian, which does not package chromium-codecs-ffmpeg and relies on libavcodec(-extra), libavformat and libavutil to provide the needed html5 support for chromium and chromium based browsers? Opera can not detect these libs, so it can not use them, so opera on debian is stuck with that poor html5 support.
And no, I will not risk breaking my system by installing the chromium-codecs-ffmpeg from ubuntu, let alone the stuff on herecura's repo which is actually a repo for arch linux! In fact, why would someone install/use a lib compiled for a different distro and definitely built with different libs/dependencies?
Does the "--ffmpeg-preload-mode=permissive" command line parameter, mentioned on the blog post, work on opera stable? I could try it...
Finally, disabling youtube's webm support by installing h264ify will be useful only if opera already has h264 support, which means chromium-codecs-ffmpeg must be installed beforehand. Else, you just chop youtube's webm support on a browser that does not support h264 and you end up with a browser that has the html5 capabilities of internet explorer, if not less.
