2016 Nov 30, 1:16
Twitter is 1984 two minutes hate
2016 Nov 28, 10:07 2016 Nov 28, 6:19 2016 Nov 28, 12:33
Context:
2016 Nov 20, 10:41 2016 Nov 20, 2:47 2016 Nov 18, 4:11
@PA_Megacorp I read the title as Couchomancy and imagined a necromancer that summons couches. No one steal my new YA fantasy
novel idea pls
2016 Nov 17, 3:14 2016 Nov 6, 1:17
@ericlaw Very fitting for the show but... those serifs. Aspects of 80s aesthetic I can do without include: wood paneling on
cars, that font.
2016 Nov 5, 8:59
Since I had last posted about using Let's Encrypt with NearlyFreeSpeech, NFS has changed their process
for setting TLS info. Instead of putting the various files in /home/protected/ssl and submitting an assistance request, now there is a command to submit the certificate info and a webpage for
submitting the certificate info.
The webpage is https://members.nearlyfreespeech.net/{username}/sites/{sitename}/add_tls
and has a textbox for you to paste in all the cert info in PEM form into the textbox. The
domain key, the domain certificate, and the Let's Encrypt intermediate cert must be pasted into the textbox and submitted.
Alternatively, that same info may be provided as standard input to nfsn -i set-tls
To renew my certificate with the updated NFS process I followed the commands from Andrei Damian-Fekete's script which depends on acme_tiny.py:
python acme_tiny.py --account-key account.key --csr domain.csr --acme-dir /home/public/.well-known/acme-challenge/ > signed.crt
wget -O - https://letsencrypt.org/certs/lets-encrypt-x3-cross-signed.pem > intermediate.pem
cat domain.key signed.crt intermediate.pem > chained.pem
nfsn -i set-tls < chained.pem
Because
my certificate had already expired I needed to comment out the section in acme_tiny.py that validates the challenge file. The filenames in the above map to the following:
- signed.crt is the Let's Encrypt provided certificate
- account.key is the user private key registered with LE
- domain.csr is the cert request
- domain.key is the key for the domain cert
certificate lets-encrypt nearlyfreespeech.net 2016 Nov 4, 4:08 2016 Nov 4, 4:05 2016 Nov 4, 1:48
@JenMsft Your tip weets should show as toasts for all win10 users
2016 Nov 3, 3:59
@FakeUnicode Spaces are technically not allowed in a URI so the only reasonable representation is percent encoded.
2016 Nov 3, 3:58
@FakeUnicode Reserved characters including brackets change meaning when decoded or encoded and so UA must not change those
2016 Nov 3, 3:57 2016 Nov 2, 1:38
I'm not begrudging anyone who's following this; I'm literally getting all my info about this from Twitter, which is hilariously incomplete.
2016 Nov 2, 1:16
@osterman @ericlaw 'CLR cooks' I assume means you get the .NET projection of the WinRT
APIs? That's good enough for most of my purposes.
2016 Nov 2, 9:30