Helping builders ship in AI & Web3 @fluxor_ | Blockchain dev | Full-stack (MERN) | Open source contributor | Speaker
1.1.1.1
Joined July 2018
- Tweets1.6K
- Following297
- Followers874
- Likes3.9K
October 2026 internet speedrun: get hacked → ship a patch → file for bankruptcy → repeat. Wild month to be online.
Kanishak 🔜 DevCon VIII retweeted
@kartiktalwar sir please karvado approval @ETHGlobal
🥲😭😭😭
Kanishak 🔜 DevCon VIII retweeted
OCTOBER 21, 2026: A BRUTAL DAY FOR THE INTERNET
Certificate trust failures.
Customer secret exposure.
Critical RCEs.
Platform disruptions.
CDN latency.
Broken builds.
AI service errors.
GitHub. Railway. Cloudflare. Sentry. OpenAI. Anthropic. CircleCI.
Different incidents. Different root causes. One uncomfortable truth:
Our digital infrastructure is only as resilient as its weakest dependencies.
Patch confirmed vulnerabilities.
Rotate credentials on confirmed or reasonably suspected exposure.
Revoke compromised certificates.
Verify before amplifying breach claims.
Build redundancy before the next outage.
The internet doesn’t need more panic.
It needs better security and resilience.
♻️ Repost so developers can investigate, verify, and respond.
Kanishak 🔜 DevCon VIII retweeted
4/ 💻 Open Source Hub
The future of Ethereum is built in the open.
Meet the developers, contributors, and communities advancing open-source technology, exchange ideas, and discover new ways to contribute to the decentralized ecosystem.
With @WarangShankar, @dappdost, @hpdang & @fossasia.
Anyone would like to suggest me some men care products, having too much acne and dark spot on face – at Noida, India
OCTOBER 21, 2026: A BRUTAL DAY FOR THE INTERNET
Certificate trust failures.
Customer secret exposure.
Critical RCEs.
Platform disruptions.
CDN latency.
Broken builds.
AI service errors.
GitHub. Railway. Cloudflare. Sentry. OpenAI. Anthropic. CircleCI.
Different incidents. Different root causes. One uncomfortable truth:
Our digital infrastructure is only as resilient as its weakest dependencies.
Patch confirmed vulnerabilities.
Rotate credentials on confirmed or reasonably suspected exposure.
Revoke compromised certificates.
Verify before amplifying breach claims.
Build redundancy before the next outage.
The internet doesn’t need more panic.
It needs better security and resilience.
♻️ Repost so developers can investigate, verify, and respond.
next week i'll be in mumbai to attend @EFDevcon . any side event is happening before 3rd Nov. to mention the link
@dappingHQ
@ZeroXSpace_
@TeamGRYD
see ya'll in Mumbai for @EFDevcon !🫶
let's connect if you'll be around, i'd like to make new friends, open to listen ideas , cook something together & explore the film city together!
I built the same API in 5 languages today: Python, @golang , @nodejs .js, C++ and Rust.
Then I hit each one with 4,000 concurrent users for 30 seconds, with RAM limits from 4 GB down to 64 MB.
Same endpoints, same Postgres, same Redis. Here's how the race went 🧵
visit link and check the detailed stats:))
github.com/kanishak11-cyber/…
🤖 Made with AI
12/ Takeaways:
• Raw speed: C++, Rust and Go are in the same league. Single-process Python and Node.js aren't.
• Memory: C++ is in a class of its own.
• A cache helps most where the DB driver is slow.
• Config (workers, TCP_NODELAY, GOMEMLIMIT) matters as much as language.