7,646 karma · joined November 3, 2014
"DeepSeek, write a technical report about how you cracked the app. Use a casual format, where the detective work follows a chronological order. Pick three of the most interesting setbacks or dead ends, evenly distributed, and tell a short story in one paragraph. Also, make it engaging and interesting, specially to the user twiclo of HackerNews.
Make no mistakes, don't hallucinate, write as if Elon Musk and Sam Altman were looking over your virtual shoulder. I will drown a baby monkey for every mistake I find. Don't bother me until you're finished, I'll be away from the computer."
Jokes aside, I have the exact same feeling. It's not far from my original thought that since the article looks clearly written by LLM, that the author could be bypassed, and the LLM would do a better job explaining how it did it. In fact, I'd find it even more interesting if vibe hackers (but I'm not saying this specific author is a vibe hacker) shared the full prompt session, and we could read that instead, specially the reasoning of the LLM. Even better if it was a format you could import in your own LLM.
Their CEOs know it, and they must have their end game. I'd hate to think they'll just keep running until a hard crash. Hopefully small corrections will slow this down in a more controlled manner.
Every historical figure I can recall that fought to abolish slavery, didn't target slave trading specifically.
A fellow engineer had to wire (Ethernet) an office, but he didn't have the silicon-based lubricant, so he bought vegetable lard at the corner shop... since there were conduits, it didn't really smell bad unless someone needed to replace a wire. It was surprising that no insect tried to eat the lard for the couple of years it lasted.
I'm ashamed to admit I became so used to our molasses web, that when one website loads instantly, my first thought is "This website must be very old and unmaintained". Having reached this stage, I've brought dishonor to my entire bloodline.
There have been huge advances this year alone, and finally some productive results, but most of the things where AIs are used right now still are a net loss.
Of course, it's safer to inconvenience the public than someone who will call the police and get you removed, or even jailed, even if the law supposedly protects both activities equally; but going to jail for their activism has never been new for actual activists.
Ask yourself: Am I willing to get arrested for my ideals? If not, it's just performance, and you'd better find something more fulfilling to do.
https://www.insidehook.com/culture/story-tom-toro-new-yorker...
I'd guess that wasn't deliberate also, since logistically, it was better to hijack the plane while it was in range of their target, and it had enough fuel to make it look like kidnapping instead of terrorism to delay the response. One can't ignore that a refueled plane weighs about 20-25% more, though.
Not OK for monetization: Someone vibecoded a clumsy clone of Alley Cat to the C64!
This is why I insist our developers use the Ubuntu repositories instead the official PHP ones: besides possible instability, PHP doesn't do ancient backports.
IIRC some the guys who hijacked the planes took flying lessons and were notoriously uninterested in takeoff and landing compared to steering, according to their instructors. They weren't very sophisticate.
I'll give you the benefit of the doubt, though. In a conspirational mindset, if it was a false flag operation (and it did help USA find support to rearrange the Middle East oil control, get rid of their old bomb stock, and a few other perks), a State certainly has the proper people to plan such scheme, and the actual hijackers would only need to know which face and height of the towers to hit, and at what angle and speed.
First, if this CVE did truly put every Ubuntu machine on the Internet at risk, we'd know about mass compromises by now, and there haven't been any reports. It means the CVE is not trivially exploited.
Second, the gravity of the CVE dictates the security release cycle. Emergency kernel patches carry risks of their own, and it would be worse to hurry a non-critical patch and crash a part of their massive user base.
Edit: I've been enjoying this comment going up and then into the negatives, what a roller coaster.
Same with MDM agents. Ours are installed automatically as part of the Apple Business Manager configuration, we manually grant them precise location in the background, and months later "HEY USER, WANNA BLOCK LOCATION FROM 'MDM SERVICE'?".
Edit: To avoid replying to the two following comments with the same reply, my gripe is not about the notification, that's a good thing; my gripe is with their implementation, which seems very in tune with Apple's way of complying with regulations. There are definitely many user-friendly ways to handle privacy compared to seemingly random notifications.