

Imagine a robo-taxi driving you into 3 feet of water because it thinks it’s a road, and then not being able to get out of the taxi because there’s no human to unlock the doors. I think this could have been a real risk of fatalities.


Imagine a robo-taxi driving you into 3 feet of water because it thinks it’s a road, and then not being able to get out of the taxi because there’s no human to unlock the doors. I think this could have been a real risk of fatalities.


The S stands for Secure.


It’s security researchers finding security problems.


Thanks, that makes more sense.


July '26 in grey and Oct '25 in blue? Is this a mistake?
Laywer up, delete facebook, hit the gym.


You mean the bit where you pretended to “pretty strongly dislike AI” while having a shitfit that the whole of lemmy is blaming AI for this Microsoft bug despite the fact that only one comment (at the time) even mentioned it?
Yeah I read that and I thought it was pretty obvious that you like to fuck robots. Nice try!


Nice profile pic, who’s the artist?


What are you ranting about? I only see one comment mentioning AI and it’s not even a top level comment, nor is it the most upvoted comment in that comment chain.


Yeah exactly, I don’t understand how the original comment is still getting upvotes.
Since your comment it gained (+36, -11). People don’t read, I guess.


Where did they say it was a client side bug?


Being vulnerable to AI psychosis seems to be a trait shared by all of these CEOs. It’s disappointing and frankly, extremely depressing.


This looks completely insane. Good luck to the dev!


These people wouldn’t recognise art if it walked up and slapped them in the face.


When is Sativa Nutella going to resign?


Fuck off, this is an open source community. You don’t even own the copyright to your own project.


Just use FreeTube instead of this vibe-coded slop.
You’re right, at the least the name should have the year in it so that we know if it’s a new vulnerability or an old one.
And since a product can have multiple vulnerabilities in the same year we should have a number that increments with each new vulnerability found.
Also, since one vulnerability can affect multiple products (eg. a vulnerability in a library), we can’t use the product names to identify the vulnerability (as that could be quite a long list). We will just use the acronym for our naming scheme so that we can distinguish our list of numbers from other lists of numbers like book ISBNs or ICQ numbers.
We could call our naming scheme the Cool Vulnerability Eponym.
So the vulnerability name would end up as something like
CVE-2026-123456.