Web Browser

In general we could have a Nano-X compatible browser (that uses Nano-X API) that executes on a contemporary machine, but is displayed on a Nano X server running under ELKS. So you:

• telnet to a modern computer or Rasberry PI
• you configure the a Nano-X browser to use the network IP of the Nano X server running under ELKS
• you start the browser over telnet on the remote computer, it shows on ELKS and Nano X

So it is like finally using the advantages of the client/server architecture of the X graphical systems. I used to do a lot of X server ssh port forwarding.

Also the browser needs to compile on contemporary systems, not ELKS, which probably makes it easier to develop.
We could say that it is not limited by the memory available to ELKS, but indeed it is. Showing an image on the X server under ELKS will still consume a lot of memory.

The issue proposes a Nano-X browser running on a contemporary machine and displaying through an ELKS Nano-X server, but names no files, tests, or entry points. First clarify the browser scope and implementation plan, then define how remote display, compilation on contemporary systems, and completion will be verified.