People are probably block robbing on their optimized clients. Someone has got to release an optimized binary.

Any idea how to "hashing the block header once per nonce instead of 1-3x..."

Who knows what that actually does to the potential of finding a correct PoW though.

Running different Sieve values per thread rather than the current all threads same Sieve, could spread out that risk, even if it's just 1 out of 4 running at 10k and the other 3 at 1M

Has anybody else tried messing with the nMaxSieveSize variable?
By chopping a zero off of it, I seemed to be able to get almost a 5x increase in pps. I know that reducing the sieve size would effectively reduce the amount of numbers checked for each run of the sieve and then reduce the likelyhood of finding a block, but is pps more important than search size?

Left my somewhat optimized version running over night and came back to 3 additional blocks mined.
Getting roughly ~60 pps with 500K sieve size and basic optimization flags. Running on a single thread of a stock i3 2120.

What will the value of this coin be with how few of them are in existence?

will there be a mac os x client in near future?