[untitled]
6 comments
Back in the 1990s when Telecoms needed to built out networks and infrastructure to cover a vast geography with cell towers to get the last mile delivery, these pricing and delivery models made sense. Today, with hundreds of megabits of bandwidth, a planet-spanning internet, and space-based internet, it does not. SMS is a hilariously backward and outdated system desperately clinging to a pricing model that doesn't reflect carrier costs in the slightest. I shudder to think what the internet would have looked like if thinking like this led to mobile networks being so twisted.
Was expecting to learn how SMSes work on the cellular side. Nothing of that sort. This is probably the worst AI slop article I have ever seen with the same thing repeated multiple times, short stupid sentences, which I can only assume is a product of someone pushing his tool/prompts to rank well in search engines.
Small addition:
One thing this post does not fully cover is that delivery behavior is not just "success vs failure".
Different routes can behave differently under load, especially in terms of latency and delivery timing.
This is something most APIs do not expose at all.
A follow-up focused purely on delivery tracking and timing behavior would probably make sense.
One thing this post does not fully cover is that delivery behavior is not just "success vs failure".
Different routes can behave differently under load, especially in terms of latency and delivery timing.
This is something most APIs do not expose at all.
A follow-up focused purely on delivery tracking and timing behavior would probably make sense.
Holy AI slop. How does stuff like this make the front page?