Zizzle

Even if these extensions are being used I'm sure the attack surface of X11, it's extensions and it's drivers is large enough to make it trivial to breach. Even compared to a modern browser like Chrome.

I wish they would throw a dialog or interstitial that would let people know about it.

The more people asking why they have a "reduced quality" video in 2016 despite paying $90 for their phone plan the better.

Dick Clarke has been saying the same.

> Clarke explained that the FBI was trying to get the courts to essentially compel speech from Apple with the All Writs Act. "This is a case where the federal government using a 1789 law trying to compel speech. What the FBI is trying to do is make code-writers at Apple, to make them write code that they do not want to write that will make their systems less secure," he said. "Compelling them to write code. And the courts have ruled in the past that computer code is speech."

http://arstechnica.com/tech-policy/2016/03/former-cyber-czar...

"During his testimony today, Comey dismissed the notion that Apple’s assistance in the San Bernardino case would impact other phones, reiterating his belief that any code Apple created to help in this case would only work on Farook’s phone."

And that belief is based on what exactly?

Apple has being saying the opposite. Apple doesn't know it's own code? FBI knows it better.

I recently put a turbo on my van since I live high in the mountains where the atmospheric pressure is low and the performance loss is noticeable.

Of course the ECU needs adjustments to the fuelling tables (you need to run rich under boost to prevent detonation), spark timing tables, as well as a patch to the OS to allow the use of a different manifold pressure sensor (default OS doesn't recognise press above 100kpa).

I guess this was illegal.

I have heard rumblings from the professional engine tuners that the OEMs are already starting to lock down ECUs. Not only via DRM, but by having enough checks in the code that modifying parameters to up performance results in error codes and limp home mode. They expect to be having to go to after market ECUs soon.

Some of them would have cost more than my whole project:

https://www.holley.com/products/fuel_systems/fuel_injection/...

Fortunately there are more DIY friendly set ups:

http://megasquirt.info/products/diy-kits/

But it seems a waste to have to throw away a perfectly good ECU because the OEM (or gov) decided to lock it down.

I'm a bit worried that these stories floating around about title 2 being imminent will give the monopolies time to throw more money at the problem to make it go away.

i.e. "convince" Wheeler or get congress to pass a bill.

Or it could be a ploy by Wheeler. Make noise about full regulation, then make the carriers think they have won some concession when he negotiates and implements something lesser.

I foresee an arms race here.

Next gen FTDI clones will work around this driver detection. Next FTDI driver has new detection code.

Iterate until the counterfeit chips are indistinguishable from the real thing via software.

It also seems like a task with inherent parallelism.

Upload the corpus and throw a bunch of cloud instances at it.

Why leave out PostgreSQL?

Exactly.

It's not like the ISPs and making a profit. They are extremely profitable and just want more.

Makes me wonder how much this discussion is being atrsoturfed.

The ISP are already massively profitable.

The data caps are artificial scarcity to create even more profit or drive people to their own video providers.

Cities have decided to only allow 2 sets of cables to everyones house (and the FCC decided not to make them share between providers) so there is a defacto duopoly - competition is nearly non-existant.

Hence they know they can get away with double and triple dipping. Nexflix has to pay more - guess who they pass it on to?

But in the 80s and 90s they weren't heading towards big iron.

It was the opposite. 1.5 litre engines with a lot of boost making more horsepower than they do now.