We desperately need absolute maximums enforceable in the browser, reversing the firehose. I want to opt your site in to more data use, after I trust your site. And I expect sites to work within my limit or not receive visits.
We desperately need absolute maximums enforceable in the browser, reversing the firehose. I want to opt your site in to more data use, after I trust your site. And I expect sites to work within my limit or not receive visits.
Workers don't shovel extra connectivity into the towers when you go over your data cap. So why are you focusing on data flowing over the nearly-always-on connection you have through your data plan, rather than the bullshit terms you agreed to when you signed up for a data-capped plan in the first place?
Edit: remove unnecessary word, clarification
The bus doesn't magically add more seats when you make extra trips on it, but it still costs more to take the bus three times a day than twice a week.
Even though the marginal cost of your body on the bus is minimal, having the fee serves to reduce crowding (demand at that price point) as well as fund the infrastructure. Data caps are the same.
Now, you can argue that data caps are surrounded by deliberately misleading marketing and that overage charges are unnecessarily steep. But you seem fundamentally opposed to the concept of data caps.
Do you ride more because it’s unlimited? When you get to your stop for your office or dinner or whatever, do you go back home and then back again before getting off? Do you go all the way to the end of the line to minimize your cost per mile, then walk back to your actual destination?
Of course not, you use it as efficiently as possible to do the thing you used public transit to actually _get to_.
Do you consider the money you spend for your unlimited pass as rent for housing or office space? Do you just stay on the bus all day, working on your laptop and holding meetings?
Unlimited transit passes are similar to unlimited vacation plans: people normally need and use much less than 100% of the resource offered. People also don’t normally push 100% bandwidth 24/7 through their unlimited plans.
If everyone decides to use their unlimited transit pass in this way, they will go away or increase in price accordingly.
The comment I replied to claimed transit systems don't sell unlimited-ride passes. I was pointing out that some of them do. What you're arguing is they wouldn't have the capacity to handle it if every person bought such a pass and immediately ceased all activities other than riding transit 24/7, which may well be true, but is also a non sequitur.
Though since you ask, it would be a bit difficult for me to "maximize" use of my Caltrain pass in the way you're suggesting, since going "all the way to the end of the line to minimize your cost per mile, then walk back to your actual destination" is not realistic -- the line is ~80 miles long.
Hi fwip,
I don't have any knowledge about the economics or logistics of city bus lines.
I do understand something about Transfer Control Protocol, Javascript's event loop, and soft realtime performance in Linux.
Can you make an analogy between data caps and any of those concepts so I can understand what you're getting at?
-You can divide the total capacity up equally and give everyone dedicated connections that aren't very fat. Nobody likes this, and it's very inefficient because most people aren't using their full bandwidth most of the time.
-You can charge by the byte, on top of the base fee, so that using the system more costs more. It's fair - pricing directly reflects resources consumed - but nobody likes the idea of being nickel-and-dimed whenever they click a link.
-You can do the above, but include some large chunk of data (which is quite cheap) into the base fee, that most people won't go over. Call it a "cap". This works well.
-You can promise "unlimited" data, but start sending nasty letters and/or slowing the connection to a crawl when they go over some prescribed "fair use" amount. This is a data cap in all but name.
Basically, all-you-can-eat stuff is always sold on the basis that you will consume some reasonable amount, because no resource is infinite.
Without any decent weight behind it, there would be no incentive for people to build their software to actually respect the user and they would continue serving a broken application.
Much like browsers slowly boiling site owners by displaying sites as insecure if they don't have any encryption, a similar effort could be made to stop websites handing visitors around like the town bicycle.
I've thus written a script that I run daily for my local unbound(8) daemon -or bind: https://gitlab.com/moviuro/moviuro.bin/blob/master/lie-to-me