Ars Technica has been on a lowest-common-denominator kick as of late. Titles like this get more pageviews.
They've been fairly vocal in forums and random discussions about how page views are what's most important to them (when people complained about the site redesign the answer was invariably "page views are going up so it must be working").
So I think that's the direction they're heading in. Changing the format of the slug to be shorter and snappier improves page views. Following Kim Dotcom stories, holding reverence for anonymous and being pro-piracy gets them page views.
I do wish them all the best, and they are a business, but I do wish they were more interested in pleasing their '10,000 fans' deeply instead of everyone shallowly, since it's so hard to find that kind of thing these days.
(disclaimer, I used to pay money for Ars until the site design. Now I check it every day but read about a 10th of the articles I used to. Sad times.)
A difference of opinion isn't always pandering. (I find those stories pretty interesting actually, and I've been reading them for a long time too.)
Don't expose services to the internet that you're not willing to make public. Duh? What I got from this article is that some devices that people connect to the internet are configured poorly, probably came out of the box like that, and that maybe I should go double check that my router isn't misbehaving. Note that they have lists of vulnerable devices at the end of the paper, which I'll link here.
libupnp: https://docs.google.com/spreadsheet/ccc?key=0ApUaRDtAei07dFd...
miniupnp: https://docs.google.com/spreadsheet/ccc?key=0ApUaRDtAei07dDh...
soapapi: https://docs.google.com/spreadsheet/ccc?key=0ApUaRDtAei07dGx...
The discussion of libupnp is kind of terrifying on its own: "There are no less than seven unique buffer overflows in version 1.3.1 of this code." Which sounds pretty bad until you notice that by "this code" they're referring to a single function.
The paper itself is much better than the Ars article, by the way.