Could you elaborate? I see no glaring typography problems on KDE (while there are quite a few on macOS, IMO). Iconography – IDK, fairly consistent on the default theme, but it is a bit of a peculiar look.

One thing I really like about macOS is the shortcuts. You can fairly easily get 90% there on KDE, though. The last 10% is tricky regardless of the WM you choose: some apps just don’t want you to mess with the shortsuts in this way (looking at you, Mozilla).

Apart from that, honestly? With global menu, KDE is nearly indistinguishable from how I use macOS.

> Run the script as described in the project's Read Me

I don’t think this warrants a whole installer script – if you replace UUIDs by hand, you can as well read through the .mobileconfig file and make sure you understand what the profile does, then double click it to install :)

Note that you might also want to remove some other entries from the profile, as, from a glance, those might still delay minor updates by 30 days. (Or does `forceDelayedSoftwareUpdates=false` make these harmless?)

I really really don’t like how the author spins AGPL relicensing and enforcement as an indication of project dying. AGPL is a perfectly fine license [1] for FOSS projects, and enforcing the license is a prerequisite of a healthy project. I get what he’s trying to say, but putting it all in the same category as cutting features and winding down in general feels... wrong. Trying to save a project should not be called “dying”.

That said, congrats on resurrecting it!

[1]: The fact that big tech doesn’t want to touch it is on the big tech, not on the license!

I guess late-stage relicensing will always feel like a rug pull to the community of users of the previous license.

If by flaws you mean the security researchers spamming libxml2 with low effort stuff demanding a CVE for each one so they can brag about it – no, I don’t think anybody can fix that.

Based on context, i kind of imagine they are more thinking of the issues surounding libxslt.

libxslt part I can agree with. But xmloxide readme states XSLT support is a non-goal anyway?

It is, and all logs should ideally go to stderr. But that doesn’t let you pipe them to different places.

That’s pretty much class action lawsuits!

> I'm putting my email on GitHub precisely to give people a way to contact me.

They’re not only looking at the public email in your profile, they’re also looking at your committer email (git config user.email). You could argue that you’re not putting that out for people to contact you.

(I’ve used that trick a couple times to reach out to people, too, but never mass emailing.)

Wise does accept cards for transfers, but I think most people use cheaper methods. (Also, last time I checked, they’ve used Adyen.)

I’ve poked around – looks like it’s not enough to just declare you’re an accredited investor, but also prove it?

What evidence do I need to provide as a US investor: https://help.angellist.com/hc/en-us/articles/15569926884109-...

As a non-US investor: https://help.angellist.com/hc/en-us/articles/15570114297869-...