Mike Burns @mikeburns@mastodon.technology

A fundamental flaw of the Web is that the browsers accepted liberally but the servers did not send conservatively.

Also this was my first time successfully using Rust. It was fine. Had to turn off colors in cargo, and the error messages are much too wide for a terminal, and the docs all seem to be in HTML instead of mandoc, but such is life in the fast lane I suppose.

I wrote this so I could hook it into mutt via auto_view and mailcap, but mutt's builtin pager can't handle all the terminal escape codes I used!

Weekend project: read Markdown, output terminal escape codes. Supports all of CommonMark plus some extensions such as GFM (but not tables).

Just distributing the signify key I'll use for signing tarballs.

untrusted comment: Mike Burns genesis public key
RWSMMhDm75mlbJi6BMrgSgymOBrnF7jQvKKivy7FyA3TaE9rlz0ibB/s

Should I be making use of -z -- should I embed the signing data in the gzip header? Will this prevent users of minisign, etc., from interacting with it? Is this meant to be a public feature, or is it only for package infrastructure?

Make a keypair for kicking off the world. Make pub available from my Web site (HTTPS) and share it on fedi. Sign foo-1.1.tar.gz with it (gzip header?). Package within the tarball the pub key for the _next_ version, and install it to $PREFIX/share/foo.

For foo-1.2.tar.gz, sign it with the newer key, make a new keypair for the next release, package that in the 1.2 tarball and install it in $PREFIX/share/foo over the prior one.

Does that seem right?

I maintain a few tiny projects. When I distribute them as tarballs I also make the SHA checksum and a PGP signature available. My PGP key is on all the major keyservers.

How do I switch to signify? It doesn't specify key rotation, expiration, or revocation protocols. It doesn't have a key distribution mechanism. How do I implement those in a practical manner?

I have so many XML files in /usr/local/share/metainfo. Does any program on my computer use these files? Why are they here? If I were to modify one, what would it change?

I've recently learned about FreeDesktop AppStream XMLfiles, but I can't figure out what I'd use one for in practice. There has to be some context I'm missing.

The file is installed on the OS and then considered available? How does that differ from .desktop files? Why do all the docs talk about package managers -- how is the installed file used there?

What context am I missing?

https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html#sect-Quickstart-DesktopApps