3 ms·
Usage during peak times is already discouraged by the network degrading during peak times: rather than charge more you simply get less value, which is equivalen
by saurik 13y ago
Usage during peak times is already discouraged by the network degrading during peak times: rather than charge more you simply get less value, which is equivalent. This causes traffic to naturally smooth out some over time. You thereby in fact do need some way to cut back on the total usage, as a bunch of people randomly using Netflix really does cost more than a bunch of people randomly browsing the web. The goal of the network is not to support the peak load: this seems to be a key misconception in these arguments :/. It just isn't economically efficient to build a system that can support the peak load. If people really do want to have a system that can stream Netflix to everyone's house at 7pm when the traffic throughout the rest of the day is nothing like that amount, then someone has to bear those costs: either Netflix needs to subsidize the weird bandwidth requirement, customers need to opt in to "supports Netflix" plans, or we have to give up entirely on pricing models that don't take into account usage in some way. You might disagree with how that usage is calculated, but right now the problem is that most people just want "lots and lots of bandwidth for a flat rate", and that is inherently incompatible with a demand for network neutrality :(.
- SilasX 13y agoI'm aware of all that and don't see how it refutes my assumptions or solution. Yes, the network is degraded at peak times naturally. My idea is to further penalize heavy users (weighted by time of use) but do it in favor of lighter users (which avoids the rent seeking problem). As you note, this inevitably penalizes total use, but does it in a way that accounts for when the use is bad.
- saurik 13y agoSo, first off, I want to point out that I think we are largely in agreement, as I certainly would not be bothered with your suggestion were it implemented: the key thing is that people are charged for their usage in some manner as opposed to expecting a flat rate to cover "lots and lots of bandwidth". However, you are also stating that simply charging people by the byte is incapable of having a similar effect--that your modification is the "only way" to gain a benefit. I was showing that because there is already a difference in the price during peak vs. non-peak times you don't need that modification. I also argue (generally in this thread, though not in that comment as it had not seemed like it was needed; now it does) that even as per byte billing has almost the same overall result (again, due to peak capacity being inherently lower than peak desired load) it has a key benefit of being a cost remotely capable of being predicted: charging people based on a constantly-fluctuating idea of "how much bandwidth are other people using" is a price fluctuation that can't be effectively predicted until after you are accruing the cost: it requires users to not only predict their usage, but keep track "these four hours are the Superbowl, so everything is going to cost more". I guess this could be solved by having a live "surge pricing" indicator in your status bar next to the network icon, but that requires infrastructure to traverse that across NATs that we don't have currently. One more point on that: it would also be valuable to do this kind of minute fluctuation with relation to power, but we don't: we just bill at best a difference for "typically peak" vs. "typically non-peak", even if some days are fundamentally more energy-intensive than others (as in addition to it being a weekday someone scheduled a massive lights show across the entire city or something). That is why I still feel like I responded to what you said: while I did not in any way attempt to address whether your model was more or less "accurate" (I have yet to decide whether that is really the case, but it certainly doesn't sound wrong or anything), I was only trying to show that it was not by any means "necessary".
- SilasX 13y agoAlright, I agree that "cannot" was too strong. Nevertheless, charging for total usage is discouraging the wrong thing, even though it correlates with the right thing. If you want the roads to run smoothly, you don't charge everyone a dollar; you charge peak users $4 and everyone else nothing. And weighting data price by "peakness" is not significantly harder than not weighting it; in both case it's "just another metric" for the user to monitor. (The broader point is that, in no case does it justify the standard ISP practice of singling out a particular content provider, even if the content provider is responsible for 99% of usage.)