I found a note to myself that I should post about my per-host colors. I don’t know whether it’s of general interest to whoever reads this thing, but I guess I thought that once, so here we go.
When I bought my Nanoleaf panels, which I wrote about in my previous two posts, I didn’t realize that they’re not just programmable lights. They’re also touch sensors. Or so they claim! The truth is, I haven’t been able to use the touch interface reliably. This post will recount my efforts.
In my last post about Nanoleaf, I ended by saying that I wrote a program to light up each panel a different color, to help me pick out which panel had which panel id. I also said that I didn’t make that program using the custom animation API. It’s true! I used the streaming interface. I actually got that going before the custom animations. It felt like what I’d want: a way to send a never-ending stream of instructions doing something like tracking log events or keystrokes or I don’t know what.
For my birthday, some family sent me a $200 gift card for Amazon. I wasn’t sure what I’d like. I have too many books queued up already, and just sort of enough stuff. I knew there’d be some toy or luxury that would be a good pick, but nothing sprang to mind. I mentioned this conundrum to Rob N, who said “Why not Nanoleaf?”
my stupid CPAN “meta analyzer” (again)
Email, indexing, and error reporting
In past years, one of my big areas of work at PTS has been PAUSE. If you’re not a CPAN wonk, here’s a tiny explainer: PAUSE is the Perl Author Upload SErver. It’s where you go to upload new software to the CPAN, and to manage the permissions on packages for which you’re the administrator. It’s got a number of interrelated pieces, but the two easiest units to describe are the web interface and the indexer.
Ten years ago, the “toolchain gang” who manage the libraries most central to deploying and testing CPAN libraries came to an agreement on the minimum supported version of perl. Nobody needed to keep maintaining v5.6, and everyone who hadn’t already, moved to v5.8. That was ten years ago, but the toolchain was still pinned to v5.8. I am not enthusiastic about targeting v5.8, and have written about this before. I bumped some modules to v5.12, earlier this year. I got some feedback, both positive and negative, but I felt good about it.
It’s been three years since the last Perl Toolchain Summit. In 2019, I wasn’t sure whether I would go. This time, I was sure that I would. It had been too long since I saw everyone, and there were some useful discussions to be had. I think that overall the summit was a success, and I’m happy with the outcomes. We left with a few loose threads, but I’m feeling hopeful that they can, mostly, get tied up.
I ignored Mastodon for a long time, but eventually I had to stop. Now that I stopped ignoring it and started using it, I feel like I’m either going to lose interest or (ugh) get involved.