This is very similar to a project I'm working on called Sim95 [1]. It has an entire networking stack and visual basic style language. You can host your own websites, chat servers, anything you want, and everything runs over a virtual network (websocket that passes through a relay).
It has all the warts of the early internet era: you can program a virus, get people to download it, delete their documents, etc., but it also has a lot of the charm, build a website, chat with strangers, enjoy the lack of facebook (for now until someone builds it).
Lovely. 16MB of RAM in the 90s? That's luxury.
And that dial-up sound always takes me back to happier times. Not unlike normal people's childhood songs.
Sort of. The quality/length of your local loop made a difference.
And heck, 56k being able to do 56k in the first place was dependent on not having a "regular" line between the ISP and their central office (CO), but rather it being digital, whereas the line from the user to their CO was always analog. Removing a set of digital to analog and analog to digital conversions in the ISP -> user path was what allowed the download speed to reach 56k. Upload was limited to 33.6k because it included an additional set of conversions and introduced more errors, prohibiting the higher speed.
This shows getting up to 56k over normal phone lines was indeed tricky.
In order to get 56k, you needed to be on a reasonable quality line, and there needed to be an all digital (PRI) connection between the Telco end of your phone line and your ISP.
If your line was noisy good luck. If your line had loading coils in the path between the CO and you, that would help your voice calls but make 56k harder to achieve (and was definitely problematic for DSL). Most telephone lines had loading coils every wire mile between the CO and the customer. If you had any of the older wonky stuff telcos used to magic more pairs for customers out of thin air, chances are they wouldn't work at 56k.
56k modems didn’t always negotiate to the full 56k. The handshaking allowed connections at much slower speeds. It depended on the quality of the line. This is the US - we didn’t have ISDN, at least no one I knew had it in 1996.
ISDN was available near me in 1996 (Southern California, Pacific Bell) ... but nobody I knew had it. It cost a lot for the install and monthly, and there was no unlimited local calls tariff like there was for a regular "analog" lane. You'd have to be pretty serious to want that.
A while back, I set up a server that limits bandwidth through it to roughly max dialup speeds https://dialup.moveything.com/. It has some gifs, progressive jpegs that are fun to watch load, and a mirror of xkcd.
It uses rate limit buckets per-IP on the server side, applied before SSL termination so it doesn't include that overhead. If you open two tabs, they'll have to share. If your behind a NAT, you'll have to share with your NAT-mates. And, it also has headers saying not to cache anything, so you can continue to enjoy the experience.
A lot of people don’t know how cool it felt to dial into the internet or a service like Compuserve or Prodigy and suddenly have this whole world open up to you. Even at 56k.
I'm sure someone pointed this out in the other thread, but 56kpbs modems essentially didn't exist in 1996. They launched at the end of the year, cost a ton, and the manufacturers hadn't standardized the speeds, so it really didn't matter much as you weren't browsing AOL, MSN or Compuserve with it yet.
33.6k.rip is a harder domain name to get though, so I get it.
That reminds me. Can we standardize cypress tests to load the website via a restricted speed as one of the tests? Some of of our modern webpages are still slow on the latest iPhone/Pixel/Samsung over 5G.
8,600,743 bytes of assets and frameworks later I'm finally able to see your contact-us address.
It has all the warts of the early internet era: you can program a virus, get people to download it, delete their documents, etc., but it also has a lot of the charm, build a website, chat with strangers, enjoy the lack of facebook (for now until someone builds it).
1: https://sim95.kippy.io/
(When did this change? Around 2012?)
Also riddled with inaccuracies.
iirc ISDN did require a special phone line, but 56k was fine over regular lines.
Sort of. The quality/length of your local loop made a difference.
And heck, 56k being able to do 56k in the first place was dependent on not having a "regular" line between the ISP and their central office (CO), but rather it being digital, whereas the line from the user to their CO was always analog. Removing a set of digital to analog and analog to digital conversions in the ISP -> user path was what allowed the download speed to reach 56k. Upload was limited to 33.6k because it included an additional set of conversions and introduced more errors, prohibiting the higher speed.
This shows getting up to 56k over normal phone lines was indeed tricky.
If your line was noisy good luck. If your line had loading coils in the path between the CO and you, that would help your voice calls but make 56k harder to achieve (and was definitely problematic for DSL). Most telephone lines had loading coils every wire mile between the CO and the customer. If you had any of the older wonky stuff telcos used to magic more pairs for customers out of thin air, chances are they wouldn't work at 56k.
You only got max speeds where the noise was low enough.
sometimes you'd also reconnect because the handshake got messed up and you'd connect at 33.6 instead of 'real' 56k
It uses rate limit buckets per-IP on the server side, applied before SSL termination so it doesn't include that overhead. If you open two tabs, they'll have to share. If your behind a NAT, you'll have to share with your NAT-mates. And, it also has headers saying not to cache anything, so you can continue to enjoy the experience.
33.6k.rip is a harder domain name to get though, so I get it.
Now we just need to bring back BBS’s and the daily turn based games. Legend of the Red Dragon, Usurper, etc.
Select modem mode and just hurt.
8,600,743 bytes of assets and frameworks later I'm finally able to see your contact-us address.