Still, I prefer to follow Hanlon's razor, and not assume malice. This kind of mistake always seem obvious in hindsight, but if it was, why was there no one warning about it at the time?
177 karma · joined September 8, 2018
Still, I prefer to follow Hanlon's razor, and not assume malice. This kind of mistake always seem obvious in hindsight, but if it was, why was there no one warning about it at the time?
That said, uMatrix, from what I remember, uses the webRequest api which does work from urls. So if you know JS, you can always create an extension and add your own filter.
e.g. from what I remember, when installing xfce in debian, you get the ugly barebones defaults from upstream. Compare this to Xubuntu...
From: https://developers.google.com/speed/webp/faq (Why not simply support WebM in <img>?)
WebM uses more memory, it is less widely supported, uses more resources when playing, and is currently less efficient compression-wise than WebP.
About FLIF, I was recently checking it and it's indeed a very interesting format. Notably because it can be used on any type of image. I assume it hasn't pickep up steam because it doesn't have the backing of any big sponsor. Google is pushing WebP, and introducing another format at this time is probably not worth it.
Keep in mind, I don't deny that the military can find uses for what the article describes. But, to go from this, to deliberately provoking WW3 by massively launching such a weapon on China is suicide. It would provoke a counter-attack, guaranteed, no matter the political arguments.
Plausible deniability is fine when the targeted countries can't counter-attack, or the matter is relatively minor. But, directly against China and with world-ending repercussions? No way.
Within 6 months, a country with nuclear weapons is forced in a desperate situation. What could go wrong?
Is there really a point to such a scenario between nuclear powers? It doesn't make much sense to me. The US might as well launch all its warheads from the start.
They all have Linux distros, sponsored nationally.
https://en.wikipedia.org/wiki/Category:State-sponsored_Linux...
_If_ Boeing really is behind all this, they may well be unaware of the specific details, sure. But so what? This doesn't make them any less responsible. So I don't understand what makes this "worse".
> Three senior insiders at Apple say that in the summer of 2015, it, too, found malicious chips on Supermicro motherboards. Apple severed ties with Supermicro the following year, for what it described as unrelated reasons.
And then as an "unrelated and relatively minor security incident" later on.
Doesn't seem the case to me. The majority of BBC submissions, even by the OP, sit only at a few points.
And about how Chrome got a foothold in the first place, I distinctly remember Google agressively advertising their own product on their search engine page, and bundling the binary with everything under the sun (Adobe Reader, anti-virus, etc...). Every time you installed software, there was a good chance Chrome was included with it. Tech influencers had their part in the success of Chrome, but it definitely wasn't the only factor, or maybe even the most important one.
It's obvious really, and Google never denied it.
HN isn't representative of most users of Chrome. I doubt that we qualify as "a lot" to Google. An extremely vocal minority, at best.
Qt widgets look close to native UIs but the feel isn't always the same, especially when you have to juggle with different platforms (all native widgets differ in subtle ways even when their function is the same).
https://perens.com/2017/06/28/warning-grsecurity-potential-c...
For a civilization to survive and be qualified as being advanced, not only implies being smart enough to develop some technology but smart enough to know when NOT to use it. e.g.: let's not use nuclear warheads, let's not use grey goo, let's not communicate with possibly agressive alien civilizations.
And what if the publishers break into your home and are the ones to scratch the DVD? That reflects better what happened in the article.