From 847c480dcd600a9396b81a9573292ac42f39d6d1 Mon Sep 17 00:00:00 2001 From: Frederick Yin Date: Wed, 25 Oct 2023 11:53:18 -0400 Subject: random/xkcdbot: behold - Sam Levine --- docs/random/xkcdbot.md | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/docs/random/xkcdbot.md b/docs/random/xkcdbot.md index 7b5735f..ef6e0cb 100644 --- a/docs/random/xkcdbot.md +++ b/docs/random/xkcdbot.md @@ -2,7 +2,7 @@ First version 2022-11-29 -Updated 2023-10-22 +Updated 2023-10-25 ![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 @@ -123,3 +123,25 @@ a matter of community. I admit I cannot solve it by myself. Therefore, I am going to ask for the community for help. To be continued. + +## Update (2023-10-25) + +This is fire! I reached out to Sam Levine, who agreed to co-maintain +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. + +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 +access to the bot. Now what? They lock me and Sam out of it? + +- If they violate the TOS, we can certainly report it +- If they make it obvious that the account's been hacked, people would + know +- If they don't, they are impersonating us, which is pretty impressive + given they are doing two people's jobs in one + +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. -- cgit v1.2.3