You haven't addressed the actual point. Which was that we shouldn't need to think about whether any particular comic is or is not of interest to people carrying out surveillance.
I don't know if some present or future government could be offended by people reading this comic but it shouldn't be a question we even need to ask. If you want to live in a world where surveillance is not the default then the very least you can do is remove the tracking from your own websites.
Thus I applaud the author of this website. And I'm really bored of the dullards who chip away at my freedom saying "but it's only a tiny transgression, what does it matter?"
To give one example: Windows Explorer has been extensible since Windows 95. That was 21 years ago. Dropbox has to pull nasty hacks to integrate with the macOS Finder [1]. That's now.
This is basically national security letters with oversight. Which is part of the problem. When any of the major democracies introduces a law like this, it normalises it for the rest. Which then gives encouragement to the more oppressive countries. The whole world seems to be in a race to the bottom.
This is kind of what LINQ does. You write a query in C#. The structure of the query (like an abstract syntax tree) can be exposed to the query provider which can interpret it or compile it to the CLR or compile it to SQL or whatever.
An HSM consists of some secure memory to store a secret and a program, and a processor to run the program to perform computations using the secret.
A Yubikey consists of some secure memory to store a secret and a program, and a processor to run the program to perform computations using the secret.
The programs are different but they are basically the same thing. The author wonders why there isn't a simple general purpose gadget you can load your own program on to. As long as the action of loading a program clears existing secrets, the device could be secure.
Or to put it another way, consider a Raspberry Pi acting as a router and as a Raspberry Pi acting as a media streamer. They have completely different purposes, but they are the same thing.
But in every company I've worked for mail is signed for by whoever and, if it's addressed to an executive, delivered to a secretary who reads it and decides what to do it.
Given the requirement for secrecy, there is zero chance that an NSL will be treated in this way. And it won't be served by a random process server. Most likely it will be served by an NSA employee, in a discreet situation of their choosing.
The long forgotten irony in this meme is that cars used to be designed like this. There were no seat belts and the steering column was a rigid spear. It was practically designed to kill you.
Historical evidence suggests that there would indeed be fewer accidents but more car drivers would die (because even quite trivial bumps would be fatal), though pedestrians and cyclists would be safer. As someone who chooses not to drive, that sounds pretty good to me.
This isn't theoretical, I've seen it with HTTP, HTML and elsewhere. Any time two pieces of software disagree on how to parse a chunk of data, especially if one of them is supposed to be doing some sort of security check, you should expect to find a vulnerability lurking.
I don't know if there's a name for this class of problem. I'd be interested to know.
Water pipes often accumulate a layer of sediment at the bottom. Anything that stirs it up will cause brief discolouration of the water. Your pipes may be fine. (That said, I wouldn't drink the water right now.)
You don't need a pause button on all the videos. You just need a single button that pauses all the videos. I would be delighted if the escape key on my laptop served this purpose.
Of course, now you have no UI no restart a particular video. But the advertisers would figure this out about 30s after a global pause feature was introduced.
Early RISC processors read data from memory 32 bits (4 bytes) at a time, and these reads had to be aligned on 4-byte boundaries. This was a feature of the memory architecture, not just the processor.
Thus an aligned read of a 32-bit integer took one memory access; an unaligned read took two, which took twice as long. This killed performance.
Rather than quietly performing badly, the processor threw an exception to encourage you to fix your code.
The ARM2 worked a bit differently. It ignored the bottom two bits of the address when it read a value from memory. When the read was complete the value was rotated by the value of the bottom 2 bits multiplied by 8. This had the effect of putting the byte referenced by the full address in the bottom 8 bits of the 32-bit register. A flag in the instruction let you optionally mask off the top 24 bits to simulate a byte read.
I have to use two passwords to login to Lloyds bank. One conventional password (which is presumably stored salted and hashed) and one where I have to enter characters from three positions they choose. The latter is intended to mitigate the risk of using your account from a vulnerable computer. The former takes care of vulnerabilities on their end (as far as any password can).