GMT died in 1972, so can we put this to bed already please?

Do you think generalizing about the inhabitants of a country of 320 million people/10 million km2 will help the problem?

Made a pretty good datacenter too. Already had a loading dock, concrete slab floor, & plenty of HVAC installation points.

Sorry to rain on your parade, but multipath TCP already does this...

n/t

Exactly. That's one of Schneier's central arguments as to why sites getting "hacked" is so prevalent today. Once some initial security perimeter (e.g. a firewall) is breached, system design & security is sloppy enough that it's a free-for-all for the intruders. If systems were designed as a fortress built to secure data this would be a lot less of an issue, as unsuccessful crackers are broke crackers that need to start looking for income elsewhere.

Was the trial held in Tampere?

ba-dum-cha

Sorry, couldn't resist...

And easily crackable...

Torque is all the OBDII goodness I need, along with an ELM327 dongle from Amazon.

Because your home network isn't plugged into $100K+ routers with the military's availability SLAs.

There's nothing wrong with copper or its age. You're too far from the CO.

If competitive carriers like CenturyLink had access to facilities that THE PUBLIC PAID FOR that now belong to Verizon et. al. they could put gear in the patch cabinets much closer to their subscribers (this is known as FTTC). In the UK there are several carriers using VDSL2 technology to provide 80mbps down/20mbps up service over "ancient copper" for a little more than the price of a normal DSL line, because their gear is only 300m from the subscriber in the neighborhood patch cabinet.

But the US Congress repealed the legislation requiring incumbents to allow acces to their facilities in 2005, so the end result is that the broadband situation in the US for most folks is:
  - Incumbent DSL that isn't faster than it was 10 years ago
  - Cable
  - If you're very lucky, fibre

NoScript does the trick pretty nicely too...

n/t

Maybe it's because a whole lot of people don't want to screw around with a full-blown PC anymore & just get on with doing what they need to do instead of fighting with Windows Update & malware all the time.

Including our CEO, who does all his work on the road with...

a 10" iPad.

Personally, I'm lazy. I've been using Pine (now Alpine) directly on a mail server for all my mail since 1995 (on my own servers since '97). Old habits die hard.

It works great over really low bandwidth connections (though sometimes high latency can be annoying), you can view any attachments you need automagically with X11 forwarding via SSH, and you don't care at all about which machine you're accessing it from. Also you get to read the TEXT in your mails & not HTML, most of which is useless garbage when it comes to emails (for the 0.1% of HTML mail I do actually need to read as HTML, such as tables, Linx often gets the job done, & if not I just bounce it to my gmail account, which is pretty much full of spam otherwise).

When various folders get Too Big (or I move on to another job, or whatever) I move them into an "archive" folder (& I have an "old-archive" folder for the really ancient stuff) and bzip2 them. I archive my inbox files at the beginning of every year too. When I need to find something old, I just bzgrep for it. After an archiving session (which takes all of 5 minutes) the whole thing gets backed up from my mail server to my NAS at home.

Did I mention that my backup MX is a SparcStation 20 and still works just fine for all this? Of course I don't keep much on it but if my main server dies I can still send & receive mail just fine.

Note that this is not exactly something I sat down & spent time thinking about, I just started moving mail out of the way like this when I left college & built a couple of OpenBSD mail & DNS servers, and kept doing it as it works well enough.