"The Federal Trade Commission unanimously voted Wednesday to pursue policies that will make it easier for people to repair their own things." https://www.vice.com/en/article/k78xbn/ftc-formally-adopts-right-to-repair-platform
I dislike when companies capitalize on incidents, so I usually publish my thoughts months later to avoid even the appearance. But folks asked us how @purism products fare against a Pegasus-like attack so I wrote about our overall spyware defense. https://puri.sm/posts/defending-against-spyware-like-pegasus/
Most interesting. As part of my periodic rotation of strong random passwords on my never-used-but-maintained-so-family-can-still-tag-me-in-things-only-they-care-about Facebook account, I noticed there's an option to Encrypt Notification Emails. I've enabled that, and assume that the tiny set of people I know who actually use PGP might be interested to know of this feature. All one of them follows me on here so, my duty is done!
Given that the network I am responsible for is chock full of Azure services, it looks like I will now find out if my brain has any space left for learning PowerShell and C#. My personal tools are quite probably always going to be Bash, Python, or Rust. Same for any work related to the embedded nodes connected to my network. For the cloud stuff the clear winner in exposed functionality is C#, so I guess I’m learning it get around the big gaps in Azure’s Python SDK.
It's strange that we are solving the problem that people use the same passwords everywhere, by replacing passwords with unrevokable biometrics, that *have* to be the same everywhere to work.
Biometrics aren't secrets. It seems like "a good quality infrared image of the target's face" is hard to get right now only because the tech isn't ubiquitous yet. Wait until every website the user logs into has a copy. https://arstechnica.com/information-technology/2021/07/hackers-got-past-windows-hello-by-tricking-a-webcam/
This was a good episode
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.
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