Okay, so now for some interesting news that may make some cringe. I
was told by some sources that this is the place to go if I want to
discuss additions to the "Gopher Protocol" standard. Well, this
evening, I built a proof of concept new Gopher type. I am really
hoping that we can all work together to make this the newest Gopher
type in years! This new Gopher type fits Gopher so well that it would
be stupid to not include it in the Gopher standard for for clients to
actually support it. Have you ever heard of this little markup
language called "Markdown"? It's a very simple, but powerful markup,
and it's used on lots of programming and documentation websites. If
you use GIT, then you most likely store your README file in Markdown
format. Wouldn't this format fit in with Gopher's overall goal?
Markdown is very lightweight, and looks good with or without being
processed. I see some Gopherholes trying to use HTML, and I'm like...
REALLY!!! Markdown would suit these types of documents better,
especially when it comes to text-based or low end device clients.
Markdown has the advantage of looking great, but still takes little
bandwidth and looks nice in plain text too.
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project