Buidl Crypto just published an long-form interview with me where I touch on just about every aspect of @purism. It's a great conversation, check it out here: https://open.spotify.com/episode/290Apvlx688VWT4vPqBl6n
Latest update on my run with the Librem 14 - https://ajmartinez.com/tech/posts/202128-001-librem14
Bumped dependencies for two of my #Rust crates today. Should automate that process.
1m34s from my projects qube for a release build of ARSE 0.11.0. Pretty impressed by how close the VM performance is to the live distro performance.
The Librem 14 running Pure OS Byzantium off a USB stick did a normal release build of ARSE 0.11.0 in 1m30s. I need to build it in Qubes OS again and make note of the time for a better comparison because I did add two new dependencies between 0.9.0 and 0.11.0.
Lots to like about this machine.
v0.11.0 of A Rust Site Engine is out, and completes my 1.0 feature roadmap items. I've not rev'd to 1.0 as there is some refactoring to be done, and I would like to get that done between now and the time I actually release 1.0.
Earlier this week my significant other, for whom ARSE was created, made her own post without any assistance from me. Now, with 0.11, interested parties can hit also consume content by RSS.
One more thing I've meant to give a go on my @purism Librem 14 for a while was just doing straight DP over USB-C. I've had a cable for this for a long time from when my NUC was in my office. Anyway, it works fine. Of course having left my regular charger across an ocean this means I can only do this when running on battery since I must charge over USB-C for the time being, but I'm glad it works without issue.
For any other Librem 14 users running Qubes, I was able to install the librem-ec-acpi-dkms package in Qubes dom0, which lets you have more control over the embedded controller including setting charge thresholds. I documented my steps here: https://source.puri.sm/-/snippets/1170
It took two days of troubleshooting by way of trial and error in an absolute vacuum of useful information. Neither COTURN nor Matrix communities were what one might term useful in any way - with both often outright denying an issue was even possible. This isn't how you grow adoption.
I'll post my working config later, as well as some notes on how I'm dealing with Ubuntu's COTURN package having no good way of accessing Let's Encrypt certs thanks to an ancient version of systemd.
#FOSS misery
Getting to the point where I will soon be someone who *used to* run a #matrix homeserver. The spec is a disaster, the reference implementation does not work, and it's increasingly difficult to justify asking anyone to use one of the many underwhelming clients just to send me a message that happens to be encrypted end to end.
For now I'm just going to keep using the built-in ports and stop messing with the USB-C PD hub and my Librem 14.
Added a very minimal "gallery" per the specifications of A Rust Site Engine's Product Owner (aka my bride to be) for the v0.10.1 release.
If I could help computer users understand one thing it would be that unless something changes, their future computer will be locked down like their phone, so they can only install software if the OS vendor approves. I talk about this in a new blog post: https://puri.sm/posts/the-future-of-computers-the-neighborhood-and-the-nursing-home/
As of todays #linux-next (https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tag/?h=next-20210112) you can run the #librem5devkit without any additional patches using the default mainline arm64 #defconfig. This means distributions can enable it without trouble from #linux 5.12 onwards. The #librem5 itself needs some more work but it builds a lot on what we have for the devkit.
In an embedded security presentation I watched today my favorite language, #Rust, got a notable mention. I happened to be concurrently building Buildroot for one of my Beaglebone Black boards, and it had just gotten to the compiling of #ripgrep so Cargo was busy doing its thing. Perhaps next week I will actually get started on the Rust Embedded book and make some lights blink.
May well be that my USB-C hub, or my sys-usb qube, is to blame in my troubles with the Librem 14. Using everything straight off the laptop made it through a day of repeated Buildroot builds that flexed all my cores for more than an hour at a time.
Performance on my fairly beefy homeserver was atrocious the last 3-4 days. It took 9 attempts to join the synapse room on Matrix.org, and then the “solution” suggested was to add federation workers. Six hours after I noted more than 85% of my federation traffic was failing 1.37.1 was released, and actually addressed the very issue I was seeing.
If you’re running a Matrix homeserver do yourself, and everyone else, a favor and get off stale releases.
https://matrix.org/blog/2021/06/30/security-update-synapse-1-37-1-released
I like to work with my hands. That may mean hammering out solutions to complex problems in #Python or #Rust, building things in my shop, or spinning yarn to knit something warm. You’ll likely see some of all of that here. By day (and sometimes night) I keep >13k nodes and services alive in the Electric Vehicle sector.
PGP: FCBF 31FD B34C 8555 027A D1AF 0AD2 E852 9F5D 85E1