AirBreather

https://youtu.be/WLfAf8oHrMo

This sure looks like C# to me, not C/C++

You’re absolutely right! It’s not just flawed — it’s impossible to enforce.

/s

More seriously, the core issue isn’t completely novel to large established open-source projects. How do they deal with the possibility that someone might be contributing code from, say, a closed-source competing product (or one whose licence is otherwise incompatible)?

The same answer ought to work here, probably.

Maybe Trump will fire him.

In theory, the president can’t fire the vice president, for the same reason why the vice president can’t fire the president.

But I don’t think anyone’s ever just tried it with the “screw the rules I have judges” workaround, so, 🤷

No, the DOJ entity for that area is the US Attorney for SDNY.

Manhattan DA = state, not federal

Is this the kind of “warning” like those “warnings” they put on grape concentrate products during Prohibition to help you avoid “accidentally” using it to make wine?

Since you’re still a Windows user at least for now, and assuming that you’re planning on continuing to be open-source, I can recommend Certum for this. https://shop.certum.eu/open-source-code-signing.html

I gave up trying to initialize the USB thingy using Linux (I tried regular Arch [btw] and an Ubuntu distrobox IIRC), but once I got through the initial steps using Windows, I was able to sign ongoing builds with Linux just fine. It took a LOT of trial and error since there seem to be very few people who simultaneously

• pathologically dislike using Windows regularly
• still want to make it easier for people on Windows to minimize Windows Defender complaints when running software that they build
• have the motivation and resolve to send a lot of PII to one of a handful of companies whose longtime business model is based around reputation and trust in order to get a usable certificate
• are stubborn enough to go out of their way to still figure out how to do a subset of this stuff on Linux
• are capable of actually succeeding at that, and
• are willing to show how they did it in a way that should be reasonably easy enough to understand and adapt to your situation

I didn’t renew after my first year - I switched from publishing an executable to publishing it on the web, so I no longer had a need for it - so I don’t know how things have changed (if at all). Most of my information came from eventually stumbling upon this wiki page for a Ruby-based tool where they figured out the last bits I needed to get it to work.

• It also has instructions for initializing the USB thingy on Linux too, so if I were to renew, I’d give that a fair shot… but seeing “icedtea” and a link to a web application that no longer resolves, I’d still only recommend it if you can use a Windows machine once a year.

I was beyond belief that such a tier list could exist without it.

He’s been composing for so long, you’re not going to let him spend that time decomposing afterward?

I can’t even imagine how my friend would take it.

OK, OK, time out. You haven’t tried talking with them about it? If you have as strong a mutual (platonic(ish?)) relationship with them as you say you do, then it should be able to survive a serious conversation about your shared future, especially if you emphasize that you want to try to keep them in your life in a major way like this.

That conversation will probably be hard, and I really can’t think of a solution that would feel perfect if I were in your shoes, but I would sure as hell rather have that conversation than the “I made a decision, and here is how you will be impacted” one, or the “I kept my life on hold because I was worried how you might react to talking about it” one.

I don’t know your personality or your friend’s personality, so I can’t promise that you will sort it all out without emotions running high, or what the ultimate outcome of such a conversation will be.

But jeez, bud, you’ve GOT to be able to have serious talks with people whom you trust and care about.