summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrederick Yin <fkfd@fkfd.me>2023-12-15 00:15:18 -0500
committerFrederick Yin <fkfd@fkfd.me>2023-12-15 00:15:18 -0500
commitb498863206dbaa157b162467ec3dbd854b5530db (patch)
tree216ac8ec9e5e1b322641acb4ba31d9aa38fbd88f
parentc9a1f63e2a7c96b8d5cb5cc4dad364a86a6e2ebd (diff)
random/xkcdbot: 2023-12-15 update
-rw-r--r--docs/random/xkcdbot.md9
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/random/xkcdbot.md b/docs/random/xkcdbot.md
index ef6e0cb..48d75ff 100644
--- a/docs/random/xkcdbot.md
+++ b/docs/random/xkcdbot.md
@@ -2,7 +2,7 @@
First version 2022-11-29
-Updated 2023-10-25
+Updated 2023-12-15
![A Mastodon post with comic number, title, title text, xkcd.com URL and
explainxkcd URL; a reply below reads "Heads-up for my subscribers:" then
@@ -131,7 +131,10 @@ xkcdbot and provide alt text with Mastodon's edit feature.
I had intended to send a PGP-encrypted email, but Sam does not have that
or any E2EE. So after consideration, I committed the cardinal sin of
-cybersecurity: I sent him the password in plaintext via email.
+cybersecurity: I sent him* the password in plaintext via email.
+
+_i realized later that he/him might not be the best pronoun but they said
+they're okay with any. i really oughtta be careful next time_
Say what you will but a bot that posts comics is just too trivial for
a lecture on asymmetric key cryptography. Like sure a hacker could get
@@ -145,3 +148,5 @@ access to the bot. Now what? They lock me and Sam out of it?
I will now contact botsin.space's admin to know if we can recover the bot
in case that happens, but I doubt it ever will.
+
+Update same day: Colin (botsin.space admin) said yes 🔥