Nice that instead of completely cutting you off at the cap they put it in super slow 500 kbits. That is actually usable and used to be the fastest speed you could get at home.
My first company was an ISP, and our selling point was that we had higher bandwith out of Norway than any competitors in our price range.... A whopping 512kps.
I remember being amazingly excited to have saved up enough money to go to the store and buy a 33.6 modem (an amazing upgrade from my 14.4).
A year or so later I upgraded to a v.92 only to realize my ISP (I think it was IDT at the time) didn't support that and only supported some other 56k "standard" (details are sketchy on this, I was like 12). I was devastated and it was too late to drive back to computer city to exchange it for the correct one.
If I remember right we could get 64kb/s or 128kb/s if you bundled them, that was in Germany. But also, we didn't have that, we only had a 56kb/s modem and I remember really wanting ISDN when I was a kid :)
Copper, but not ISDN. Fractional E1 leased line. There were expensive and limited ISDN connections available in Norway at the time ('95), but not cost effective for an ISP.
The standby account -is- 500 kbps, probably it's the same mode, so I'd expect the same performance.
Anecdotally, even though I'd have told you that 500 was probably enough for non-streaming stuff that I do most of the time, in my experience when my connection switches over to Starlink (I have Comcast primarily, but it has had reliability problems the last few months), it usually hits the Starlink limits pretty hard. I've never identified any nefarious activity, it just seems like all the little things on my workstations and various devices that chatter add up to enough to trigger Starlink's controls.
The first modem that I owned was 1200 baud. The first one that I used was 110 and it was exciting when it was upgraded to 300. It took ~20 years from when I first got online until my home internet reached 512kbps.
I bought a cheap 1200 and then once I had use for it I saved up for a USR 14.4 with a shiny extruded aluminum case. At one point I was sharing that with two roommates using SLIP and surplussed Cisco coaxial NICs.
Ok, I’m not normally one to be the pedantic bits/bytes guy, but if you’re gonna go and make a bit/byte “clarification” you need to get the annotation correct or you'll just confuse everyone.
It’s 500kb (small b for bits) and 62.5kB(capital/big B for bytes).
People always use bits for connectivity. 62.5kB/sec -- maybe really 55-60kB/sec downloaded. Or 18 seconds to get a megabyte.
This is simultaneously fast (on my 14400 bps modem that I spent the most time "waiting for downloading", I was used to 12-13 minutes per megabyte vs. 18 seconds here) and slow (the google homepage is >1MB, so until you have resources cached you're waiting tens of seconds).
It would be nice if everything were just a touch more efficient.
I end up transferring 940kB (with a lot of blocking cranked up). Typing "hello" in the search bar takes it up to 1MB. Then the first page of search results is another 1.3MB.
Now, I assume all of this would start working before it's all transferred. But we're still talking about tens of seconds of transfer at 500kbit/sec.
(And Google at least acts like they care about bandwidth a little. So many 15megabyte pages out there...)
Unfortunately, the 56kbps internet was a lot more usable. I've been on 256kbps cellular connections (T-Mobile free international roaming) and it works, but it's pretty bad. Everything takes way more data these days, and nobody thinks about slow connections when writing software so there are a ton of overly aggressive timeouts and bad UI that assume operations won't take more than few seconds.
Data rates are almost always multiplied by powers of 10, because they're based on symbol/clock rates which tend to be related to powers of 10. There's no address lines, etc, to push us to powers of 2 (though we may get a few powers of 2 from having a power of 2 number of possible symbols).
So telco rates which are multiples of 56000 or 64000; baud rates which are multiples of 300; ethernet rates which are mostly just powers of 10; etc etc etc.
Of course, there's occasional weird stuff, but usually things have a lot of factors of 5 in there and seem more "decimal-ish" than "binary-ish".
I'd disagree that that is usable today. A few days ago I had some network trouble that restricted me to about 350kbps, although stable without much packet loss, and a lot of stuff just didn't practically work. At that speed, loading images and resources on webpages within timeout limits is hard. Many web apps don't work, or degrade enough that you wouldn't want to use them.
Also what do we actually use the web for? A lot of streaming video and audio that won't work. A lot of reading webpages with a lot of images and ads, that won't work. I'm sure that Wikipedia would load and work slowly, but that's not really representative of web usage today.
There's a separate argument about whether the web should be like that, but regardless of your thoughts on that, it is like that.
Set your device to "metered network" and all the background shit will stop running. That's what I had to do to get my Starlink mini working in Standby mode. As soon as your device is on WiFi it thinks it's a free for all and starts updating and downloading shit in the background.
The 500KB/sec is more than enough as long as that isn't happening.
I need to go improve my knowledge, I haven't paying enough attention to the options lately, and I experience the same phenomenon -- I have a few workstations along with some IoT trash and Starlink standby mode pegs just from the chatter from the devices. As you say, on WiFi they don't bother controlling themselves and they are constantly finding things to do.
- News, phlogs, Wikipedia, translation services -> Gopher or Gemini, gopher://magical.fish and gemini://gemi.dev plus gopher://sdf.org and Bongusta Phlogs. It's magical.
- IRC or IRC+Bitlbee -> IM, Jabber, IRC, most protocols
- Email -> Mbsync+msmtp + mutt. Caching helps there
- Usenet -> Slrn+Slrnpull, it has tech groups, caching and there's a web news discuss group too
This is fine if you're the sort of person who knows about IRC, is satisfied with content on Gopher, etc.
But most people depend on contacting family and friends via WhatsApp/Messenger/etc, they depend on YouTube for entertainment and education, their TV is increasingly online, they read their newspaper on a website with images, etc.
It's a privilege, and a lifestyle choice, to be able to live on 2.7KBPS.
You can use whatsapp over IRC->Bitlbee and reading newspapers at least for text mode. Privilege? more like the reverse. There are phone data plans for $10 that upon finishing your monthly data, you got throttled like that until the next month.
And in my country people did crazy stuff in order to ilegally watch soccer matches in cable TV's, such as writting magnetic deco cards with an electronic PICF84 based tool.
That compared to using Lagrange and gemini://gemi.dev to read the local newspapers and bookmark them in order to avoid typing down the https:// URL over and over, it's lke going for a Ph.D instead of joining a local library.
People isn't that dump, it's just lazy. And, sadly, uninformed.
In the infamous blackout in Spain, I was the only one in the bus that could fetch the news reliabily over Gemini due to the low bandwitdh.
The rest were waiting over and over.
And after that everyone got a pocket radio tuner just because. Something I was just doing over decades too because FM and AM radio will actually work anywhere.
But the web doesn't offer a nice degradation. In the blackout, they just kept sending the full raw data, literal thousands of cookie trackers, JS scripts and the mandatory ads. You at least have https://text.npr.org and https://lite.cnn.com. My country? They just pushed the web SPA's and OFC they set no OPUS stream (something every smartphone understands from at least 2012) with a smaller bitrate.
I hope we get LLM browser agents that will convert the web back to that state again. You can get sorta close now with adblockers, various "lite" modes, and unofficial client sites, but it would be nice if it were universal.
This is a separate discussion, but while I agree in general that pages should be less bloated than they are, ads shouldn't burn my CPU, etc, I think it's a sign of progress that the web takes much more bandwidth. 4K video is better than HD, is better than SD, is better than no video. Illustrations improve articles. More client side Javascript tends to mean more interactivity which is often a good thing (not always). The web today does so much more than it did 20 years ago, and we should be proud of that achievement rather than push back on progress by expecting the web to work on a connection from 20 years ago.
No, not nice. Previously, if we exceeded the 50Gb cap, there was the option to continue on at high-speed for $1/Gb. And that's the same price per Gb as the base plan of 50Gb/month for $50. Now, it's either upgrade to unlimited, or enjoy Netflix at 500Kbps. I want the old plan back.
It's unlikely that we will exceed 100Gb/month in the camper. But if we do, it's either slow speeds, or pay $165/month for unlimited roam every single month we use it, versus paying a little extra for the few times we go over. In the end, it'll probably work out okay for us, but I liked the previous option of being able to get high-speed data at a reasonable price should we go over the limit.
Fortunately 1. For slow speeds, it’s not like you have to live with that slowness every day. The impact is limited to the remaining few days of the month where you ran up against the 100GB, so the either-or in your statement looks worse than it is; and 2. Starlink makes it dead easy to switch from plan to plan right in the app so you can go right back to a lower plan when the higher one is not needed. With the caveat that they do change what plans are available sometimes as we’re seeing here.
If I calculate correctly then 500 kbps is actually enough for Netflix in standard quality. If one wants to binge watch 4K (7 GB per hour) then the unlimited plan makes more sense anyway.
