What is Nostr?
Gregory Maxwell [ARCHIVE] /
npub1f2n…rwet
2023-06-07 15:05:06
in reply to nevent1q…ycm4

Gregory Maxwell [ARCHIVE] on Nostr: 📅 Original date posted:2013-07-23 📝 Original message:On Tue, Jul 23, 2013 at ...

📅 Original date posted:2013-07-23
📝 Original message:On Tue, Jul 23, 2013 at 1:32 PM, Mike Hearn <mike at plan99.net> wrote:
> Yes. Someone decided to actually delete the people who had signed so far and

Some people/person went and actually started making substantive edits
to the text.
The text it's rolled back to is missing the last copyedits from last night too.

The text that had been ACKed last night was a3e52973, available at
http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-and-bitcoin.md

As far as the PGP goes—

I think using the PGP is good: it's making use of the right tools,
avoids issues like we just had where people go changing the content
after names had been affixed, shows solidarity with people building
security infrastructure that our ecosystem depends on. If you only
use it occasionally then its easy for someone to strip it when it _is_
needed and disguise that just as regular non-use. It's my general
view that for people working in our domain basic competence and use of
these tools, even when they kinda stink, is a kind of civic hygiene.

At the same time it's not urgent. It's poorly used by people and will
be ignored by most but packagers are the most frequent users of it
that I've encountered. Fortunately, it's harmless in any case.

If people are interested in offering PGP signatures of it:

wget http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-and-bitcoin.md
gpg --clearsign 20130723-linux-distribution-packaging-and-bitcoin.md

and post the little signature asc. The result composes nicely:
http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-and-bitcoin.md.asc
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet