Neal Wilson ✅ @neal@social.typica.us

Wow, I just got text spam pretending to be voting information giving me the correct polling location, but the wrong date. Looks like someone doesn't want me to vote. (I'm totally going to vote.)

Lap cat is lap catting.

Closed out a few of my coffee contracts today. Next shipment is all just more of the exact same lots as I've had previously so there's no product development work to do with that unless testing the first batch reveals something weird happened in storage, which for this supplier is not something that I'm seriously concerned about, but it's a possibility and I'd be doing the testing anyway.

Today's dreams included a 1970s style cartoon that could have been used as marketing for PETA. I noped out of that one pretty fast and traded it in for some artsy thing in which a lady knocks at the door and hands an envelope to the person who answers. The envelope is opened and inside is an HTTP request. The lady is then allowed in and ends up walking through a forest in like a magical princess type dress. Both of those were new.

Today's spam includes a message from a South African email address trying to phish access to my non-existent account at some cryptocurrency exchange. It was not a very convincing fake even if I did have the account they were trying to scare me about.

The secret to setting records in video games is to go for oddly specific ones that nobody else is competing for. I recently decided to see how much physical damage I could get out of Qiqi, or more specifically, the passive damage that Aquila Favonia deals when Qiqi takes damage. This is the best I could manage. I can't find evidence that anybody else has done better from this very specific damage source, but would love to see that if it exists.

I won a prize in an in game photography contest with this post containing some accurate yet questionable puzzle solving advice: https://www.hoyolab.com/article/15193037

Mom sent a tech support request. Says her television isn't working right which for her really could mean just about anything, so I'll be trying to sort that out after work.

Roasting demo went well. Lots of good questions. People seemed engaged. Probably not what they expected going to a poetry jam, but it was fun and some of the poetry was pretty good too.

Doing a little combination lecture coffee roasting demo tonight. I'd agreed to it as a fun little community event but yesterday I learned that I'm also getting paid for it, so that's a nice bonus.

Today in odd tasks: someone brought in some coffee they bought from me a couple months ago and wanted me to mail it for them. It's not any cheaper for them to have me do it instead of just taking it to the post office (and it's more expensive than if they had just placed the order through the web site and had me mail it while the coffee was still fresh) but sure, I'm dropping other stuff at the post office anyway so I can do that if that's what they really want.

Got confirmation that the issue was indeed that the unit got flipped to oz which means inventory was only being updated by 1/16th of the truth. I appreciate when people who ask me for help let me know if the advice did or didn't work.

Put my tech support hat on. Don't know if this is the solution, but my current best guess based on the screenshot is that they didn't notice that their unit had gotten switched to oz when they wanted it to be lb.

I think I'll throw something together and mess around with that soonish.

The way you'd use this is scan over until you see significant divergence. If that's happening at a low enough temperature closer to the right side of the graph, you're probably fine, if it's happening at higher temperatures closer to the left side you'll probably taste the difference.

The idea here is that what's happening at the end of the roast is generally more important than what's happening at the start. It's conceptually similar to the profile translation analysis that I've advocated for over the past couple decades, but doesn't require picking out significant temperature ranges in advance (plus there's no reason you can't do both if you want to go for the deeper analysis).

Had a thought while roasting coffee today and I don't know if there's anything to this, but I'm just going to throw it out there, but as a tool for comparing data from multiple batches after they're finished, what about doing an x axis that's end time minus time. That would align everything at the end of the batches instead of at the start.

I feel like today is going to require a lot of espresso.

Today's coffee roasting was interrupted by roaster repair. Somehow the tube connecting to the vacuum sensor managed to disconnect itself which shut off the gas mid-roast and didn't allow the gas to turn back on until that was fixed, which is the right behavior for a safety system like that.