News for hackers. Stuff that matters.

A comment on The Gemini protocol as seen by curl maintainer. Parent comment

Re:The Gemini protocol as seen by curl maintainer by ilyt on Sunday May 28, 2023 @02:31PM (#36106528)
Right but if you want simple why not "just" use markdown (with maybe HTML support cut off?). Why make something subtly-similar-but-incompatble ?

If you want protocol to be light and low on bandwidth, why would you not include at least the simplest of caching semantics ?

It is just bad design decision after bad design decision

[ Parent | on HN ]
Re:The Gemini protocol as seen by curl maintainer by halicarnassus on Sunday May 28, 2023 @04:36PM (#36107523)
Markdown is not context-free and therefore hard to parse.

Caching can be abused for tracking.

That's why both are solutions to the problems the Gemini project is trying to solve.

[ Parent | on HN ]
Re:The Gemini protocol as seen by curl maintainer by halicarnassus on Monday May 29, 2023 @02:17AM (#36111237)
I meant to wrote "That's why both are solutions to the problems the Gemini project is trying to solve." m(
[ Parent | on HN ]
Re:The Gemini protocol as seen by curl maintainer by ertian on Sunday May 28, 2023 @05:31PM (#36107983)
Why not? Why is it necessary to use existing approaches, even if they add a lot of incidental complexity? What does it hurt you that Gemini has their own custom markup language that's different than Markdown? You can set up your own little Markdown HTTP server, they're not stopping you.
[ Parent | on HN ]
Re:The Gemini protocol as seen by curl maintainer by vitiral on Sunday May 28, 2023 @08:12PM (#36109108)
Markdown has loads of bad design decisions for writing a parser... or being the (human) parser.

I've made an attempt to do better, it may be illuminating: https://github.com/civboot/cxt

[ Parent | on HN ]