Mehbub

@Mr_PrithviYadav Good work. What did you build?

My first SaaS payment just hit my bank Built it. Shipped it. Sold it ₹60,000 from my first client I’ve never earned like this before. Not from something I created. This isn’t just money It’s proof. Proof that building something real works. The journey has officially begun.

@satwiksps @kirat_tw Will do mate.

@_devleo10 @kirat_tw Hey congrats we made it 🎉. It would be awesome if you could add your proposal to the repo here: github.com/satwiksps/GSoC… It will help out future students who want to see what a good application looks like. It's just a quick fork and PR, and it really helps out the community.

Last year, I applied for Google Summer of Code. Got rejected. This year, I applied again and got accepted into GSoC 2026 with UC OSPO. If you got rejected last year, try again. That's literally it. @kirat_tw Thanks for all the good influence. #GSoC #GSoC2026

@Suman_N_Jain My guy🤜🤛

Super proud daa !

TLDR for next time you migrate a domain: 1. update A record (IPv4) 2. update/delete AAAA record (IPv6) 3. fix www CNAME 4. wait for TTL

You deployed a new site on Vercel, updated the domain. Half the users still saw the old site...how would you find that what's wrong?

Fix was simple delete the AAAA @ record from your old DNS provider. Whenever you migrate hosting don't just update the A record check your AAAA record too.

The culprit was an AAAA record (IPv6) still pointing to the old server modern networks prefer IPv6 over IPv4 so half the users were routed to old hosting while the other half hit Vercel

I was in a similar situation. My first guess was DNS propagation checked whatsmydns.net, everything looked fine but the nslookup showed TWO IPs: 216.198.79.1 (Vercel ✅) 2a02:4780:11:... (Hostinger ❌)

Hey @render @anuraggoel , one of my clients was targeted by a phishing attack hosted on your platform. Credentials being harvested at: jhrbghrbgehj-off.onrender[dot]com Can you investigate? Happy to share more details.

@CLonarkar24 Bro hamare school mein aate the iye wala magic book sell karne

I am from this generation🫣 Are you??

@akashcorex Appreciate it bro.

Great useful tool. Much need bro 👍🏻

@code_codeforge lmic.tech

Drop your project URL Let’s drive some traffic

Used to take Ls in meetings because of my mic. Bad audio. “Can you hear me?” every time. So I built L-Mic — a free tool to test your mic before you embarrass yourself again. Real-time visualizer. Detects clipping + low volume. No signup. Just use → lmic.tech

In a nutshell: The model isn't the bottleneck. Your prompt is. Use budget models for UI work. Save the expensive ones for backend logic where precision actually matters. Prompt better. Spend less. @mannupaaji

Migrating to JSON now isn't a technical problem. It's a coordination problem. You'd need every single one of those systems to change simultaneously. That's not a version bump rather a decade long infrastructure project.

When UIDAI designed the Aadhaar data sharing standard in the early 2000s, they needed cryptographic proof that the document hadn't been tampered with. XMLDSig, the XML digital signature standard, was the right tool for that job at that time. JSON had no equivalent. XML was it.

Every fintech in India is parsing XML in 2026 and nobody is switching anytime soon.

@DnuLkjkjh Denying direct file access (.env) is just the obvious first layer. Secrets actually linger in git history. Ideally you can run trufflehog before every push + git-filter-repo to scrub old commits.

@_devleo10 i'd block .env, but also old commits and deploy files. secrets usually leak through grep paths before the obvious file read. are you denying git history too, or just direct file access?

You didn't get hacked. The tool your colleague uses got hacked. That's how Vercel got breached. Same result.