10,844 karma · joined August 6, 2018
If ASML’s output were absolutely necessary to the US or the rest of the world, and if no replacement could be made, the Netherlands would have infinite leverage and be the most powerful country in the world. That they aren’t tells you all you need to know about exactly how far they could take a strategy like what you’re describing. Yes, everyone needs ASML. But ASML also needs everyone else.
An elite toolmaker is nothing without the factories that use the tools.
The odds of the Dutch attempting to encumber the use of ASML machines by western bloc allies is similar to the odds of the sun going out suddenly. It ain’t gonna happen.
I grant that if you act as a significant source of funding to a given entity, that entity is less likely to hurt you, if it knows what your interests are. Of course, this is completely impractical for hobbyist users of open source software.
That being said, I don’t have a problem with people standing up for what they believe, even when it has no practical impact. It’s good character building. I would expect that Sundar is similarly unbothered.
Economically, the BDS movement is making demands of so many companies that there’s hardly a large firm or other organization in the country they don’t have a problem with. But if you are saying you’re going to boycott everyone, it means you’re not really boycotting anyone.
People have been convicted for using words to convince other people to commit suicide.
Also not sure where you got the 3.7% number, but light duty trucks overall contribute around 10.4%. This includes some fraction of SUVs (those with truck-like drive trains weighing over 6000 pounds GVW) and minivans.
That being said, decarbonization of the truly necessary energy consumption is also a requirement, and that is expensive too. You need to convince people that they should want to pay for it -- no the billionaires cannot pay for the whole thing, for inflation-related reasons that are too complicated to get into right now. (The basic thrust of the argument is that US construction and industrial capacity is already highly utilized, and that allocating more workers to decarbonizing will necessarily drive up the cost of everything else, regardless of who nominally pays for the work.)
But maybe we disagree about this other thing. I'm not certain that closed source/paid software is less of a risk either. There have been high profile incidents lately that suggest this is not a sufficient defense.
Personally I just think you're barking up the wrong tree with this pay/contribute=>reduced risk link. I don't think there's anything there. I will grant that you are at slightly less risk from software you know well and contribute to directly, but that's only of any help for very low level stuff that doesn't have many dependencies.
I do not think that someone's status as a contributor to open source mediates their safety from supply chain attacks. Big companies that donate gobs of money get hit, and so do small operators who have contributed nothing are just trying out a hobby project.
At least according to the prompt, the library was attempting to delete not just itself, but all tests that depend on it. I do think if the prompt was solely scoped to removing the dependency on the library, it would be somewhat more defensible. Even better if he suggested an alternative!
I do not think it is correct to say that someone who is building something with a tool you don't like "deserves every single thing coming to [them]". That seems a little mean to me.
There is an intent to cause harm and a reasonable expectation of achieving that intent. And at least if the github issues are to be believe, a successful actuation of the intent in at least a few cases.
The delivery mechanism is interesting for its novelty but I don't think it fundamentally changes how the library should be classified. Conditional malware, maybe?
I'm trying to think of how best to handle this in terms of preventing people who might otherwise be harmed by this package from coming to depend on it. Ordinarily, packages that intentionally harm their users are banned from repositories like npm and so on relatively quickly. Whether the same will apply in this case is an interesting question, because while the number of AI-using programmers is growing rapidly, I'm not sure it is a majority yet. If not, perhaps some formal way to tag the package as unusable by certain downstream projects?
Did you ever visit crazyguyonabike.com? A long time ago I had the pleasure of following the journey of a friend of a friend of a friend on that site:
https://www.crazyguyonabike.com/doc/?doc_id=2405
Stuff like that I guess?
I'm not sure it's anything to fret about. Someone who has the ability to inject a prompt into your AI probably has the ability to run arbitrary code as your user. The prompt injection is the strictly less worrying part of the exposure you have.