1 new of 79 responses total.
Let me be clear what I mean: I *personally* don't want to put a lot of time and effort into supporting Gopher, but I'm certainly willing to take content and marshal it over into the gopher area, make changes to the server, etc. If folks use gopher, and most importantly if it becomes a draw that pulls people into Grex then I'm fine with it. If it doesn't, then I'll take it down (it is, after all, yet another unencrypted service running on Grex that could become a security issue). But if no one is using it, then no one will notice. :-) I'd be slightly more enthusiastic about a low-markup set of static blog web sites, to be totally honest. Gopher as a protocol is a lot less interesting. A gopher-style thing via HTTP, with minimalist content (a la Markdown) that's directly interpreted in lieu of HTML is a lot more interesting.
You have several choices: