Supporting multi-line input without changing the specification
raingloom at riseup.net
Wed Feb 24 09:14:00 GMT 2021
On Tue, 23 Feb 2021 12:10:35 +0100
Solène Rapenne <solene at perso.pw> wrote:
> On 23/02/2021 11:56, Sandra Snan wrote:
> > avr wrote:
> >> a client that allows for normal edits but translates those into sed
> >> commands when updating the page
> > These kinds of suggestions are along the line of having a client
> > that supports translating *asterisks* to emphasis, translating
> > <font family="foo"> to a specific font family, and so on.
> > There's nothing stopping anyone from implementing that kind of
> > thing at any moment and if it's gets traction it'll get traction.
> > We're in a similar situation as what broke the pre-standards web.
> > There's not a lot me or anyone else can do about that so I don't
> > worry too much about it♫🐞
> > However, for sending text I recommend email.
> > Here's an idea for how a wiki in a world where spam didn't exist
> > could work:
> > You send email to an address. The text of the page at the path that
> > matches the subject of that email is then set to the body of the
> > email.
> > Whether that subject is "nice/orderly/unixy/path" or "Completely
> > bonkers with spaces that'll need to get percent-encoded and trunced
> > to match the 1024 limit."
> > If people want to edit they can paste the old text into their new
> > email.
> > This is just from the top of my head and not something I'd put into
> > production any time soon.
> there is nothing preventing users to publish markdown files instead
> of gemini files. On gemini, it's not mandatory to have everything as
> gemtext which would be reducing Gemini potential.
> Like it is often done in gopher, people can have gemtext files as
> menus with their texts files in markdown that could be opened with a
> nice markdown viewer program, and links with gemini:// scheme from
> the markdown file would be opened using the gemini client. That would
> be like using opening a PDF from a website and clicking on a link in
> the PDF :)
> The workflow may not seem optimal but it's perfectly doable with the
> current state of the protocol.
Could also just use a different protocol for (complex) editing. Maybe
export the source files over 9P.
More information about the Gemini