From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] ipso: read keys from stdin
Date: Wed, 1 Sep 2021 22:42:07 +0100 [thread overview]
Message-ID: <2974A5D9-3B0C-4F43-B477-6EE1C6DD6124@quintile.net> (raw)
In-Reply-To: <9FC46F3B1F0981A3E325246D34DB1545@eigenstate.org>
as an an alternative you could extend to secstore’s protocol with an append message.
it might be cleaner than ipso’s read,modify,write.
-Steve
prev parent reply other threads:[~2021-09-01 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 1:37 ori
2021-09-01 21:42 ` Steve Simon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2974A5D9-3B0C-4F43-B477-6EE1C6DD6124@quintile.net \
--to=steve@quintile.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).