2021-10-16

Complexity or Do NOT mark it down, please!

=> #gemini
=> #complexity
=> #grumpy

The discussion is back. And it makes me grumpy.

=> gemini://skyjake.fi/gemlog/2021-10_mark-it-down.gmi | local copy | gemini://skyjake.fi/gemlog/2021-10_re-mark-it-down.gmi | local copy

2021-10-14 Datapulp : Re: Mark It Down

=> gemini://blog.datapulp.de/re-mark-it-down | local copy

2021-10-14 gerikson: Re: Mark It Down

=> gemini://gerikson.com/gemlog/misc/Re-Mark-It-Down.gmi | local copy

2021-10-14 Idiomdrottning: Re: Mark It Down

=> gemini://idiomdrottning.org/re-mark-it-down | local copy

2021-10-15 Alex Schroeder: 2021-10-15 Re: Mark It Down

=> gemini://alexschroeder.ch/page/2021-10-15_Re%3A_Mark_It_Down | local copy

2021-10-15 hari: Re: Mark it down

=> gemini://harrison.cafe/re-mark-it-down-do-not-use-unicode | local copy

2021-10-16 Teiresias: A Bit about my Gemini Stack

=> gemini://the-brannons.com/gemini-stack | local copy

2021-10-16 Idiomdrottning: Gemini Ain't Broke

=> gemini://idiomdrottning.org/gemini-aint-broke | local copy

These I picked off Antenna, I'm sure there's more.

Because we can?

Why not use markdown instead of gemtext? Why not make gemini servers serve several different layouts like gemtext AND markdown AND $fancy_new_format as well? Because we can? A few things were actually put into action on this very planet because we can, nuclear bombs being just one of them. Another being the mess called Internet.

In a very different context I wrote:

While curiosity might kill a cat here and there, it is my firm believe, that complexity will kill us all some day.

=> gemini://ew.srht.site/en/2021/20210811-power-outage.gmi

And today I would add: apparently rather sooner than later.

Well, maybe we'd rather not!

The gemini protocol is simple enough to write a server in any old language --- except for the tls/cert bit. But even that can be outsourced to a component suitable for it (as demonstrated by vger/relayd setup). Gemini Text is simple enough that I can write a parser for it in an afternoon. And I would definitely prefer that it stays that way.

What exactly makes gemini space better if we /add/ complexity?

So: If you, the author, want control over the presentation of your content, by all means, use something adequate. Create .pdf files or whatever and host them on several protocols, if you desire so. But please, do not try to make gemini/gemtext any more complex.

In my not so humble opinion:

• Do not add complexity to gemtext --- like inline bold face or /italics/ or even => links. I highly appreciate that I can read the source just as well.

• Do not add complexity to the gemini server side --- like adding multi-formatted content on the fly services. The server can serve any file if requested.

• Do not add complexity to the gemini client side --- like rendering markdown and what not. The client can route any funny content to a viewer outside of itself, if so desired.

• Do not add unneeded complexity by using unicode characters, which are just another glyph of the same character --- see the techrights thing for an example:

=> gemini://ew.srht.site/en/2021/20210411-upd-re-your-gemlog-may-not-be-accessible.gmi

• For applications be sure to read solderpunks vision of how it can be done:

=> gemini://gemini.circumlunar.space/users/solderpunk/gemlog/a-vision-for-gemini-applications.gmi | local copy

• For simplicity consider to separate the handling of ssh/certficates/crypto from the gemini server component. I imagine simple sensor like things to answer in gemtext format to requests, inhouse, on my private network, without any need for transport layer security.

• And always remember: the text content is the important thing. Visually pleasing presentation will not make misinformation or bulldust inherently better.

• I shall consider to remove the html part of my capsule for simplicity. If I need to look at it, there is wobbly now. Thanks, Björn!

Cheers, and keep it simple!

~ew

=> gemini://warmedal.se/~antenna/ | https://tildegit.org/solene/vger | https://warmedal.se/~wobbly/

=> Home