Anthony Martinez @ajmartinez@librem.one

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

@kyle my Dovo may actually need to be sharpened after like a decade of getting by just honing on a leather strop. I have the stones here with me to do it. Maybe I will.

@kyle interesting, I've not used a safety razor of that type (vibrating or otherwise). Just my straight razor. Haven't used that in a while either if I'm honest.

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.

https://ajmartinez.com/tech/posts/202126-003-librem14

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.

https://crates.io/crates/arse

#Rust #FOSS

@veer66 That's true, but unless you're running a daemon that interpreter startup time is per execution and the build cost (for a given version) happens exactly once. Of course I think this is amplified on simpler problems where the comparison is fairly simple std lib vs std lib work. Otherwise like most things it's about the right tool for the job, and the compile time certainly factors in!

@purism @kyle heh this same photo was used in an embedded security workshop I attended this week!

@veer66 I know the feeling. One of my Advent of Code solutions that disgusts a real software engineer for its inefficient algorithm still *finishes execution* before Python can even launch its interpreter. Still, Python remains a useful tool on which I have created quite a few mission critical tools.

@veer66 good deal. I generally turn to Python when my Rust chops aren’t enough. If Apache Arrow handles your use case rock on with it!

@rbrown bumping up the RAM in sys-usb didn’t help, and I bounced the VM without checking dmesg and friends. When the screen goes dead over USB-C it also takes out charging which I believe contributed to my dead machine symptoms. At present I am just not using the USB-C hub with my Librem 14. It has enough native ports to suit my needs, but I may try just a dumb hub with no more than PD pass through and USB3.1 ports to see how that goes. Charging itself has not been a problem directly on the port

@veer66 have you tried the community help chat on Discord? Lots of helpful and very knowledgeable folks there who can probably help.

@veer66 you can use Option<T> to make your destination field optional on read, and then add the value as Some<T> before you write it. Make sure you read the csv into a mutable struct and you should be good to go.

@stsquad indeed shared data has been the one time I needed to explicitly declare a lifetime. Someone somewhere wrote an excellent piece that demystified them a good deal. I’ll try to find it, though perhaps it’s not as mystifying to real developers. I’m just a guy who sometimes solves problems with software.

@rbrown in my case the shutoffs happened while I was out of battery and thought I was charging but was not. That’s what led me down the am I charging or discharging path. My screen (hdmi through the usb-c hub) randomly shutting off may be due to the sys-usb qube OOM killing things so I bumped it up to a gig from 300M. Plan to use it that way today. Will let you know how that goes.

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.

@veer66 you don’t have to. Which csv crate are you using, and did you use serde’s macros to map the header fields to whatever you wanted them to be? Extra stuff doesn’t matter.

@stsquad very little I’ve written has required explicit lifetimes, but in the cases it has ‘static is almost always the only sensible one anyway.