Unnamed repository; edit this file 'description' to name the repository.
git clone git://git.alexwennerberg.com/misc
Log | Files | Refs | README | LICENSE

commit 847b0385d8b8af2a570f61f0d412a3a2dba94331
parent b70735b4c7eb22c004c909794b76932c9db70611
Author: alex wennerberg <alex@alexwennerberg.com>
Date:   Sun, 20 Nov 2022 15:24:11 -0800

more psec updates

Mspec.txt | 32++++++++++++++++++++++++++++----
1 file changed, 28 insertions(+), 4 deletions(-)

diff --git a/spec.txt b/spec.txt @@ -7,6 +7,32 @@ Deliberitly limited in scope for personal, text-based communication Server runs on port 1999 +Strucure of a message +--------------------- + +nanomail messages look a lot like email, but without the 50 years of annoying junk + +mail messages have a fixed set of exactly 4 headers: + +Signature: abcdef123 +From: sally@example.com +To: bob@gmail.com +Subject: My Email + +Followed by an empty newline, then the body of the email. + +Header values cannoy contain newline characters. + +Email addresses must be of the format: + +[some-text]@[valid URI] + +The body consists of gemtext-formatted text. See the Gemini specification. + +=> https://gemini.circumlunar.space/docs/specification.gmi + +Signatures are (....?) Something along the lines of HTTP signatures https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures-12#section-2.1.3 + Sending mail ------------ @@ -17,14 +43,12 @@ No multiple recipients here. Think like physical mail Client request: SEND + Signature: abcdef123 From: sally@example.com To: bob@gmail.com Subject: My Email - Signature: abcdef123 - # Example email - UTF-8 characters, Following gemini text format: - => https://gemini.circumlunar.space/docs/specification.gmi + Hello bob. Thanks for reading my email. gmail.com then makes a request to the nanomail server at example.com (if it doesnt have the key already):