but isn't the speed (7 tx/s) different than the block size limit (1MB/block)?
The block size determines the transactions per second. Allowing a larger block size means that more transactions can be included per block.
thx for making me review that. i was getting confused with data rates. is there a maximum MB/s that constrains the network speed?
At least there is no hard limit. There seems to be a soft limit depending on the network bandwidth of single nodes, though. If a single node has not enough bandwidth to download the next block within 10 minutes, it can't catch up with the blockchain. E.g. a typical private residential internet connection has about 2 MB/s (?) receiving bandwidth. When blocksize is larger than 2 MB/s * 10 * 60 s = 1200 MB, home nodes can't download the blocks in time and will be left behind. Luckily it's the receiving speed that is relevant here, which is a lot faster than sending speed on the typical home internet line.
EDIT: There is nothing stopping an organisation having 2 pools at 20% = centralization by a different name, but at least there would be no danger of a 51% attack.
The danger of attacks possible by controling more than 50% of hash power are still there, even if a single organization decides to operate 2 pools. The organization simply has to coordinate the attacks across both its pools.
I think having one organization operating 2 pools is even worse than having one organization operating one pool. More so, if it's not known by the public, that both pools belong to the single organization. The real danger is hidden in this case, which is worse, than a danger the public knows about.