Just a bit of FOSS tinkering this morning. Badass: @Djuri has #bitaxe stats integrated into his #btclock project! More badder ass: Include the Bitaxe logo! @skot9000

If you live in LA long enough, you start recognizing people you know in movies and on TV. Started watching Skeleton Crew last night and was happily surprised to see that one of my friends was the first extra killed in the show! 🤣 And then only after seeing the credits did I realize that ANOTHER friend was in the same ep! Jack is a world-class juggler. Basically any time you see juggling in a Hollywood production, odds are pretty good that it's Jack. I should've known. OF COURSE he was the juggling holographic poodle!!! 🤣

NEAT! Real-time nostr zap notifications! First time seeing this flash live on the #btclock! Cool shit, @Djuri !

Last night's experiment: 40% whole wheat 3% flax 90g sun-dried tomatoes 60g shredded parmesan 2 sprigs of fresh rosemary Extras folded in after bulk ferment during pre-shaping. Tastes pretty dang good!!! But next time: * MOAR rosemary and parmesan. * Add the rosemary at the beginning. * Maybe add the parmesan at the beginning (adding the cheese late prevented the folds from sealing together, creating too many gaps)? Would the acidic(?) tomatoes affect the fermentation? * Would have used rye if I had any on hand. #bread #sourdough #baking

I posted a note yesterday from Coracle BUT I think for some reason my browser tab didn't have nos2x enabled. That post never got out, but I didn't see an error when sending. Is it possible that Coracle just silently sat on it without a notification? --- (Posting this from Coracle... but w/nos2x enabled!)

Back home after 12 days in El Salvador. Apologies, but I was mostly quiet on nostr due to some limited connectivity. * Airbnb internet connection was dead for basically the entire second half of my trip. 🙁 * @https://silent.link worked great but not gonna stream tons of content in/out of nostr over a pay-as-you-go data plan. Local cell network was ~$7.50/GB. I did YOLO back into nostr at the airport and holy shit did I eat up my remaining data balance fast!! Also, I still use twitter and think of it as my "work" account. And this trip, even the non-bitcoin site seeing and whatnot, all felt appropriate for my "work" audience since El Salvador is such a big part of the bitcoin story.

Absolute JOY to see my wonderful friends k9ert and Moritz of Specter Wallet fame!

OF COURSE HANDSTANDS HAD TO HAPPEN! @Adopting Bitcoin #handstand

All I know is: builders love builders. Awesome to meet and get to spend some time with @Djuri down here in El Salvador!

TFW @KumaDawg is no longer content to just sit next to me in her "copilot's" seat. First the loving headlock to stop her from standing on the table. Then the struggle to escape... Seizing the high ground... UNLEASH THE CHAOS!! #dogs #dogstr

🔥 @SeedSigner en español GETTING CLOSER!!! 🔥 It seems so simple, but it took me all day to add the logic to make our titles able to scroll. Certain phrases in other languages just aren't going to fit on our tiny screen so this was always a must-have part of this multilanguage effort. But all of our UI components are custom built -- can't just whip out some css or JS -- so any new behavior takes some work to add in. Tomorrow: Do the same thing for button text (looking at you, "Herramientas"!).

I thought I could implement a pretty important new @SeedSigner feature in the uninterrupted 2-3hr block I had earlier today. Narrator: He didn't even come close. Like not even a little. Like, wow, he's really terrible at time estimates. Me now: --- (ya, I'll be fine. Just astonishing and hilarious to be so wrong!)

This is super nerdy, but I've spent most of today so far working on (er, struggling with*) the @SeedSigner CI test runner (automated process that sanity checks code updates). We have a typical test suite for it to run, but our screenshot generator is, in its own way, another set of tests that help reveal unexpected bugs. It's stupidly simple, but it took HOURS to figure out how to get the CI to merge those two sets of test results into one final "coverage" report (how much of the code is actually tested). Happy to report: success! With "Coverage report" cleanly in its own section of the CI checks, we'll be able to easily see if any proposed new code additions are missing appropriate tests. In general, coverage should be ngu only. If coverage decreases, your work on those proposed changes is not yet done. This is building off of amazing work by dbast (https://github.com/dbast) to get these CI checks integrated in our repo in the first place! --- *sometimes building in public means also exposing just how bad you are at some things. Oof, the guess-and-check struggle!!

Lots of really interesting insights and observations landing hard for me (in a good way) in this podcast ep. Really strongly recommend giving it a listen.

Hidden Brain Media

Emotions 2.0: The Benefits of Mixed Emotions - Hidden Brain Media

Sometimes we feel just one single feeling with overwhelming force. We’re joyously happy. We’re crushingly sad. But sometimes it’s...