Hidden volumes aren't all that great for hiding porn. Generally, porn takes up a large amount of space. Hidden volumes are great for hiding a small amount of data (passwords, launch codes, bank statements, etc) among a large amount; not so great for hiding a large amount of data.
People doing this kind of facilitated communication, had previously written entire sentences, paragraphs, poems, and so on this way. And it was all, as far as the experiments show, the facilitator, not the patient, who was really writing it. Some of the facilitators had no idea; they really thought that it was the patient writing everything, and they were just helping support the patient's hand. A few of them renounced FC after this, realizing it was just them subconsciously writing for the patent, but some continued to persist in their belief that it really was the patient writing despite the strong evidence to the contrary.
Have you never had an experience where you attributed reasoning to a pet's actions? Sometimes we can tell what a pet wants, and so we can reason about what they are doing; sometimes we might be wrong about it. There are plenty of cases where you have a good guess based on other information, like the pet getting hungry at the appropriate time. If you tried doing "facilitated communication" with your pet, and really believed that it worked, you would probably wind up spelling out things like "I'm hungry" when it was hungry; and then take that as evidence that your pet really was writing that, not you.
In fact, this kind of reasoning is used all the time in research that shows that you can teach animals human language, or sign language, or the like. You get researchers who learn a lot about the animal; learn about its attitudes and ways of non-verbally expressing itself. Then they start reading things into the signs or sounds the animal makes, and present it as evidence that they've taught the animal language. But if you do any kind of experiment that takes that particular researcher out of the picture, or provides a reasonable level of blinding, all of that ability goes away, and you hear them talk about how "well, they can't perform under these kinds of stressful situations."
You might think "well, so what, it's at worst something harmless that makes the family feel better." But there have been cases where via facilitated communication, kids (or based on the above research, their facilitators), have accused their parents of sexual assault. Fathers have had to move out of their houses and fight long legal battles on the basis of an accusation that, most likely, was simply made up by prompting of the facilitator. Believing that facilitated communication works without strong evidence that it's the patient and not the facilitator in control can have some serious consequences.
But if you point this out, especially in relation to a feel-good FC story like this one about someone completing college level coursework through FC, you just sound mean and contrary. I would love to believe that advancing technology and therapeutic methods allow people who cannot learn via a conventional methods to have access to knowledge they never would have otherwise. But given the lack of strong evidence that FC really works, these feel-good stories sound more like people just trying to sell more snake-oil than an actual breakthrough.
But Stallman does not believe that making a phone call is evil. Nor does he believe that choosing to allow yourself to be tracked is evil. He objects to being tracked himself. If someone else has already chosen to be tracked, he might think that they made a poor decision, but it's their decision to make. There's nothing wrong with then asking them to use your phone.
This is nothing like asking someone to kill for you. Killing is always wrong. Trading your freedom for being tracked for the ability to make phone calls on the move is a personal decision. Now, he would probably prefer that people not have to make that decision; that phones ran all free software, with no locked hardware that you can't get access to, so you could control your own phone and determine when it did or didn't broadcast. But that doesn't make it wrong for someone else to make a different decision than he did.
Hmm. I can't see how it would be much more dangerous than using a mirror. I ride with a mirror mounted on my glasses, and I glance up at it briefly then back at the road again. The same would be true of the glass. Sure, when you're first getting used to it you will probably linger on it for longer due to the novelty and getting used to the exact focus point. But once you get the hang of it, I can't imagine it would be much different than glancing at a mirror, which is perfectly safe.
The mirror is there to increase your situational awareness while cycling. Glass has a strong potential to do the opposite. If its use is limited to HUD for information useful to you for cycling, fine, but if you're getting text messages or anything else you have to think about, it's distracting.
The Web has DRM, implemented in proprietary plugins: Flash (and to a lesser degree, Silverlight).
And this proposal involves DRM implemented with proprietary plugins (known as CDMs). There is no requirement that CDMs be available across platforms, on open operating systems, available to license by any vendor. The CDMs are the new proprietary plugins, they just happen to do less than Flash, leaving more of it up to the browser.
Is it really so much better to trade one proprietary form of DRM for another? What does that actually get us? More crappy services, where Hollywood decides on a month by month basis which particular services get to offer its content, so you need to sign up for 5 different services just to watch all of the content that you watch? And each one of them supports different set-top boxes, doesn't work on open platforms, and restricts you from backing up media that you have bought?
This isn't improvement; this is just wanting to get browser vendors to implement anti-features that users object to, instead of getting Adobe to do it.
The worst part is that Flash and Java aren't going to go away anytime soon either. You basically have to have both, and the web will be a lot harder to navigate on anything but a Windows machine.
No, you're not screwed. Acquire a useful skill that's in demand and which can be done from a desk: drafting, CAD, graphic design, 3D modeling, video editing, web design, programming. Do that craft, and develop a portfolio of work. Find a non-profit that you like that needs that work and spend some time donating that work to the non-profit so you can have some real world experience in that field, that demonstrates that you can work with other people.
Almost every reasonable hiring manager (which may be a minority of hiring managers, but is still non-zero) will value someone with a good portfolio who's shown that they can get the job done over someone with credentials and years of experience in the industry who doesn't have a good portfolio to show (as someone who's been doing technical hiring recently, I've always wondered about people who apply for a job with 20 years of experience and not a line of code they can show me; I realize that there may be many jobs where you work on proprietary code that you can't show to someone else, but not having a single side project, one-off hack, a few patches to the mailing list of an open source project, or even a former employer you can ask for a code sample to show under NDA in your whole career seems a bit odd).
I already am going for drafting, which includes Autocad and Solidworks. I already am decent at general 3d design (and still have plenty of classes to go).
Still, because I'm past the 6 month employability gap, NOBODY will touch me.
It's actually easier to do "creative career repair" on a 6-month gap than a 4-month one.
Don't get me wrong. You always want to avoid being unemployed for 6 months if possible; but there are ways of touching that up.
If you were in full-time school, just use that. You don't even need to lie. The truth is always better-- not because there's major risk of getting caught, but because it's always better to form relationships based on the truth, and the cognitive load of maintaining a lie will take steam out of you even if you never get caught. The "6-month problem" doesn't include full-time students. If you were a part-time student, maybe you can make it look full-time?
However, if you are stuck needing to lie, I advise the "odds and evens" strategy. Rank your choices 1, ..., N. Odd-numbered choices get full disclosure of the truth. Even-numbered choices get the story you want to tell. (Or, if you think your history is that damaged, tell the truth to evens and your new career history to the odds.) This gives you a sense of whether the issue you are covering up is an actual employment problem, or whether it's something else.
A salt is not for adding extra secrecy. It's for making it take more work to solve a large number of passwords at once. It doesn't need to be stored separately to do this.
What you're thinking of is a secret-splitting scheme; where you split a secret among multiple parties, where you need the information from both parties to reconstruct the secret. That's a valid cryptographic technique, but that's not what's meant when you say "salted password".
The problem is, for passwords, that approach isn't really workable. Whatever machine is verifying the passwords will need access to the full hash to do so, so if it's compromised, you could get access to the full hash.
I suppose you could split the verification into two parts, on two separate machines. Each one would have it's own password database, with independent salts, and the machine trying to authenticate the user would request verification from each of the other machines before allowing you in. However, that would make your password system slower and more fragile; now if either of those machines goes offline, your login functionality breaks (and yes, you could do a "two out of three" system to avoid that, but now you're talking about tripling your hardware requirements just for your password verification system).
Really the best bang for your buck will come from (a) securing your system so that it doesn't reveal your password database in the first place and (b) using bcrypt, scrypt, or PBKDF2 to make brute forcing a database that is disclosed much more difficult. It's far more likely that you will build a secure system by following basic security practices like isolating services and giving each the minimum privilege that it needs, doing code review, keeping inessential services off of important machines, using prepared statements rather than building SQL queries from user-supplied strings, and so on, as well as using off-the-shelf security components that have been well tested like the above hash algorithms, than you will by designing your own password system using some novel technique to spread the secret out among multiple machines.
There actually has been research on how to split passwords across multiple servers (one example http://www.passwordresearch.com/papers/paper270.html), and RSA is currently marketing a commercial product that does this. While I agree that most people probably aren't concerned enough about password exposure to do this, there are effective solutions to accommodate those that are.
Or, pay him via his parents. Somehow we manage to have child actors get paid by movie studios; there must be a way for them to be able to pay children bug bounties, if they actually wanted to.
The source code is available; it's available under a "shared source" license rather than free software/open source (you can look at it, but not modify it), but it is available for review. https://www.tarsnap.com/download.html
He also has a bug bounty http://www.tarsnap.com/bugbounty.html, and several substantial security bugs have been found and fixed due to the bug bounty (http://www.tarsnap.com/bounty-winners.html). In fact, the first of those, the AES CTR nonce bug, was found before he had offered the bounty program; the bounty program was inspired by that bug, and has since led to the discovery of several other more minor issues.
So, the source is available, and there's a bounty out for discovering bugs ranging from cosmetic issues to major security issues. Feel free to review it and submit any bugs you find!