It's also worse than that. It uses the Raycast logo directly in the launcher itself. Which is odd because just above this, OP says:
"I've actually thought about that before; I've tried to be extremely clear in the project's README with a disclaimer that this is a non-commercial hobby project and is not affiliated with the official Raycast team in any way."
Clearly a bright kid, but that's quite a fumble. Among my ideas for being extremely clear about not being affiliated with Raycast I would have to say using their name and using their logo together would be the worst way to communicate that.
> Author does realize openssl[1], Linux[2], and many other "enterprise-level" pieces of software are entirely (or almost entirely) maintained by volunteer developers, right?
> In other words, applications where some other system (human or otherwise) will catch the mistakes.
The problem with that is that when you move a human from a "doing" role to a "monitoring" role, their performance degrades significantly. Lisanne Bainbridge wrote a paper on this in 1982 (!!) called "Ironies of Automation"[1], it's impressive how applicable it is to AI applications today.
Overall Bainbridge recommends collaboration over monitoring for abnormal conditions.
The Caddy[1] webserver also has built-in ACME. It has all the problems Rachel mentioned, of course, because now it's an ACME client embedded in an even bigger piece of software, but it's handy for sure!
I don't know much about Caddy scalability but it's worked great for my personal sites.
They're not, they're a (refreshingly transparent) non-profit -- but the government has the ability to reassign management of .ca to another organization as they wish.
