By Eve Sampson and Christina Anderson from NYT World https://ift.tt/XgI3Zap
via IFTTT
Wednesday, 30 April 2025
Tuesday, 29 April 2025
Monday, 28 April 2025
2025 Canada Federal Election Live Results
By Joel Eastwood, Martín González Gómez, K.K. Rebecca Lai, Eric Rabinowitz, Matina Stevis-Gridneff, Urvashi Uberoy and Christine Zhang from NYT World https://ift.tt/qmkESxu
via IFTTT
Sunday, 27 April 2025
Saturday, 26 April 2025
Friday, 25 April 2025
Thursday, 24 April 2025
Wednesday, 23 April 2025
Tuesday, 22 April 2025
How Pope Francis Catalyzed the Catholic Right in the U.S.
By Ruth Graham, Melanie Bencosme, Jon Hazell and James Surdam from NYT World https://ift.tt/kW9qSOP
via IFTTT
Monday, 21 April 2025
Sunday, 20 April 2025
Saturday, 19 April 2025
Friday, 18 April 2025
Thursday, 17 April 2025
Wednesday, 16 April 2025
Tuesday, 15 April 2025
New best story on Hacker News: Cursor IDE support hallucinates lockout policy, causes user cancellations
Cursor IDE support hallucinates lockout policy, causes user cancellations
790 by scaredpelican | 276 comments on Hacker News.
Earlier today Cursor, the magical AI-powered IDE started kicking users off when they logged in from multiple machines. Like,you’d be working on your desktop, switch to your laptop, and all of a sudden you're forcibly logged out. No warning, no notification, just gone. Naturally, people thought this was a new policy. So they asked support. And here’s where it gets batshit: Cursor has a support email, so users emailed them to find out. The support peson told everyone this was “expected behavior” under their new login policy. One problem. There was no support team, it was an AI designed to 'mimic human responses' That answer, totally made up by the bot, spread like wildfire. Users assumed it was real (because why wouldn’t they? It's their own support system lol), and within hours the community was in revolt. Dozens of users publicly canceled their subscriptions, myself included. Multi-device workflows are table stakes for devs, and if you're going to pull something that disruptive, you'd at least expect a changelog entry or smth. Nope. And just as people started comparing notes and figuring out that the story didn’t quite add up… the main Reddit thread got locked. Then deleted. Like, no public resolution, no real response, just silence. To be clear: this wasn’t an actual policy change, just a backend session bug, and a hallucinated excuse from a support bot that somehow did more damage than the bug itself. But at that point, it didn’t matter. People were already gone. Honestly one of the most surreal product screwups I’ve seen in a while. Not because they made a mistake, but because the AI support system invented a lie, and nobody caught it until the userbase imploded.
790 by scaredpelican | 276 comments on Hacker News.
Earlier today Cursor, the magical AI-powered IDE started kicking users off when they logged in from multiple machines. Like,you’d be working on your desktop, switch to your laptop, and all of a sudden you're forcibly logged out. No warning, no notification, just gone. Naturally, people thought this was a new policy. So they asked support. And here’s where it gets batshit: Cursor has a support email, so users emailed them to find out. The support peson told everyone this was “expected behavior” under their new login policy. One problem. There was no support team, it was an AI designed to 'mimic human responses' That answer, totally made up by the bot, spread like wildfire. Users assumed it was real (because why wouldn’t they? It's their own support system lol), and within hours the community was in revolt. Dozens of users publicly canceled their subscriptions, myself included. Multi-device workflows are table stakes for devs, and if you're going to pull something that disruptive, you'd at least expect a changelog entry or smth. Nope. And just as people started comparing notes and figuring out that the story didn’t quite add up… the main Reddit thread got locked. Then deleted. Like, no public resolution, no real response, just silence. To be clear: this wasn’t an actual policy change, just a backend session bug, and a hallucinated excuse from a support bot that somehow did more damage than the bug itself. But at that point, it didn’t matter. People were already gone. Honestly one of the most surreal product screwups I’ve seen in a while. Not because they made a mistake, but because the AI support system invented a lie, and nobody caught it until the userbase imploded.
