RFC: TinyLogs format

Status: Draft

Last update: 2021-07-05

=> https://codeberg.org/bacardi55/gemini-tinylog-rfc

Introduction

A Tinylog is a simple file with all "microblog" style entries to share small contents and interact with other geminauts' tinylog.

The original idea and most "rules" comes from Drew/uoou/Friendo [1]:

=> [1] gemini://friendo.monster/log/lace.gmi

The goal of this RFC is to standardize the tinylog format for better coherence between authors by providing a consistent approach.

This will also allow better tools around tinylogs to improve both authors and readers experience reading micro entries.

Tinylog format

This tinylog format proposal is composed of a mandatory part that tinylogs must be compatible with and optional information that author could add as meta information about their tinylog.

Mandatory format

Each tinylog entry must be formated as follow:

## 

It starts with a second level header (##), followed by a space and then <date>.

=> gemini://gemini.circumlunar.space/docs/companion/subscription.gmi [2] gemini://gemini.circumlunar.space/docs/companion/subscription.gmi

YYYY-MM-DD hh:mm TZ

• A timezone abbreviation [3] like UTC, CEST, ET, BST, …
• A valid UTC offset (eg: +02:00 for CEST, -06:00 for ET, …).

=> [3] https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations

Note: Timezone abbreviations are not standards (eg BST is an abbreviations of 3 different timezone). For better comprehension for any tools, the UTC offset is usually better.

If the timezone is not precised, UTC should be assumed.

Entries should be in order from newest to oldest.

Each entry must be separated with 2 new lines (ie paragraph break).

Example:

2021-06-20 20:40 +0200

A small thought to share.

2021-06-20 20:30 CEST

A first tinylog entry

### Optional Header information

Additional informations could be added at the top of your tinylog file:

author:

avatar:

licence:

Example:

author: @bacardi55
author: @bacardi55@gmi.bacardi55.io

Example:

avatar: 🦪

avatar: 🦪 (:oyster:, U+1F9AA)

Other additional metadata could be added but shouldn't be expected.

Optional response information

It's common in the gemini world to respond to a particular entry of an author. In that case, author should add a line below the header line with formatted

[=> linkToOriginalEntry ]RE: @author[@capsule.tld] 

The link to the original entry (and thus the => prefix) are optional.

Note that the Re part is case insensitive, which means either one of Re, RE, re, or even rE can be used.

Example:

## 2021-06-20 22:30 CEST
=> gemini://capsule.tld/tinylog.gmi Re: @user 2021-06-20 22:30 CEST
A response to @user: hello, cool post!

## 2021-06-20 22:30 CEST
=> gemini://capsule.tld/tinylog.gmi Re: @user@capsule.tld 2021-06-20 22:30 CEST
A response to @user: hello, cool post!

## 2021-06-20 22:30 CEST
Re: @user 2021-06-20 22:30 CEST
A response to @user: hello, cool post!

## 2021-06-20 22:30 CEST
Re: @user@capsule.tld 2021-06-20 22:30 CEST
A response to @user: hello, cool post!

It will be up to the client to decide whether to use this information or not.