-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 03/24/2014 08:23 AM, Werner Almesberger wrote: > > Does Chrome really not support Ogg or is it just a configuration > issue on Ron's side ? Would seem rather petty of Google to do > that. > *** I think ChromeOS does not come with Ogg support by default. WebM is the in-house "open-source", so why support diversity? That adds complexity you know...
> > [1] > http://security.stackexchange.com/questions/26049/chrome-ssl-warning-you-cannot-proceed-because-the-website-operator-has-request > *** Aha! Funky. A self-signed wildcard certificate + Strict Transport Security triggers an Easter Egg :) == hk -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQJ8BAEBCgBmBQJTMCGWXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0 ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg9i1EQALW/xemQINjzGuczxaAf0kh/ ah14JWodhi1H7BWnWUJuhqrE7ehZhJ1yG3hrc7E0fuZtChOszBs5M+bBlsL2TPsO Gnr5bd7zpLoVxtPp21BFZzHGhnIoeOx51n4Udh3iWS35/YFNiMk0BwNVEQxs5bQc QAJqF7ejE4sS6OuPxKmC1g8gwa7RkcInJ+Xutf4yLvOLsDAN4qx5Y6hWfo6LAmmv TCuMnYs/pYmMNLcsWAyGjNvLkzsx4aJODWNa/H/AigvuvOdVgxTdur20qmznVrur Pa0MCbwc4y/KLlUzMqb+04t08nb7mtLmZlL6uvLHN9ReLXB4lngbaMG5YCpRhbyy tfLetX9fcAtGiHfMJIxTi1Eh6zuXUEoQ4sYSiLHfsMjlBfLE3n1VZ8OQBGSggDV1 bhOqRqynXqL6D+AhzNwqhcY3Epi/Yhplxe0ZWKFn1SJx2usp2YCfEukk8L17M4Fd 9c0B0EyQEWITDKBxW2NyE3L5/aPW7d0/AfPnWRx8T7nyRKltCV1nm5ReAHeTmMMG 4Z3hKkAiBG2QQfXa2JDVveeUmdpThz8uC8534hlJth5pP53OHManOary6+XoNJK9 nBtLOtHprZ2bxlGOZeSlLkaW7MIOtiMtxLHuOUcwstmY9HnWT3Q4YsWTMGqInFEU 94RBhlpaJu878uN8GiFb =3Mbh -----END PGP SIGNATURE----- _______________________________________________ Qi Hardware Discussion List Mail to list (members only): [email protected] Subscribe or Unsubscribe: http://lists.en.qi-hardware.com/mailman/listinfo/discussion
