The thing I don't like about the US democracy is that it's essentially false dilemma based. Yes, you do have more than two parties, but "everyone knows" that they will never get elected, and you can't let the other side win, so you "have" to vote on one of the two big parties.

How much of a democracy is it when the choice is that limited? It's a soft limit, but still an effective limit.

If North Korea let the people select from, say Kim Jong-un and (while he was alive) Kim Jong-il. Would that then be a democracy? If they technically allowed other people to run for Dear Leader, but manipulated the populace to only consider the two main candidates, would it then be democracy?

I see, thanks for the answer :)

At least you have thought about things, and seem to have a good understanding of the mechanics, and have reasons for the changes. Which is more than sadly too many who develop crypto code have.

As for the changes you've made, I haven't looked at them closely so I won't even try to discuss them :)

The only thing I can say about it is the basic gut feeling that any novel approach to crypto should be distrusted until verified by time and experienced people :)

A bit late to the party, but.. There are some things I'm curious about.

Wouldn't different IV (or nonce in CTR mode) effectively stop that potential problem?

And from another of your posts that I was wondering about:

A bit change in CTR mode shouldn't alter anything past it's block, from what I understand. There's no state that's moved on from one block to the other (well, except the counter, but that's not affected by the block data).

And again, wouldn't different IV / Nonce effectively stop that problem?

http://linux.die.net/man/1/tcptraceroute

http://manpages.ubuntu.com/manpages/gutsy/man1/paratrace.1.html

8. Add option for custom CSS?

I'd like to mention that many of them are currently ditching 100% of the pc gaming marketplace, and are doing fine.

Did anyone say SteamOS?

Peekaboo

Didn't the manufacturer make similar claims about the Mythbusters lock too? That turned out to be hogwash.

Let's wait and see how it actually works.

http://www.anandtech.com/show/4329/intel-z68-chipset-smart-response-technology-ssd-caching-review/2

Intel SRT tech seem to bring a good compromise. Best of both worlds sort of.

> Mega claims that they could not decrypt your files. This is demonstrably false.

Not quite.. It requires all these things to happen:

1. Mega gets a reason to get your key (LEA for example)
2. Mega adds new JS just for you
3. You use the web interface
4. You log in
5. You don't notice the new code (Mega already have a chrome browser extension that would stop this by running its own code instead of the server's code iirc)

So.. They have to start looking for your key, you have to use the *web interface*, AFTER they decided that, and you have to run the new code.

None of these are a given. You can upload on an account, and then never log in again. Or use a non-web client (is for android and windows, at least). Or use a browser with the extension.

Hehe, yeah, the AA defense in TA had some problems with large air swarms. Think they just moved too fast for the in-game engine and defenses to keep up properly.

Hence, why you made large fucking swarms, and just set them to patrol the enemy base. They'd need an equal fuckton amount of air defenses to stop it, making it impossible to do anything else (and they slowly got killed, too.. And then your base stop existing)

Go home, comment. You're drunk.

Django, Pylons, Bottle, Flask, TurboGears, Zope, Web2Py...

And that's just some of the popular frameworks..

Another TA fan! Wohoo! okay, I mostly turtled, built vulcan, and then just sent waves of Hawk's until the enemy base were gone, mine were gone, or he'd built too much air defense..

Anyway.. As a TA fan, I keep a close look on Planetary Annihilation - I just hope they get that good old TA feeling into it (they say they focus more on TA than SupCom, but we'll see)

Alpha is out, and there are a lot of gameplay videos out, but I am waiting for beta before I get my toes wet.

Deliver open API. Make a smartphone app. Add support for making "payment". Support QR.

Logic:
  * Merchant makes payment entry (give it description, unique id, itemized bill if wanting to, and so forth)
  * App (or own system) shows QR code with data
  * User scans QR code
  * User gets full details of the transaction
  * User click "Pay" - data gets sent to paypal, which verifies, matches unique ID, and sends confirmation to merchant system.
  * Merchant screen shows "Payment OK"

Alternatively you could use bluetooth or NFC to transfer the data instead of or in addition to QR.You could even set the phone app to connect to specific wifi or bluetooth connection automatically (if available) to send the data to paypal, so all devices with camera and wifi would be supported, no need for mobile internet.

PayPal already have the branding and infrastructure. They could do this in a week.