💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › ydwnkla76h.fsf@UBEblock.ps… captured on 2022-03-01 at 15:56:03. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
From: Winston <wbe@UBEBLOCK.psr.com.invalid>
Subject: Re: FAQ: Project Gemini (minor edits)
Date: Fri, 03 Dec 2021 13:12:54 -0500
Message-ID: <ydwnkla76h.fsf@UBEblock.psr.com>
1 of 2 articles I'm reposting. I posted these so soon after the
newsgroup appeared on AIOE (while everyone was still trying to get other
sites to carry it) that they may have propagated poorly (or not at all).
This one is only about suggested minor edits to FAQ, so mainly of
interest to the FAQ maintainer(s).
I previously posted:
This followup suggests formatting fixes to the FAQ text.
[Yes, I saw that one can also use git to obtain the original and that
there's then a way to submit changes, but I don't feel like doing all
that at the moment...]
In section 2.8, the second paragraph is missing several sentence-ending
periods and is missing a paragraph break before 2.9:
Original:
> There are bindings to TLS libraries available for almost every programming
> language under the sun Many developers are already at least partially familiar
> with TLS and therefore don't need to learn anything new to implement Gemini
> Most users are already trusting TLS to secure their web browsing and email,
> and therefore don't need to decide whether or not they want to trust some
> unfamiliar technology to start using Gemini TLS is a deeply entrenched
> industry standard, whose definition and implementations will both continue to
> be scrutinised and improved by security experts for the foreseeable future,
> and that work will happen for reasons entirely unrelated to Gemini - it makes
> a lot of sense for a small project to "freeride" like this. 2.9 Why didn't you
> just use Markdown instead of defining text/gemini? The text/gemini markup
> borrows heavily from Markdown, which might prompt some people to wonder "Why
> not just use Markdown as the default media type for Gemini? Sure, it's
> complicated to implement, but like TLS there are plenty of libraries available
> in all the major languages". Reasons not to go down this route include:
Suggested:
There are bindings to TLS libraries available for almost every programming
language under the sun. Many developers are already at least partially familiar
with TLS and therefore don't need to learn anything new to implement Gemini.
Most users are already trusting TLS to secure their web browsing and email,
and therefore don't need to decide whether or not they want to trust some
unfamiliar technology to start using Gemini. TLS is a deeply entrenched
industry standard, whose definition and implementations will both continue to
be scrutinised and improved by security experts for the foreseeable future,
and that work will happen for reasons entirely unrelated to Gemini - it makes
a lot of sense for a small project to "freeride" like this.
2.9 Why didn't you just use Markdown instead of defining text/gemini?
The text/gemini markup borrows heavily from Markdown, which might prompt
some people to wonder "Why not just use Markdown as the default media
type for Gemini? Sure, it's complicated to implement, but like TLS there
are plenty of libraries available in all the major languages". Reasons
not to go down this route include:
Original section 3 header:
> 3. Getting started in Geminispace 3.1 I'm curious about Geminispace, how can I
Suggest adding a paragraph break:
3. Getting started in Geminispace
3.1 I'm curious about Geminispace, how can I [...]
Original section 4 header:
> 4. Contributing to the Gemini project 4.1 I like the sound of the Gemini
Suggest adding a paragraph break:
4. Contributing to the Gemini project
4.1 I like the sound of the Gemini [...]
[END]
-WBE
Parent:
Start of thread: