Mexico, 2026-10-27
Good day. Or midnight, or whatever. So, now you can read the blog from the WAP side of this website too. WAP or Wireless Application Protocol was a standard that allowed very basic phones to use the internet. It was introduced in 1999, when phones had tiny monochrome screens, kilobytes of RAM, and their internet speeds ranged from 2400 to 9600 bits per second.
Knowing this, WAP really was a way to define which limited set of capabilities was a WAP browser in a cellphone expected to support. In other words, it was, at least in part, HTML for very basic cellphones.
WAP imposes very strict limitations. Pages are written using a language called WML, which feels a lot like HTML, but it's actually XML. Many body tags are shared with HTML, hence why it's not impossibly hard to write an HTML to WML converter, or content that works for both. However, WML uses a fundamentally different structure around said body, so it's very much not like you can drop an HTML file in and expect it to work. A converter (or coding for both) remains feasible nonetheless.
Among those limitations, it is often not possible to exceed 1 KB of network data per requested page. WAP gateways were once a necessary intermediate between cellphones and WAP content servers, they work by compressing content requested by cellphones in a basic, easier to understand format. It is kinda like a proxy. Cellphones use the UDP protocol to communicate with the WAP gateway, and then the gateway itself uses HTTP to contact WAP content servers.
The hard limit for early WAP devices was the MTU of the network itself. Some devices would work unreliably if a displayed page was larger than 1 KB. If anything, a hard limit was around 1400 bytes on the wire, which often equals to 1500-1800 bytes of text content depending on how well the compression worked.
In practice, this means that any serious website that wants to offer the same text content (or wall) on WAP will have to implement a way to break the image down on pages. Doing so was pretty hard for me but eventually I figured a way. It's kind of basic and broken, but it works, it avoids destroying tags, ensures that they are recovered in order and avoids breaking a word across two pages.
I have set the WAP side of the blog router script to limit page size to somewhere between 1200 and 1300 bytes. These are text bytes, if you are using an older phone that requires a WAP gateway, data on the wire will probably be between 900 and 1000 bytes per page. Unless the phone firmware itself is buggy (many were, even under conservative limits), you should not have trouble reading this.
However you may or not be sore from scrolling through so many pages. But yeah, this is why you're gonna take a bit of time to read through this if you're coming from the WAP world.
Sorry if this blog post was boring. I was excited to see this working, and honestly I am being a bit verbose on purpose to test the whole thing with actual content.
I'll remind you that the HTML (desktop/laptop) side of this blog does have an RSS feed, so if you want to stay tuned and get a notification when I post a new entry, well, there it is, load the URL up onto your favorite RSS aggregator.
Oh, and I forgot to mention. The WAP website can be accessed from a retro cellphone (or a WAP browser) on wap.danielthefox.com. Your mandatory stop in the mobile information superhighway.
Cheers, have a nice day.