Some shorter thoughts and updates that might not warrant a full gemlog entry. I'll probably be using this to post updates on my various projects in a much more regular fashion.
Just subbmitted a PR for the `sc` crate which gives the ability to make syscalls from Rust on NetBSD/x86_64. If accepted, maybe I'll see about adding other architectures on FreeBSD and NetBSD.
I managed to get the latest git source of Zellij to compile and run on FreeBSD, so no more faffing about with Tmux. Hooray! The fix for Zellij will be in the next release apparently. I had to apply a patch from the port to the `wasmer-vm` crate, as they're making some erroneous assumptions about not being able to support x86_64 on FreeBSD.
So apparently the terminal multiplexer I've grown accustomed to (Zellij) isn't working on FreeBSD right now. Trying out tmux. Hopefully my muscle memory doesn't get in the way too much.
I decided to install FreeBSD on actual hardware again and had some interesting complications. I had a full gemlog post ready to go about it actually, but one of the complications lead to some data loss, so I'll have to put it all back together again.
In other news, I've been forgetting to git commit/push/pull when updating this tinylog and had to clean up a bad merge earlier. No posts should have been lost, which is the great thing about putting it all into VC, but obviously my workflow needs updated.
The latest Dory commits center around an iso-8601 time implementation, which is the format that `timestamp` lines are supposed to use in messages. The spec is of course a little ambiguous, and iso8601 allows dates in one of three formats, with the further distinction that there is both a `basic` formatting and an `extended` formatting, where the difference is the appearance of separators between the fields. I've decided for expediency to only implement `calendar` style dates, which is the traditional yyyy-mm--dd format that we're all used to seeing.
Today, after finishing a blog post, I wrote a parser to convert a `&str` to the `Message` struct in Dory. I also added a lot more test coverage, which revealed a few issues to fix.
The `sendmsg` binary (using Dory as it's backend) is now able to send Misfin mail to the reference server. This required more debugging skill than it should have due to some issues with both rustls and a compiler issue. Might be good for a full post? Anyway, link to the repository below.
Just finished hacking together a small binary that sends Misfin messages from the command line using Dory. Time to grab the reference implementation code and start testing.
As an aside, I was thinking that client certs in theory should make identity spoofing next to impossible. That might mean that Misfin clients could just directly shell out to a sendmail-esque binary such as this rather than logging in to a remote server and sending their messages from there. Basically how email was always supposed to work, before all of the spam mitigations broke the ability to deliver mail from unknown random IP addresses. I mean, where you actually send from shouldn't make a bit of difference so long as your certificate goes with you.
Began a proof of concept binary project to test out sending Misfin mail using Dory. I should be able to commence testing for interop in the next couple of days. Watch this space for progress reports.
Rust 1.70 came out this past week. One of the highlights of this release was the stabilization of the OnceCell and OnceLock types. OnceLock in particular is a big deal because it has the potential to replace the `lazy-static` and `once-cell` crates, for those times when you want to have a lazily evaluated static data structure.
I just finished a short while ago changing Zond to use the new interface and so far so good. It's nice and simple, with good documentation.
I wasn't completely happy with how I had previously setup the workflow for this log, so I did a bit more coding to automate things in a better way than before. I created a small Rust crate for working with Tinylogs and incorporated that into Zond. Now, when you type `zond tinylog` with no other arguments, an editor window will pop up for you to type your thoughts. So long as the temporary file thus created is not empty, the text is added as a new post. This also allows the log to contain a header, which was not possible before.
