@the_tower_power_ hmm probably nothing since no one reads anymore?
@kyle good thing I know how to make my own yarn and knit my own fabric I guess.
Any @purism Librem 14 owners have a USB-C dock recommendation?
Today, I setup a local version of A Rust Site Engine for my significant other. This uncovered a few bugs in the Windows binary, which were addressed in 0.7.1. Then, while setting her machine up so she could make local edits and have them Just Appear live on the site I made another release, 0.8.0, which removed the Credentials struct entirely. My roadmap has been updated accordingly, and I will focus on performance rather than making an admin portal for a minimal site generator.
Tune in to our new episode! @katherined and @dsearls chat with @kyle and Shawn Powers about Signal’s exposure of vulnerabilities in Cellebrite’s mobile device hacking software.
Click the following link for full episode - https://www.reality2cast.com/68
#Signal #Cellebrite #cellphone #encryption #technology #podcast #newEpisode
@silwol something I’m pleased to see indeed.
"All that's left...." for A Rust Site Engine on its path to 1.0 is complete documentation, and the admin portal. Just added user-defined bind address/port to the configuration, and spruced up the README, marking another release: 0.7.0
Since I'm taking a long vacation in May, expect me to also start serving more than just my tiny demo site. In fact, with a 10hr flight starting my vacation I might just build a few of them in the air and deploy when I land.
@kyle one of the discussions I had with my team today was in fact the importance of documentation. It's now a performance target for the year for everyone on my team.
That said, my process for documentation occurs while I'm writing whatever I'm writing. This is, for me, mostly due to the fact I often question my abilities in even languages I use daily. Documenting what I am trying to do helps me accomplish the goal, and avoid perpetual feature creep.
Long day today in preparation for an upcoming, and much needed, month off. Got to know `-engine pkcs11` as an option to many openssl tools today as I put the trio of Nitrokey HSM 2 modules purchased for my team to use in eliminating single points of failure in the safe storage of critical secrets. Sadly almost none of these tasks are even tangentially documented by Nitrokey, OpenSC, or anyone else - but now that I’ve sorted that out for my team I’ll put something together publicly as well.
@stevenroose test coverage for ARSE is pretty close to 100% since I’m doing TDD. End of next week is my hope for finishing the admin feature and user documentation. That said if you can manage putting markdown inside a folder on your own it should be ready for you. What I added yesterday allows you to define your own template and CSS so in theory you can make it look however you want.
@stevenroose haha in the current world we need to take every opportunity to laugh. The name cracks me up, and so I stuck with it. The demo site is at https://some.bullsh.art just to round it out 😂
@stevenroose can’t say as I’ve not looked at Zola, you’re welcome to take a look and let me know though. In the long standing tradition that is #FOSS I had a need and wrote my own solution rather than looking at what else exists and making contributions there.
Well, I hadn't planned on adding additional features to A Rust Site Engine today but... Two Release Tuesday can be a thing can't it?
https://crates.io/crates/arse 0.6.0 adds accessing individual posts directly. Underneath the feature add was a major refactor of the application's core and the Engine struct itself. While rendering and load times were already very fast, I was previously loading the Tera template for every single request. Now it's done once at startup.
Released 0.5.0 of A Rust Site Engine today, adding support for custom templates for the rendering engine.
The README has been updated with some information on setting a custom template. Previous users will need to add the template parameter to their [site] config section to upgrade to 0.5.0. This should be the last breaking change for the config before 1.0.
Since direct inbound is neither necessary nor desirable, I’ve spun a new firewall VM in Qubes with my Wireguard interface. Now the AppVMs are using that VM instead of their own individual tunnels. I didn’t need to free up allocated IPs in my VPN, but now there’s one available for another device if needed. When I am back stateside I will reconfigure my US home network (as it’s needlessly complicated today), and add a peer for my Qubes VM so I can always reach local home assets directly.
WireGuard has really made it extremely easy to join my home networks on both sides of the Atlantic, and my cloud services (private side) together. Syncthing is replicating (note: do not confuse this for backing up - not the same thing) important data between two of my machines, while Borg is maintaining backups in multiple locations. All running smoothly between Qubes VMs, cloud VMs, Fedora and Debian on metal, and even the two iOS devices I still use.
Had a pretty good work week with my team being super efficient and taking a lot of good initiative to get things done before I even assigned it. Ended it all on a high note when I checked my personal email and saw my Librem 14 from @purism has shipped! Just saw a post about running Qubes on it, so when I fly home in a few weeks I will bring my backup with me so I can get things running as soon as possible.
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