If you want to be super minimal, I prefer acme.sh[1] instead. It even comes preconfigured for various DNS providers[2], and you can even create your own hook if there isn't already one[3].
>Sadly, the one non-standard thing that they continue insisting on is Snap.
Snap was and largely is mainly for the server crowd, that they've shoved into the desktop. So in that regard I suppose it's at least consistent for them.
That said, snap is still terrible, but Canonical always just does their own thing.
>The system runs a downsized version of Doom that requires less RAM.
You could even say it's a...light-weight DOOM.
I'll see myself out.
(In all seriousness though, super impressive work! It always amazes me what computing power actually resides in what we deem to be "simple" devices these days - in some ways it feels like computing power gone to waste.)
>What is not good, though, is if you, the maintainer, are burned out, or overworked, but stubbornly insist on being a bottleneck in the project under your inept stewardship nevertheless, and just whine and moan about your burnout to get internet points and worldwide pity.
The problem is when there are no other maintainers to the project, and you quite firmly believe the project itself has a future, just that nobody else is able to do so. Yes, you can quit, but if people truly do rely on your project (but nobody is actually willing to take the reigns) then it can become an issue of pride for some. To be clear, I'm not suggesting that people burn themselves out (I myself have gone down that road before), just that "Walk away" isn't always such an easy option for some people.
If nothing else, it's impressive that they've actually managed to migrate those Google Talk users over the years (myself included in that, albeit less than I used to). They probably did so extremely begrudgingly, but the path went something like:
Google Talk -> Hangouts -> Google Chat
People I added years ago are still reachable in Chat, which I guess is nice (in spite of everything else).
It's actually the WHATWG you need to watch[0], not the W3C. The latter has had basically no power for some time now and only endorses what the WHATWG propose[1].
The great thing about Firefox before the Photon addons apocalypse was that anyone could theme the browser in whatever way they wanted. Sure, it's still possible, but userChrome is a messy hack that Mozilla are trying to get rid of any moment now.
Soon, we'll be stuck dealing with whatever UI Mozilla feels like implementing for the current week. Thanks for your efforts for now at least.
The problem with Pale Moon is it's effectively a dead end from a development standpoint. Yes, it gets security fixes from upstream (for which are applicable) but it doesn't receive much in the way of meaningful web compatibility (the elephant in the room being WebComponents, which none of the team have the capability of implementing in the current codebase). It's based on Firefox 52 and refuses to re-base on later versions, partially due to lack of XUL-based extensions and partly due to the introduction of Rust (which does not exist on some platforms which Pale Moon supports - including Solaris/Illumos).
>Authentication of boot loaders is done via cryptographic signatures [...] the cryptographic certificates that may be used to validate these signatures are then signed by Microsoft
This is what concerns me. While Microsoft are indeed dominant, surely them signing these is a conflict of interest? Why can't there be an external body that signs these, including those for Microsoft?
[1] https://github.com/acmesh-official/acme.sh
[2] https://github.com/acmesh-official/acme.sh/wiki/dnsapi
[3] https://github.com/acmesh-official/acme.sh/wiki/DNS-API-Dev-...