What if... we had Markdown as a first-class citizen of Geminispace?


I'm feeling a bit conflicted about this, but ultimately it's up to you to decide which format suits your content the best.

@jk this scares me, especially in lagrange which seems to have the largest client following. I'm glad you're limiting the set of decorators you're allowing and not including things like inline links, but oof, it's scary.

Markdown basically is HTML, as you point out. Once that nut gets cracked open we have to face the question, "does content in mime-types other than text/gemini allow for nested requests?" Does the image pre-load in Markdown? And if that happens, is there any functional difference between Gemini and HTTP? Yes, there's a slippery-slope argument and that's a fallacy, but in this particular case I think we are literally dealing with a slippery slope.

You're dipping your toe into it for richer text formatting. It's something people have talked about before. Clients were bound to do it eventually. I dunno... it's just scary.


@tomasino It’s good to be careful here for sure.

One should not conflate page content and the protocol, though. A richer-formatted page is still served over Gemini, with its single request rule and no preloading. Even HTML can be used outside the context of a full-blown web browser, although I’m not sure anyone would want that.

IMO the biggest danger is fragmentation. If people don’t see the value of standard Gemtext as the glue that holds Gemini together, the community splits apart.

@tomasino In any case, I’m not planning to rush into adding non-Gemtext-based document formats to Lagrange. There are more important short/medium-term things to take care of, and there is also a maximum size for the code base that makes sense for a single developer.

Sign in to participate in the conversation

skyjake's personal Mastodon instance