That Google gets you developer questions such CSS properties being used incorrectly or CDNs not issuing cross domain headers. Which is easily fixable by the web site developers / sysadmins and thus isn't remotely the same thing as the web browsers themselves not supporting @font-face.
There's a great many subjects I'm ignorant on, but I do know what I'm talking about here. So you're wasting your time trying to prove that I was wrong about @font-face.
The joke point you made at least makes some sense - even if I personally think it's a petty reason on its own. But everyones judgement will differ. :)
Anyway, your original comment was judged by the community to not be contributing to the conversation when you expanded or whatever you call it. So downvotes. No big deal.