Hi Kim,
Noted. It doesn't take long for any program to fill up the 32K RAM in
the M100 and family. With Woolly, the Gopher client would actually
reside on the onboard STM32 microcontroller containing 1.5MB Program
Flash and 320K RAM. The code on the M100 would be User Interface code
only making I/O calls to the Woolly based Gopher client to send
keystroke information and read screen content updates. At least that is
the idea.
Ken
On 8/3/17 12:15 AM, Kim Holviala wrote:
Might as well chime in :D
I know more about the Gopher protocol than pretty much anyone (in
2017? how useful!) and I'm the author of pretty much the only
remaining up-to-date gopher server software. Also own a M100, M102,
NC100, Z88 + various other old laptops.
The biggest problem implementing a gopher client is the lack of memory
- it doesn't take a long article to fill up the ~20K that's available
of the 32K free memory after counting in the gopher code. Other than
that the protocol is dead simple, can be implemented without keeping
state and needs no fuzzy parsing logic of any kind because it's very
strict and hierarchical.
- Kim
On 03 Aug 2017, at 10:06, James Zeun <[email protected]
<mailto:[email protected]>> wrote:
Ray I might like to bend your ear, as I've been toying with setting
up gopher on my PiDP-8.
James
On 2 Aug 2017 11:24 p.m., "Ray Lopez" <[email protected]
<mailto:[email protected]>> wrote:
I run a gopher server at gopher://ratthing.com
<http://ratthing.com/>. It can be reached via
http proxy at http://ratthing.com:7780 <http://ratthing.com:7780/>.
I'm always glad to help out with setting up or hosting services.
RL
On 8/2/17 8:03 AM, John Gardner wrote:
> Something for you guys interested in getting on-line to think
about...
>
>
https://motherboard.vice.com/en_us/article/9kwek8/long-live-gopher-the-techies-keeping-the-text-driven-internet-alive
<https://motherboard.vice.com/en_us/article/9kwek8/long-live-gopher-the-techies-keeping-the-text-driven-internet-alive>
