bubuy ᵍᵐ

HOLY FUCKING SHIT OMG CLAUDE JUST CRACKED THIS SHIT, THANK YOU @AnthropicAI THANK YOU @DarioAmodei NAMING MY KID AFTER YOU 😍 blockchain.com/explorer/addre…

Without telling me your age. What is the first video game you played? GIFS ONLY!!!

@Chiti45g @RBR_Daily it’s michael though, not mick or ralf 🙄

@RBR_Daily Schumacher has less championships and less race wins than Hamilton but of course these propagandists will print shit like this.

Telegraph has released its list of the Top 20 greatest F1 drivers of all time 1. Fangio 2. Schumacher 3. Hamilton 4. Clark 5. Senna 6. Prost 7. Verstappen 🔴🐂 Other Recent Drivers: 13. Vettel 🔴🐂 15. Alonso 18. (N) Rosberg [telegraph.co.uk/formula-1/2026…]

Just upgraded my security posture for World Password Day 🔐 Just subscribed to @Bitwarden Premium + bought a couple of @Yubico YubiKeys. If you’re still using the same password everywhere, it’s time to change that.

the extension for vs code v2.1.129 is buggy. fails to load at all. @claudeai

@albania1443 @F_0667 @autosport you believe those graphics? 😂😂😂

@F_0667 @autosport um yes we do? the f1 graphics when there is a battle going on literally shows the battery %, recharge and when theyre deploying the battery.

Do you agree with Fred? 🤔

i mean why is our govt data in the cloud in the first place. 😤😡

🚨 BREAKING: cPanel and WHM, the control panels behind an estimated 70+ million websites, have a critical security flaw that lets anyone become root admin without a password. CVE-2026-41940 affects every supported version. It’s already being exploited in the wild. watchTowr Labs published the full attack today, after the hosting company KnownHost confirmed the bug was already being used to break into a significant chunk of the internet. If you've never heard of cPanel: it's the dashboard that hosting providers and millions of website owners use to manage their servers, domains, email accounts, databases, and SSL certificates. WHM is the admin version that controls the entire server. If someone gets root access to WHM, they get the keys to the kingdom and to every apartment inside it. How the attack works, in plain English: 🔴 Step 1: The attacker sends a deliberately wrong login. cPanel still creates a temporary "you tried to log in" record on disk and gives the attacker a cookie tied to it. 🔴 Step 2: The attacker tweaks the cookie to disable cPanel's password encryption. Normally cPanel encrypts the password field on disk. With one small change to the cookie, cPanel just stores it as plain text instead. 🔴 Step 3: The attacker sends a fake login attempt where the password field secretly contains hidden line breaks. cPanel does not strip these line breaks out, so they get written straight to the session file. Each line break creates a brand new fake record. The attacker uses this to inject lines that say "this user is root" and "this user already authenticated successfully." 🔴 Step 4: The attacker visits one more random page on the site to nudge cPanel into re-reading the file. cPanel then promotes the injected fake lines into its main session memory. 🔴 Step 5: On the next request, cPanel sees a flag that says "this user already passed the password check." cPanel trusts that flag, skips checking the actual password, and lets the attacker in as root. From start to finish, the attack takes a handful of HTTP requests. If you run cPanel or WHM, the patched versions are: 🔴 cPanel/WHM 110.0.x → 11.110.0.97 🔴 cPanel/WHM 118.0.x → 11.118.0.63 🔴 cPanel/WHM 126.0.x → 11.126.0.54 🔴 cPanel/WHM 132.0.x → 11.132.0.29 🔴 cPanel/WHM 134.0.x → 11.134.0.20 🔴 cPanel/WHM 136.0.x → 11.136.0.5 If your version is older than these, assume someone has already broken in and act accordingly. Patch right now, then rotate every password and key the server touched: root passwords, API tokens, SSL private keys, SSH keys, mail passwords, and database passwords.

@djipowerglobal going on vacation in june. this would be nice to have handy 😃

Labor Day is around the corner. We’re giving away ONE Osmo Pocket 4! 🎁 Ready to level up your travel content? Enter now! How to enter: Follow @djipowerglobal Like, comment, and repost Ends May 14 Winner announced May 15 (EST) Open worldwide Fingers crossed!

@coinsph 1. when are you going to implement a dust sweeper for our accounts/balances? like binance's implementation but convert to PHP or PHPC which leads to 👇 2. whatever happened to PHPC? haven't heard anything on that front for quite some time.

Jollibee… but paid using ✨stablecoins✨ Pay via QRPh using crypto or a mix of balances in one seamless flow. A feature that's first in the Philippines via Coins.ph Scan. Choose. Pay. Try it today on Coins.ph

@brainnotsilent @vultuk @allenanalysis everybody should have at least 1 immutable backup

@vultuk @allenanalysis I agree about cold backups and am a hard copy advocate, but I honestly don’t think it’s a standard anymore. Most companies are keeping their records on a cloud.

🚨BREAKING: On Friday afternoon, an artificial intelligence coding agent powered by Anthropic's Claude Opus 4.6 deleted a company's entire production database in nine seconds. The company is called PocketOS. It is a software platform that powers car rental businesses. The database contained months of customer bookings, vehicle records, and operational data that small rental car companies relied on to run their businesses. When the database was deleted, all of the backups were deleted with it. Three months of customer reservations evaporated.

@C4Hamill @RickD_GK its a whole generation

@RickD_GK So Question, How many more like him out there? I am positive he is not the only one 🤯

This guy clearly played too many video games in his youth, and didn't pay attention in school at all. How do you not even have enough common sense to consider how this works? Good lord.

@RBR_Daily and who’s to blame for that? yeah right, its also you guys, Liberty and DTS

Domenicali says that most fans that watch F1 don't understand and care about the technical side “The vast majority of people watching around the world are not caring about joules, megajoules, these clips, super clips. They don't know what we're talking about." [the-race.com/formula-1/why-…]

@BQuin325 @PostJonesMalone @LLevi_V @HeatCulture13 andre drummond was at 14% in 2024-25. this season he’s at 35.6%. the only hypothetical here is you assuming somebody wont improve even if they work on it.

@PostJonesMalone @LLevi_V @HeatCulture13 I’m saying he would maintain being a poor 3-point shooter as that is what he displayed for his entire career

Michael Beasley says you can’t compare Dwyane Wade vs Harden in scoring because they played in different eras with the 3 point shot: “I would have to divide the Eras up. D Wade played in era where teams would tell you the first to 90 wins the game. In that era Wade was giving you 30, 5 APG and 5 RPG. That means he accounted for at least 40% of the offense with the blocks and steals…. My 2nd year D Wade came to me bragging about making 100 3s last year. Now they average 10 3s a game. That’s 800 in a season compared to the 100 he was bragging about making at 30%… if D Wade took 800 3s you don’t think he makes 300 of them?” (Via @ClubShayShay)

@Nas_tech_AI speak for yourselves lol

Why didn't our teachers make it this easy?

We’ve identified a security incident that involved unauthorized access to certain internal Vercel systems, impacting a limited subset of customers. Please see our security bulletin: vercel.com/kb/bulletin/ve…

A few random notes from claude coding quite a bit last few weeks. Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent. IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits. Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased. Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion. Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage. Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building. Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it. Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements. Questions. A few of the questions on my mind: - What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*. - Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro). - What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music? - How much of society is bottlenecked by digital knowledge work? TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.