I am fully back on a 24v system running largely from electrodacus.com

My system failed in late 2021 with no replacement parts to be had, so spent the last 9 months on a 12v battery and victron MPPT charger.

For the last few weeks, I ran half my panels on the 12v system with the victron MPPT charger, and half on the electrodacus SBMS0...

Much to my surprise, the MPPT did not outperform the SBMS0, but at least MPPT was more expensive, complicated and proprietary!

Reading Low Tech Magazine's thoughts on staying warm in cold rooms, very conscious that we're gonna get more and more in trouble with our energy supply every year: solar.lowtechmagazine.com/2015

And thinking about how my computer exhausts heat into The Room In General rather than to, say, the underside of my desk, to which I could then attach some kinda curtain to keep my heat around my legs

Putting the Pacific in Pacific Northwest!

The rocks pictured are proximate to the most photographed rock on the oregon coast. Here's to underdogs!

A spaceship landed in the park. A door dilated and an alien emerged.
"Er," they said.
They looked around, turned and looked at the door, then turned again.
"Do you also experience that?" they asked the gathering crowd. "You go through a door and forget what you were going to do?"
#MicroFiction #TootFic #SmallStories

Hermetic builds, reproducible builds, software bill of materials (SBOM): the NSA recommends Guix.

OK I’m kidding, but Guix certainly ticks important boxes under “Recommendations (advanced)”.

#SupplyChainSecurity #infosec

An example of using/refusing to use privilege: twice I have been asked to be on the board of directors of a 501(c)3. Once I refused, once I accepted. The time I refused it was because I didn't want to be in a position of authority in a largely bipoc hierarchical structure and preferred to participate from the bottom, as a volunteer. The time I accepted it was a fledgling immigrant workers center organized by workers and artists who needed access to funding that my privilege could help enable.

What made it exceptionally confusing was my attempts to trigger the issue locally failed. For some reason the debugging symbols were not being used in my local builds...

I tried cross-building the failing targets as an arch:all package, but then there were no debugging symbols, as they were manually stripped out; dh_strip doesn't strip arch:all... I think... and so the dbgsym packages were not created.

So I removed the manual stripping and I could reproduce the reproducibility issue!

Show thread

Well, finally figured out why -boot was not on arm64 and armhf when the build path varied between builds.

The debugging symbols have been embedding build paths since 2022.04~rc4.

Not sure if it was a packaging change, or an upstream change, but passing -ffile-prefix-map instead of -fmacro-prefix-map to the compiler, as well as passing --debug-prefix-map to the "as" generated assembly fixed it!


Time to submit upstream!


Heard the story of the girl throwing starfish into the ocean? A man watching her says "don't you know there are miles of beach and you can't make a difference?"

The girl bends down and scoops up another starfish and gently throws it into the ocean, turns to the man and says "it made a difference to that one".

I often think of this story when world events make me feel powerless. I can't help everyone, but I can help *someone*.

So... if anyone needs me to throw them into the sea, I'm here.

your periodic reminder that you shouldn't use CC0 for software source code: « Fedora sours on Creative Commons 'No Rights Reserved' license » theregister.com/2022/07/25/fed via @TheRegisterBot

“Is reproducibility practical?” 👇

This new post asks whether reproducible deployment is a luxury for “professionals”, clarifies what #reproducibility means and how it affects #research practices.


To anyone who says "it's just summer"... here's NASA's climate spiral👇


So back in 2020 Codeberg asked for help from the community to help them with #accessibility issues. They need some help in house as the current solution helps them manage the spam that would overwhelm signups, but their moderation team is small. CAPTCHAs aren't very accessible and they would like some help to fix this. #a11y Can anyone help? The linked toot is their request for help.



Show thread

Debian has a strong maintainership model, where the maintainer usually uploads package updates...

Some days I just want to fix things!

So lately I have been working on the abandoned, forgotten, neglected packages that have been left to the Quality Assurance team...

...not because these are important packages, per se, simply because there is minimal process to update them.


...with great success!

89% to maybe 91% once all patches are applied.

Just learned that makes account names available 90 days after the account is deleted.

hard enough for

Reclaiming usernames makes it possible to squat a trusted identity that may have hosted projects in widespread use...

...and git pull will just pull from the same URL under the new account holder's control.

So and be squatted or give unto Caesar that which is Caesar's! Why is OK if you get an AI to do it for you?

I was pleased to discover I hold the not only the oldest commit in despite still feeling like a newcomer to the project, but I also was using a timezone offset three minutes off of UTC.

Maybe future me did this, messing around with the "guix time-machine" command, as the first guix commit was in 2012...


Or maybe the real-time clock on an aarch64 (a.k.a. arm64) machine I was using was very wonky.

We'll never know.

Show older

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).