Conceivably this bounty would be payable not only to government department employees, but also to anyone able to access government servers in the US, New Zealand or elsewhere, or servers of any companies or organisations working with these governments, who can retrieve documents clearly proving corruption in the whole prosecution process, and these documents help materially to derail Kim Dotcom's prosecution, this would most certainly qualify for the bounty."
- Choose n separate trusted individuals or organisations, ideally scattered around the world and unaware of who each other are
- Gain promises from these entities that they will each send a block of data to the time capsule at a given time, and not before
- Decide by policy how many of these entities (m) should be required to do their part, for the time capsule to be decrypted
- For every combination of m entities, generate m strings, where the XOR of all these m strings arrives at the decryption key
- For each of the n entities, issue the required number of strings (n-1)C(r-1) required to contribute to every combination of m entities of which this entity is a part
- Each string is prefixed with a binary string of n bits, indicating by true/false values whether the string is part of a group of each of the n respective keepers
- The whole set of strings given to each entity would be prefixed by a 'keeper number' and then encrypted
- The time capsule curator destroys all record of who these trusted agents are, and relies on them to send their keys at the appointed time
Example - 10 keepers chosen, 4 in UK, 1 in Iceland, 2 in Australia, 1 in USA, 1 in Uruguay and 1 in Morocco. Policy chosen so that the cooperation of 7 is required to decrypt. Each keeper then is thus issued 84 strings. 1 agent dies, another agent gets busted, and a third agent becomes opposed to the decryption. This leaves 7 agents. They each send their key packages in to the time capsule curator, who decrypts each package, identifies which string within each package is need to form the key, XORs these strings, then arrives at a final decryption key. Even if an intelligence organisation manages to extract keys from 6 of the agents, they won't be able to decrypt. If on the other hand, they kill up to 3 of the agents and stop them returning their keys, the decryption can still go ahead. Ideally, you would want to set n and m according to perceived risk, plus the size of the data set. For example, 36 agents and 20 required would produce a key set which would fit into a cheap 8GB USB stick.
- A 'developer' is paid to create code that works within the company's contrived runtime environment and passes a few stages of testing, while a 'software engineer' is also paid to ensure the code actually works reliably in this nebulous abstract construct called the "real world" - customer/client installations where there are innumerable environmental variables and things that can go wrong.
- A "developer" nods timidly and reluctantly to Murphy while passing in the corridor. But the software engineer says "Thanks for another great night. What would you like for breakfast?"
- A "developer" goes whining to her/his team leader when the tools or OS play up. A software engineer cracks out the machine-code debugger, logic analyser and oscilloscope, traces all the API calls, and spits out working patches for the bugs in the libraries, drivers and kernel.
If I had some plant that was failing at 3:15am and costing me a fortune, I know which I would prefer to have on site.
I'm thinking along the lines of the emacs "spook" function, amongst other things. You just need enough a large enough group of participants working together.
The system can be trained in weird ways. For instance, if enough people in enough places scratch their noses with their left hands, then break out in a mock fight, the system will learn to sound the alarm every time someone scratches their nose with their left hand.
Or, for something more socially useful - have people pull out a cellphone, talk for a few seconds, then pull out a mock gun and pretend to mug others. Then, the system will freak out every time some annoying jerk pulls out a cellphone in public. Along that same theme, train the system to send in the troops whenever someone adjusts their underwear in public, or picks their nose, or farts loudly...
Link to Original Source
* Its memory bloat teaches us to be mindful of our resources, both within the computer, and our use of our resources in everyday outer life.
* Its slowness helps teach us patience.
* Its slow startup teaches us that wonderful things don't happen instantly, and that we need to lose our attachment to time
Stay away from Chrome - it feeds the ego by promoting our addiction to instant gratification