2 ms·

See 2.5: https://gemini.circumlunar.space/docs/faq.gmi https://gemini.circumlunar.space/docs/faq.gmi Not sure how a subset would work in practice. Though I can

by tjoff 5y ago

See 2.5: https://gemini.circumlunar.space/docs/faq.gmi https://gemini.circumlunar.space/docs/faq.gmi Not sure how a subset would work in practice. Though I can imagine a javascript gemini client (as perverse as it sounds...) that could be used as a tunnel into the gemini world in cases where you just want to look something up quickly and/or don't have or want to install a proper client

coffeecat 5y ago
> Not sure how a subset would work in practice. What I'm imagining is a specification, defining which subset of HTML should be included, together with a <meta> tag which indicates a document's intention to be compliant with the standard.
- encryptluks2 5y ago
  I'm imagining some form of YAML or similar frontmatter and markup. A lot of markdown extensions really add a lot of value. Like graphs, admonitions, diagrams, presentations, tabs, mindmaps, etc. I am not particularly fond of XML. I remember liking some of the ideas behind Pug/HAML etc and wished that a browser would just render it natively.
  - MaxBarraclough 5y ago
    > I'm imagining some form of YAML or similar frontmatter and markup It sounds like you're expressing disagreement with Gemini's chosen feature-set, but the question being discussed here is whether it would make more sense to use a subset of HTML rather than an incompatible format. The point of using an HTML subset would be to retain compatibility with conventional heavyweight web-browsers. A feature-rich YAML-based scheme would be neither minimalistic, nor natively web-compatible.
- tjoff 5y ago
  Yes, but how would it be enforced? Just slap on that gemini-tag and pretend to be compliant but continue using all the shady techniques of the modern web. If most users would end up browsing gemini with a regular browser that sort of thing would be commonplace.
kevin_thibedeau 5y ago
No more perverse than the current state of affairs where you have to run JS to retrieve text content, generate hyperlinks, and image URLs.

by tjoff 5y ago

coffeecat 5y ago

> Not sure how a subset would work in practice. What I'm imagining is a specification, defining which subset of HTML should be included, together with a <meta> tag which indicates a document's intention to be compliant with the standard.

encryptluks2 5y ago
I'm imagining some form of YAML or similar frontmatter and markup. A lot of markdown extensions really add a lot of value. Like graphs, admonitions, diagrams, presentations, tabs, mindmaps, etc. I am not particularly fond of XML. I remember liking some of the ideas behind Pug/HAML etc and wished that a browser would just render it natively.
- MaxBarraclough 5y ago
  > I'm imagining some form of YAML or similar frontmatter and markup It sounds like you're expressing disagreement with Gemini's chosen feature-set, but the question being discussed here is whether it would make more sense to use a subset of HTML rather than an incompatible format. The point of using an HTML subset would be to retain compatibility with conventional heavyweight web-browsers. A feature-rich YAML-based scheme would be neither minimalistic, nor natively web-compatible.
tjoff 5y ago
Yes, but how would it be enforced? Just slap on that gemini-tag and pretend to be compliant but continue using all the shady techniques of the modern web. If most users would end up browsing gemini with a regular browser that sort of thing would be commonplace.

kevin_thibedeau 5y ago

No more perverse than the current state of affairs where you have to run JS to retrieve text content, generate hyperlinks, and image URLs.