From: Jeremy <jlrubin@mit.edu>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] [Bitcoin Advent Calendar] A Defense of Having Fun (and maybe staying poor)
Date: Tue, 14 Dec 2021 10:37:59 -0800 [thread overview]
Message-ID: <CAD5xwhj9SYwBK9J-K8W0wAnSQuT9e165W=k+=+ik8_ddrPPPFA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
Hi Devs,
Today's post is a little more philosophical and less technical. Based on
the private feedback I received (from >1 persons, perhaps surprisingly)
I'll continue to syndicate the remaining posts to this list.
Here it is: https://rubin.io/bitcoin/2021/12/14/advent-17/
To having a little fun every now and again, as a treat,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
[-- Attachment #2: Type: text/html, Size: 1705 bytes --]
next reply other threads:[~2021-12-14 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 18:37 Jeremy [this message]
2021-12-23 14:09 [bitcoin-dev] [Bitcoin Advent Calendar] A Defense of Having Fun (and maybe staying poor) Prayank
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='CAD5xwhj9SYwBK9J-K8W0wAnSQuT9e165W=k+=+ik8_ddrPPPFA@mail.gmail.com' \
--to=jlrubin@mit.edu \
--cc=bitcoin-dev@lists.linuxfoundation.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