I hoped this would be a conference about retro uses of the Gopher protocol in 2015. No such luck.
https://en.wikipedia.org/wiki/Gopher_%28protocol%29
There are probably people reading this who were born well after Gopher's heyday.
https://en.wikipedia.org/wiki/Gopher_%28protocol%29
There are probably people reading this who were born well after Gopher's heyday.
I'm not sure what the first step should be (well, other than setting up a gophersite, reading the RFCs and looking at some implementations), but given that it maps very well to a hierarchical file system, you could position it as a bookmarking tool or something of the sort.
Or you could create an easy way for people to set up their own phlogs and discover others. Position them as convenient alternatives to static site generators while emphasizing Gopher's traits.
Either way, it needs to capitalize on people's discontent with web bloat in some way.
Really? Any evidence to support this? I'm curious.
Start it, point it to a directory, just upload markdown files and you are up and running. A few simple rules to follow (like the file _info containing a short directory description, some files not being shown on the directory list). Just for getting shit online.
Something like that "motherfuckingwebsite" that gets passed around, but with a simple navigation.
https://httpd.apache.org/docs/2.2/mod/mod_autoindex.html#hea...
There is probably a way to combine modules to get it to render markdown in place of HEADER.html