Today, I finally got a FIDO2 ssh key working. (Next step is to make sure I can use it from more than one client machine.)

I have lost track at this point of the number of different ways I've failed to do so. I'm pretty sure "nah, I don't feel like doing this tonight after all" has beaten all others combined.

I think the funniest failure might have been the time I realized that the OpenSSH client I was using, while it did have a version number newer than when the feature was added...had support for it explicitly disabled because the dependencies weren't available for the platform yet.

I have decided to post a list of a few blog articles I'm considering writing soon. This is partly as a memory aid for myself about what I was thinking I might write, partly to see how posting a Question works while I'm at it, and a very little bit to ask the question: Anyone out there actually look forward to seeing any of these?

Note: The one about Microblogpub might end up so broad-ranging that even I think it ought to be broken down into more than one article. On the other hand, it might end up far shorter than I think it will.

What this is not is a commitment that I will necessarily follow through on any of these ideas, tackle any of them in any particular order, or refrain from writing about something else in the meantime; I'm almost positive I had another idea that was going to make the list and then forgot it while I was revising the Microblogpub line.

Anyhow, keep your expectations limited...A little over a year ago I thought I might try to post 100 articles over the course of 2023. I posted three.

P.S. To anyone who saw this twice, I apologize. Apparently when I had to refresh the form for writing it I forgot to set the duration back to one day instead of five minutes...

...And we're back.

(What? What do you mean back?)

So...what happened, as best I can tell, is that around September 9-10, another application running on my server ran into a bug that caused it to exhaust all available disk space recording far too rapid retries to the syslog.

Unfortunately, in my first attempt to figure out what had gone wrong, I was ...kind of sleepy, and got to the point of "Well, maybe I should just rebuild the instance with a larger boot volume" before I reached the point of noticing the 24GB of syslog - mainly because I thought the problem would turn out to be something else I'd already been worried about - and I wound up losing the instance reservation and having to wait until capacity was available again in order to bring it back online.

I suspect that a lot of instances gave up on sending posts to me while my server was unreachable...I wonder whether they'll just start again or if there'll be a Hassle involved.

It's getting to be that time of year again. The time of year when I might work up a sweat from doing something like, say, standing still outdoors for a few minutes.

#andstatus seems to work pretty well with #microblogpub these days. The result of trying to post with "public" checked but "followers" unchecked seems to be "direct," which I think may make sense but was not what I had guessed.

Today marks one month since I got my site/instance set up and made my intro post, and I want to make sure I post something today. (Actually, if I'd posted before I went to bed, I could have hit that one month pretty much on the minute.) However, I am not sure I'm actually going to get any of the things I want to write next fleshed out enough to be ready to post them tonight, so I decided to post a quick list of what I'm planning to work on or write about:

• https://bringback.blog, whether I qualify, and whether I'm participating
• 100days projects, 100DaysToOffload specifically, and whether I'm going to do such a thing
• Terminology quirks between the Fediverse and the Indieweb, and how they and the way microblog.pub works make me go "huh"
• Follow-up the first: Why that makes me feel like I need a convenient way to post something that is public, but doesn't hit my followers' timelines
• Follow-up the second: How that means I think I should try to interact with other people who do both Fediverse and Indieweb stuff
• Bonus: Why can't my instance seem to interact with Tantek's fediverse presence? Is it because I'm doing something wrong, and can I fix it?

#science: giving bees jet lag (and treatos)

I saved the holidays and stopped the villain! holidayhackchallenge.com Don't miss out on SANS #HolidayHack x @KringleCon https://holidayhackchallenge.com

All right, settled in for the evening...as soon as I finish running some updates, it's time to see how much more of #HolidayHack I can finish. I might have to come back to this fountain thing.

Tweaks to my site in the last couple days:

• My Articles page was already marked up as an h-feed, but because the links to the posts were not marked up as h-entry it appeared empty. I remedied that and submitted an issue to the dev.
• I added <link> so that, at least in theory, I can now support old-fashioned pingbacks by having webmention.io forward them to me as webmentions.
• Tracked down why, when I try to start composing a reply and one of the actors in the thread is a profile I can't retrieve (such as because their instance uses a whitelist I'm not on), I get a 500 error; wrapped the offending attempt to add them to the "@" list in a try and, for now, just drop them from the list, the same way the instance where my other account lives seems to do it. Submitted an issue for that too. (I might investigate later what happens if I try to leave the @-mention in place even though the lookup failed.)
• Implemented a config toggle (not sure why I bothered to make it a config toggle; maybe I think other people might like it eventually?) to change the object IDs of posts from being a hex representation of a UUID to being a NewBase60-encoded...well, unix timestamp divided by 60, because I wanted resolution to the minute. Why? Because I have a few edge cases I think I might come across eventually in which I want to work around the fact that I can't easily edit my posts by predicting a permalink in advance. I may remove the division by 60 eventually, because I am pretty sure I generate one of those IDs for everything I do, and therefore I now can't post two things within the same minute. That might not sound like a big deal given how long my notes are (no, I can't type this much in under a minute), but the ID in question is also used as the ActivityPub ID of the action, so it applies - I'm pretty sure, and have tested at least one combination - to likes, shares, and so forth as well. By comparison...well, I suppose I might try to like and boost something within the same second, but not often. Anyhow, I'll see how it goes - the other nice thing about it is that as far as I can tell, since the IDs were already just something standing in to be unique, I can switch it up whenever I like and it just affects my posts during the time I have that configuration active. Come to think of it, I should make it configurable whether it uses seconds or minutes. Maybe tomorrow.

So there's just one problem, from my perspective. Which is that before I decided to muck around with all that, I had meant to use this weekend to work on the #holidayhack, because I thought I might actually try to submit my write-up this year...