Thanks for your reply! Good point re: browser but I guess that's where my excitement about the possibilities lies: I wouldn't mind an extremely under-resourced device. RSS feeds and text content could be sent (and wouldn't require specialized rendering), vector maps and points of interest or transit info could be super minimal in terms of bandwidth/rendering requirements, etc.
I think that I want a 5G tty qwerty terminal..? :-)
aka https://github.com/rastapasta/mapscii for maps, etc.
> and you're not easily going to get 4G/5G support
Sorry, what do you mean by that? In the sense of 4G not being that supported vs 3G? As in the chips aren't available? Or 4G service is hard to find..?
Cheers
> I wouldn't mind an extremely under-resourced device. RSS feeds and text content could be sent (and wouldn't require specialized rendering), vector maps and points of interest or transit info could be super minimal in terms of bandwidth/rendering requirements, etc.
A compromise might be to send the traffic via a proxy that pre-resizes images, renders content and chops it up into a manageable format for a resource constrained device.
> I think that I want a 5G tty qwerty terminal..? :-)
> aka https://github.com/rastapasta/mapscii for maps, etc.
For resource constrained devices, it's probably easier to render the vector graphics. There's a few open end points out there that could make it feasible for basic navigation.
> Sorry, what do you mean by that? In the sense of 4G not being that supported vs 3G? As in the chips aren't available? Or 4G service is hard to find..?
You can get them, but they are harder to interface with than the existing 2G/3G chips. Whoever takes on the challenge might have to do some work reverse engineering how to correctly speak to the modem, for example.
WML is (needed) back?
https://en.m.wikipedia.org/wiki/Wireless_Markup_Language
It would help, but the majority of pages out there are completely unusable without Javascript.