Jamie McKane
MyGaming Journalist
This ISP explains why data caps exist
"It's just like eating Oreos".
"It's just like eating Oreos".
The solution is simple, if you're not prepared to offer an "uncapped" service then don't.
Uncapped (from the dictionary definition) "free from limits or restrictions"
The moment you introduce any limits or restrictions your service is NOT uncapped. A fairer representation of why data caps exist is the "bottomless soda" conundrum. Say your restaurant offers a Bottomless soda for lets say R25, where your normal soda costs R12.50 and your true cost to provide that soda per glass is R2.50. You'll make R10 for every normal soda you sell and every time the diner orders another soda you'll make your R10. With your bottomless option it still costs you R2.50 to provide the soda and say the average diner consumes 4 sodas per sitting it will mean that your costs to provide that service was R10 yet you still make R15 on the deal. The issue comes in when Big Joe and his mates arrive and they each consume 10 sodas. Suddenly you're not making money on them being there and consuming your "bottomless soda" so what you will do is either slow down in giving them their top up drinks (throttling) or you start adding more ice and/or watering down their drinks (shaping). As a result they are not getting exactly what they are paying for as their service has started to slow down or the quality of the product has started deteriorating. Now realistically you cannot support having your restaurant filled with Big Joe and his mates, but you also cannot expect everyone to not buy your bottomless drinks as you are making a fair amount more profit on the bottomless users who don't consume your soda in excessive amounts.
Anyways, that is just my 2c
You must spread some Reputation around before giving it to PsychoFish again.
AlsoYou must spread some Reputation around before giving it to PsychoFish again.
The solution is simple, if you're not prepared to offer an "uncapped" service then don't.
Uncapped (from the dictionary definition) "free from limits or restrictions"
The moment you introduce any limits or restrictions your service is NOT uncapped. A fairer representation of why data caps exist is the "bottomless soda" conundrum. Say your restaurant offers a Bottomless soda for lets say R25, where your normal soda costs R12.50 and your true cost to provide that soda per glass is R2.50. You'll make R10 for every normal soda you sell and every time the diner orders another soda you'll make your R10. With your bottomless option it still costs you R2.50 to provide the soda and say the average diner consumes 4 sodas per sitting it will mean that your costs to provide that service was R10 yet you still make R15 on the deal. The issue comes in when Big Joe and his mates arrive and they each consume 10 sodas. Suddenly you're not making money on them being there and consuming your "bottomless soda" so what you will do is either slow down in giving them their top up drinks (throttling) or you start adding more ice and/or watering down their drinks (shaping). As a result they are not getting exactly what they are paying for as their service has started to slow down or the quality of the product has started deteriorating. Now realistically you cannot support having your restaurant filled with Big Joe and his mates, but you also cannot expect everyone to not buy your bottomless drinks as you are making a fair amount more profit on the bottomless users who don't consume your soda in excessive amounts.
Anyways, that is just my 2c