mtvessel: Snaps approach to rolling over data is more like paying for too much food from McDonalds and them saying, OK you don't need all this food so we will sell it again to someone else.
I prefer a swimming pool analogy.
You pay a set amount to go in the swimming pool and you can swim anywhere you like in the pool. But other people are also paying to swim in the pool (shared bandwidth) and they can swim in the bits that you aren't using at that time.
Do you complain to swimming pool owners that they are selling the space that you don't use to other people? why not? you paid to swim in the entire pool but other people are using it too! If too many people get in it iwll get crowded and hard to swim where you want to go, but that's just tough.
i could see why snap dont want to do it, i pay for 150 GB a month and usually have 15 GB or so left each month, after 2- 3 months of rolling over i would only pay for 60 GB the next month but still use the same amount , if everyone did it there would be some months where people are getting free data and Snap would be paying for it , not good business practice.
TBH I'd like something similar to what WXC had with the torrent plan; unlimited nights every night but pay more for daytime traffic. I think this is a win-win for everyone; the leeches get free data, and the ISP gets less contention during the day (when it's normally busiest and the pipes are bursting) and more usage at night (when it's normally dead quiet and the pipes are idle; costing lots with no one using them). It helps to even out the normally very peaky traffic I think.
Of course the pricing structure would probably need to change (more cost for less data during the day), but personally that kind of setup is perfect for my usage patterns and probably a lot of other people's as well.
TBH I'd like something similar to what WXC had with the torrent plan; unlimited nights every night but pay more for daytime traffic.
Maybe if 2am-6am or similar. Unlimited any earlier would screw my late-night gaming sessions.
The current datapack system would seem compatible with a carry-over type system.
Why not have your usage drawn from that additional datapack pool first; you'd need to use it all up before starting on your base allocation. So you'd need to use the extra data before the end of the month or you'd sacrifice your base data.
The first month you'd want to add the datapack towards the end of your data allocation, and then you'd want to consume all that additional data before the end of the 2nd month.
Kind of a compromise where your data would be usable in two month blocks rather than resetting monthly.