No. That is not how it works. The truth is that the smaller provider pays the larger provider, no matter which direction the traffic flows. Some companies, like Netflix, are nice enough to not use their size as an excuse to charge people -- they offer free peering at internet exchanges. Other companies are maximally greedy.

Netflix limited the highest bandwidth streams to direct peers for a while. Everyone going through transit could not get the highest quality.

Similarly, it would be quite trivial for Netflix to limit non-paying ISPs to lower quality.

We are talking about ODF here. The encoding will be UTF-8.

ASCII is a subset of UTF-8-encoded Unicode. If you do not use anything beyond ASCII in your document, the unzipped file will only contain ASCII. If you put Korean characters into your document (and you do not have to change font to do so, if you are using a decent font), the unzipped file will contain non-ASCII characters. In both cases, the file will be a valid UTF-8-encoded Unicode XML document.

That would explain why the HP site is so ridiculously slow. Except that it has been slow for years, but maybe they were always running it on prototypes.

I give you SAS flight 751. Both engines out, no power to the instruments. "Landed" using the windows and a mechanical artificial horizon. No fatalities (but a few severe injuries, unfortunately).

Not anymore. Practically everyone implements the privacy extensions, and most do not generate a MAC-based IPv6 address at all.

It's great that you foresaw it all. That does not really have anything to do with what I wrote.

Obama seems to be the first mainstream US presidential candidate in a long time to "talk the talk" to the kind of people who read Slashdot. The others have been spouting ignorant crap or simply ignoring the topics that most Slashdotters care about. Therefore Obama is the first president that we can be disappointed in -- the others were known bad before they became presidents.

File system drivers in general are not properly security vetted. You can do interesting stuff to a Linux box if you put ext4 on a fake device and start messing with what is on the disk while it is being read. Many device drivers have similar problems; you could find a Linux device driver with a problem and make a fake piece of hardware resembling the real thing while exploiting the bug.

This is pretty much unfixable. While most core OS code is of a high quality these days, there is just too much driver code around. A proper audit is infeasible.

Besides, Thunderbolt makes it pointless. With Thunderbolt, you do not need to exploit anything, the bus provides you with unlimited access.

It is a sad state of affairs really.

Name one. E.g. the BMW i3 has absolutely horrendously bad mileage on gas, and practically everything else is a parallel hybrid, not a serial.

"Memory allocation is too important to leave to the programmer" vs. "memory allocation is too important to leave to the system". Also, emacs vs. vi.