@djm While I agree that the Postel / RFC robustness principle, especially as widely understood today, is largely the wrong thing to do in protocols in 2023, things were different in the early Internet and early web. Then the problem was not "how do I do this networking thing really well", but "how do I and others do this at all so that it gets wide use?". The principle mattered more back then. Without it, we might not have the Internet at all today. We might only have closed gardens.
"OpenPGP for Application Developers" is now public. I did some proof reading on that, so I'm biased, but I think it's a neat and clear intro to OpenPGP . It's more on the conceptual level than nitty-gritty bit level formats or details of the cryptographic algorithms, but it should help developers using OpenPGP understand what's happening. The site is not quite complete, but a very good start and you can help make it better.
@joeyh Thank you for the recommendation. I hadn't heard of Phanby before, but I've been trying it today, and it's overall a much nicer user experience than the native UI of Mastodon. I've not had any big problems so far, but it'll take a while to find how to do all the things I'm used to doing with Mastodon.
Overall, with half a day's experience, five out of five stars. It's easy enough to try, for anyone curious.
I've started a new job earlier this month. I now work on and for #Radicle , a distributed git hosting system and peer-to-peer code collaboration system. I'll be working on continuous integration support.
It's open source and written in Rust, and is making git be #distributed again.
@neil@pwaring I notice that for many people, an important reason to have a blog is to earn money. Medium and Substack are based on this idea, and at least they are not surveillance based advertising.
I can sympathize with people wanting to earn some or all of their living by writing on the Internet.
As a read, I do not like the experience of having to click away popups to be able to read.
@n8@mlinksva I heard many times over the years that research software tends to "not up to professional software engineering standards". Not having a requirements document is part of that.
In my experience, in the software industry, very little software of any kind has a requirements doc, at least not a useful one, never mind anything else that one might expect of quality software.
I'd like to sit down with researchers, specifically, to discuses how to improve this, some day.
On this day, in 1991, Linus Torvalds first announced Linux to the world, in the comp.os.minix Usenet group. I had written a tiny bit of code in that code: the string formatting parts of the kernel logging function printk.
Today, that code (with changes and improvements by other people) runs on billions of devices, on all continents, on all oceans, in orbit, and on Mars. Possibly other places.
"Open source" has an actual definition. The definition is important. If you relax or ignore the definition, the term becomes meaningless.
A lot of people call things "open source" that aren't. Some are just lazy. When corporations do it, especially very large tech corporations like Meta, it's an attempt to make the term "open source" meaningless.
This realization was triggered a "workflow tool" for a programming language where running a program builds it before running it, but doesn't actually write the built binary to a file. Building the program does that.
Foot gun: if one has built the binary earlier and has a binary lying around, running the program with the workflow tool doesn't update the binary. Result: head-scratching when running the binary directly gives different results.
Currently working full time on https://radicle.xyz/. On the side, I do training in the Rust language (https://liw.fi/training/rust-basics/)I have almost 40 years of experience, almost 30 of it working full time. I have code running on billions of devices, on all continents, on all oceans, in orbit, and on Mars.