Kushagra Gour @css_battle

✏️ Scribbble // Sep '26: 💰 Big milestone - made $500 in revenue (+70%) 🎉 ⚙️ Mostly attributed to increased pricing, but no. of sales was also 20% more! 🌐 Made some improvements on marketing website - demo animation, testimonial, pricing

made a game where you carve pumpkins with your webcam 🔪🎃 it's hard ↓

Just got off the phone with the most intelligent person I know. He said this is COVID 2.0. Everything on the internet is going to get hacked. One by One. It'll start affecting people close to you and one day a big bank will get penetrated and their data will be wiped clean. Thousands of accounts will show $0 and there will be no way of recovering their true balance. When this happens we will go on grid lock down. They will shut down the internet all over the world for 3 months to patch every single exploitable bug with the help of super advanced AIs. This will cause mass panic and chaos. You need to stock up on food, water, gold, silver, guns, ammo, and cash. ASAP. Rumors are that this global shutdown will start on November 17th.

Next week will be an exciting week for Antigravity! Lots of shipping will happen.

🪁 Introducing Bento - calmkite.com/bento/ Turn your messy Mac desktop into a beautifully organized space, in one click. Here's the before & after 👇

scribbble suddenly getting low number of sales. all numbers look usual, no idea why sale is dropping. if there was a product that tells me why sales drop/increase it would be very useful!!

Security called me at 6:12 AM today. "Patch every PHP server immediately." I asked what happened. "Two critical vulnerabilities. Remote code execution. No authentication required." Cool. How many PHP servers do we have? According to inventory: 12 According to reality: Nobody knows. We found one running WordPress. Three running old internal tools. One under someone's desk. Two inside vendor appliances. A forgotten employee directory from 2016. And a server named: PHP-OLD-DO-NOT-TOUCH Naturally, that one runs payroll exports. Then we found a PHP 5.6 box. I asked who owned it. The documentation said: BRIAN. Brian left in 2019. We called Brian. He said: "Oh wow, that's still running?" Excellent. By 8 AM, leadership joined the incident call. CEO: "Can hackers actually get in?" Security: "Potentially yes." CEO: "Without a password?" Security: "Yes." CEO: "Then why do WE need passwords?" Not the lesson. Finance asked if we could wait until the weekend to patch because downtime affects revenue. Security explained that the alternative was letting strangers execute code on our servers. Finance asked for a cost comparison. At 9:17, someone suggested temporarily taking the vulnerable websites offline. Marketing refused. "Our campaign is live." So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover. We finally patched everything we could find. Then our scanner discovered another PHP server. Hostname: TEMP-PHP-2014 Uptime: 4,512 days. Nobody knows what it does. Nobody owns it. Nobody can shut it down. But every time we block network access, the warehouse stops printing shipping labels. Security has classified it as critical infrastructure. It is running PHP 5.4. The vulnerability has existed longer than half our employees. The emergency patch took four hours. Finding out what PHP actually runs took eleven. The internet isn't held together with code. It's held together with servers everyone is afraid to turn off.