@Apple@iCloud iCloud folder zero-byte-truncated my password manager database, then synced it to all devices.
Gave me a decent scare; good thing I was able to recover it from a copy.
The price to rent an Nvidia H200 just collapsed from $7/hr to $4/hr in three weeks.
A -40% drop in the cost of the single most strategic asset in tech.
When the underlying commodity that powers your entire thesis loses 40% of its value in a month, that usually means one of two things: supply finally caught up, or demand was never as deep as the headlines said.
Either way, somebody is selling.
So why is the AI trade still pricing in scarcity?
DO NOT use Telegram in sensitive applications. Telegram does not need to have its message encryption broken for users to be tracked at the network layer. Telegram sends MTProto over unencrypted TCP, exposing auth_key_id - a long-lived identifier tied to the client’s authorisation key. An ISP, hotel WiFi operator, mobile carrier, transit provider, or surveillance system on the network path can see that identifier if they can observe the traffic. It can remain stable across app restarts, IP changes, VPN use, network switches, and location changes. Secret Chats protect message content, but this leak is below that layer. That makes the attack passive. The risk is in retroactive correlation. Think a journalist using Telegram from different networks for months, then joining hotel or corporate WiFi under a real name. That one identity anchor could make old logs searchable for the same auth_key_id. The fix is simple - mandatory transport encryption for all MTProto connections, with no unencrypted fallback. Telegram chose not to do this. Source: @kaepora https://t.co/TJALYAwaOs
This is terrifying @Ledger.
I just received a physical scam letter at my home address in Italy 🇮🇹
How the hell do scammers have access to the addresses of Ledger users? This goes way beyond phishing emails now.
People’s safety is literally at risk.
@levelsio 1-star reviews in Germany can be taken down due to a loophole in the German law. You can't trust Yelp or Google Maps there. Lower ratings are likely more honest, and, frankly, better.
It's fascinating how vibe coding allows people to be absolutely clueless about what they're shipping. An even bigger new era of cyber negligence is coming.
This is what happens when you vibe-code a product that handles sensitive user data:
I saw this extension announcement going viral and thought it looked cool, so I checked it out.
My first concern was whether my emails would be sent to someone I don't know. I was relieved to see you could bring your own Anthropic API key.
The website states your API key and email text go straight to Anthropic and "never touch our servers."
Then, when you try it, you hit a paywall where you can input your key. Same claim: your key is stored locally and calls go directly to Anthropic.
I got curious and decided to check the Chrome extension source code.
Damn. Not only does it send your email text to their servers, it also sends your API key!
So both claims, that it calls Anthropic directly and that your API key is stored only locally, are completely false.
I'm giving the creator the benefit of the doubt and assuming this was negligence, not malice. He used his real name on Stripe and in the Chrome Web Store.
But the lesson is bigger than one project: building with AI is fun, but if you're handling people's data, making security claims, and charging money, you need real review before shipping.
@theonejvo Do you think there's a point in continuing to burn tokens and time? Tried that briefly: out of scope, duplicate this. Completely non-transparent and sometimes plain incompetent triage is what I saw.