Show more

Just spent more than an hour trying to figure out how in the heck my Emacs config was having a different set of colors in my Qubes VMs than on my actual Fedora system. The answer was in a relic from my ancient set of dotfiles. I did not bring my .Xresources/.Xdefaults along for the ride this time, and those were in fact responsible for the non-powerline theme elements. The last time I thought I cared about these files was probably a decade ago!

If this was a parking spot in TX there would be a crane at work full time to pull trucks out of the water 😂

Took a break from messing with to take a nice socially distant walk through Delft. Everyone in town who knows me from the last year here has shouted their congratulations to me on the election in the US, as if my vote in TX counted for anything. For the last 17 years, or since I first actually read the constitution after swearing to support and defend it, I’ve cared far less about the constitutionally weak President than the immensely powerful Congress. Too bad it’s still broken.

Running on my NUC again. I’ve missed the compartmentalization the last year or two as it’s been impossible to get any work done on my company machine. It’s been a while, and a major release, since my last run with Qubes but I should be up and running again soon.

Released v0.2.1 of my connection checkin’ project today to fix some error handling issues, and reduce some duplicate code into a generic function making use of a common trait.

Next release I’ll add support for JSON payloads in the http(s) checker.

crates.io/crates/connchk

Tomorrow I think I’ll install on my NUC, and perhaps my T460s as well. Give it all a test drive before my Librem 14 or Librem 5 ship. I’ve run it Live, but my go-to Live distro is

Announcing the Librem Mini V2

"The Librem Mini v2 in just about all respects matches the Mini v1 including the same base price. The big difference is that we can now offer a new, 10th gen i7-10510U Intel processor. "

puri.sm/posts/announcing-the-l

Any week that starts with an LDAP crash is not going to go well.

I’ve never really felt like getting a car in NL until today’s pile of train delays had me zigzagging all over creation and turned a 2hr trip into 4....

I’d rather a motorcycle though if it came to that.

The General Purpose Computer In Your Pocket

puri.sm/posts/the-general-purp

"One of the neatest tricks Big Tech ever pulled was convincing people that phones weren’t general-purpose computers and should have different rules than laptops or desktops. These rules conveniently give the vendor more control so that you don’t own a smartphone so much as you rent it."

Crazy week at work ended on a positive note. After making an insane number of commits and PRs across way too many projects it finally became clear where the blocking issue was hiding. With that fixed progress can continue. The lack of meaningful tests at any level, from the unit up through systems integration, is a serious problem.

Taking a break from a gazillion screen hours to make something with my hands.

Today I deployed an Azure Function App in . When it was all said and done, and my machine sullied by MS libraries, I was left wondering how this was any different than any other container I could have deployed behind an app service. The logs showed me the answer: there is no technical difference. Also, the container MS selected is significantly less performant than the one I rolled for a different service. I may just rewrite the thing tomorrow.

❌ NSA analysts spied on significant others.
❌ Ring employees were caught looking at off-limits footage.
❌ Verkada staff use their own facial recognition tech to harass other employees.

Abuse of dangerous tech often starts with the people who build it. vice.com/en/article/pkdyqm/sur

I really should do TDD more often. Or I feel like it is helpful for me. Particularly now with something like seven active (semi-related) projects. It’s pretty rough when use of one from the other reveals a bug that has impacts on four different projects. I was able to fix one such case today without impacting the public API but it was less than fun.

Need to write some tests for a system I’ve developed for $dayJob. I hit some unexpected corners today. They were easy enough to resolve, but they never should have happened in the first place.

Going to look into some CI so I can automate builds to provide packages for my projects. Just to see how long it would take to ‘cargo install connchk’ on a small system, I installed the toolchain on a and checked: 69min. Cross compiling on my T460s takes 62s.

Any thoughts on which tooling to use?

After spending several hours fighting with OpenSSL variations in my array of Linux hosts, I have released v 0.2.0 of connchk to remove the OpenSSL dependency completely. TLS is now handled by rustls.

Now the project builds easily with cargo or cross on x86_64-unknown-linux-gnu, armv7-unknown-linux-gnueabihf, and x86_64-pc-windows-gnu.

crates.io/crates/connchk

Right now my 'connchk' project is really only available if you're a user who can `cargo install connchk`.

This weekend I think I'll add some automation to at least provide binaries for x86_64-unknown-linux-gnu, armv7-unknown-linux-gnueabihf, and x86_64-pc-windows-gnu targets. Maybe later I'll package .rpm and .deb versions too.

Show more
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml