Won't be enough for netflix or torrenting.
It also assumes that the "backhaul" between satellites wouldn't saturate under such a load.
I'd wager that under those assumed numbers you'd more realistically be able to expect somewhere between 100Kbps and 1Mbps.
Yes with packet scheduling you can get higher peak bandwidth, but 1Mbps sustained over the course of a 5 minute youtube video is going to be hard.
It's much better to target the whatsapp crowd. That facebook will pay for.
Current consumer technology gives 300b/s to too 500 kb/s Depending on how much you want to pay.
*speeds in bytes not bits
Then you should use the correct metric prefix, kBps, not kbps. It would save you from having to give unnecessary explanations.
People really should be using only kB/s and baud.
The / means per, so it means exactly the same as the p. What's misleading about it as long as you capitalize the units correctly?
Now you want to add the confusion back. Luckily, units are standardised by international bodies, not individuals, and the industry seems to be happy with the standards and uses them. Very seldom I have seen kBps (and in the few cases where I have seen it, it was wrong anyway). kb/s, while correct, I have only seen used by mistake, or by malice (e.g. ISPs intentionally misleading customers). Luckily, most professionals agree on only using B/s and bps, and no other combination, correct or not.