Well said. You saved me the trouble of writing a comment not half so clear and complete.
Ask professional drivers. These "ethical" questions are ridiculous. Avoid obstacles if possible; if not, slow down. It's better to crash into something you can't avoid as slowly as possible. It's also best to maintain control just in case the situation changes.
So, what are you going to use for ID?
So, in that atmosphere, how any single website would ever be able to "authenticate" your ID, I have no idea.
How about tamper-resistant cryptographic biometric devices? Use your government-issued fingerprint reader to log into Big Brother's system, then each server is required to make sure you have a valid current login certificate from BB before providing any services. Complete records must be kept indefinitely and will be audited against upstream connection logs.
Nobody is required to have government ID, but network service providers are prohibited from communicating over the Internet with anybody who isn't logged in with Big Brother.
Obviously this only works within one jurisdiction. Foreign Internet users would have to be handled separately, if at all.
I guess it would be easiest to manage this at the ISP level -- ISPs would be required to require proof of identity (via secure biometric reader) at regular intervals from all users. Then you don't necessarily have to bother auditing web, email, etc, servers.
It probably means that the maximum possible lifetime energy production of a photovoltaic panel is less than the energy required to manufacture and deploy it.
I have no idea whether that is true, but I believe it is GP's meaning.
IMO, if ads stopped across all internet sites, or the online advertising industry completely collapsed. The internet as we know it, would be gone.
Correction: The Internet as you know it would be gone. The actual Internet would be just fine. Universities, stores, hobby sites, government, and people generally interested in communicating with each other would pay their ISP bills and continue without interruption.
Turing's imitation game was a thought experiment. To explain it simply to an audience unfamiliar with the idea, he started with man against woman, then proceded to man against machine. The specific genders were not important or significant in the thought experiment, just the existence of some difference between the contestants that could potentially be spoofed over a teletype. There was nothing gender-specific or weird about it.
That is always true. The longer you wait, the cheaper it gets. If you wait forever, it costs nothing.
If you need a job done now then get the cheapest equipment that can do the job. If you don't need it now then wait; the price of computer equipment only goes down.
Conversely, the people who *do* have access to the bigger picture stuff, have no vested interest in giving us the unfiltered truth (or any truth at all),
Of course not. If we knew everything they know, then they wouldn't be special any more.
There's nothing in TFA that hasn't been speculated in great detail already.
No explanation totally makes sense. Here's my working model of what happened (all speculation of course):
The project has been gradually disintegrating over the last few years -- developers leaving and not being replaced, remaining developers having less time to spend on the project for whatever reason, and the perceived reward for fixing increasingly difficult bugs is not enough to keep people interested. It's just not fun any more.
The to-do list has some really nasty bugs that are difficult to fix and could potentially compromise all TC containers. The remaining developers in the project have been grinding away at these bugs, but haven't made much progress for reasons outlined above. They realized that the project was going to fizzle out before they got anything fixed. A cursory look at the 7.2 code suggests that they had committed to some major rewriting of the code, and bit off more than they could chew.
At this point, what can they do? Reporting the vulnerabilities would be irresponsible since no fixes are forthcoming. Lives depend on some of the secrets their software keeps. Best to push people gently away from TC until the problems can be fixed, if ever, while keeping the details of the vulnerabilities as secret as possible, and giving people realistic expectations about the future of TC development (i.e. none).
They probably had a plan for creating a migration plan that actually made sense, but ran out of resources before finishing, and decided to go with what they had on hand. At this point they were probably down to one very part-time developer and maybe a few unreliable volunteers. ("Hey Jim, where's that page you were writing about Linux FDE? Jim? Hello? Anybody there?")
There was really no good way forward with the resources remaining, so they did the best they could.
Why didn't they find someone else to take over the project? I guess they tried, but couldn't find anyone in their immediate circle of trust who was willing and able. Perhaps they felt that expanding their circle of trust would jeopardize their anonymity.
On the other hand....
"WARNING: Using TrueCrypt is *not *secure *as
Reading Rainbow is an American children's television series that aired on PBS from June 6, 1983, until November 10, 2006, that encouraged reading by children. As of 2012, it is an iPad and Kindle Fire educational interactive book reading and video field trip app.
Remember that Edward Snowden was a contractor with Booz Allen Hamilton, and has proven to the world his unimaginable and extraordinary access to the most senstive of NSA programs --- and who owns Booz Allen?
I give up. Who owns Booz Allen?
When it is incorrect, it is, at least *authoritatively* incorrect. -- Hitchiker's Guide To The Galaxy