Seems that would be redundant with the Department Of Homeland Security's Office of Cybersecurity and Communications: http://www.dhs.gov/office-cybe...

Or I guess it could also mean "the guy who made the comments was never permitted to know the details of how much access he had".

Back in May they already said Snowden didn't have access to all that data: https://www.techdirt.com/artic...

Not quite irrelevant.

Microsoft probably sells Skype data to some law enforcement and intel agencies but not to others.

If it replaced it, I could almost be OK with it.

The problem is that it didn't - so for half the stuff you have man pages (with pretty good see-also sections); and for the other half the stuff you have info pages; and suddently you have to do twice the work to find anything.

Better search technology could help that one.

I rather the distributions stay away from this -- or at most just passed whatever documentation they do add to the upstream projects.

IMHO the biggest *problem* now is that you often have to got to Red Hat's manuals, or to Arch's or Ubuntu's wiki, or to Gentoo's mailing list, etc. to find documentation to anything.

Seems like that means you have a half-dozen competing efforts that all are re-envengint the same documentation; and since many of those distros are commercial enterprises, are motivated not to share and to paywall off their investment. Ugh.

I think that's *half* of where the problem started.

The second half is when various Linux distros started writing their "own" documentation, rather than contributing back to the upstream projects.

Once documentation fragmented like that; every damn blogger started trying to make documentation "his" to preserve his own page-rank; and a bunch of commercial Question/Answer sites saw the business opportunity of trying to own the documentation for themselves.

Once all those were in place -- it seems most of the efforts moved away from contributing documentation back to the source projects, and moved towards commercializing and monitizing "answers" - which is only profitable when the documentation doesn't keep up.

Sad.

Now if only they would push such information to the upstream projects we'd be getting somewhere. Otherwise, that's just one more set of web-pages that needs to be checked.

Pretty annoying if the best way to find out about an application is to have to check the Yggdrasil archives, the Slackware web page archives, the Caldera docs, archives of the Mandrake web pages, Knoppix blogs, etc.

Interesting project because they're very strict about requiring correct documentation (and regression tests) for even minor patches that random users contribute, before they even consider them.

I think Unix (not just BSD, but I include BSD-based SunOS 4.x) documentation from the mid 90's was the best and easiest to follow.

The main thing I miss from that era is that practically everything I wanted to know could be looked up in man pages; and if not on that first man page I tried, in a meaningful see-also page.

These days, seems most software (not just Linux, but for any platform) is scattered amongst HTML-urls that point to long-gone former websites, and youtube tutorial videos.

Now you might say that much of today's software is too complex to describe in a man page --- but IMHO - that's the bigger problem. If people write complex monolithic bloat, writing pretty documentation for it is the least of our problems.

The entire point of the research is to learn enough to be able to stop an outbreak in a major US city if one were to start.

Why do you seem to be advocating not doing such research?

I agree, but T-Mobile is doing great because they don't *want* to be left alone. They are being so aggressive with their pricing because they want to be targetted for a buy-out. Their parent company, Deutsche Telekom AG, has made it clear that they want out of that business.

Hard to tell who "them" is.

It's being used by, and trying to be hacked by, many groups.

University researchers, governments, MPAA/RIAA, computer security companies, etc.

Seems the project should encourage as many people as possible attempting to hack it -- because that increases the odds that when people finds a hack, at least some of them will report the weakness back to the project.

On the other hand, if the project discourages hacking attempts, only malicious groups will find the hacks.

Don't be mistaken, they are a just a lion in a den of other lions. They are all literally fighting over sticks and stones: holy sites. If it were at least Oil we could at least say they were fighting over resources, but that region is obsessed with killing each other over ancient, probably historically inaccurate, vendettas and magical piles of dirt. It is a region of unstoppable forces and immovable objects. This is what happens when they meet - violence and destruction of everything except themselves.

If they just unlocked the bootloader on the rest of their phones and encouraged people to download and try Tizen on their formerly-android phones, it could grow the ecosystem fast. Just market it as a "now with no google spyware" phone, and I think many will go for it.