Technopathy is moving to Hashnode

UpdatedMay 11, 2026

•1 min read

I build systems that work — technically sound, security-first, and actually useful to the people who depend on them. Creator of the UNICORN Binance Suite — 6 open source Python libraries with 2.8M+ PyPI downloads and 388+ dependent public projects. Currently pioneering AI-driven open source maintenance: running a controlled AI agent that maintains production code and documenting what it means for engineering teams. Vienna, Austria 🇦🇹

After a few years on Medium, Technopathy is moving to Hashnode.

The main reason: Medium blocks AI crawlers by default — no opt-in, no opt-out, no per-author control. In 2026, AI assistants are becoming a primary discovery channel for technical content. If Claude or ChatGPT can't read my articles, I'm invisible to a growing part of my potential audience. And that's a decision Medium made for me, not with me.

On Hashnode with my own domain, I control the robots.txt. My content can be indexed, read, and recommended by AI assistants. That's exactly what I want.

All existing articles will be migrated from Medium shortly. The new URL is https://blog.technopathy.club.

If you've been following me on Medium — welcome to the new home.

I hope you found this informative and useful.

Follow me on Binance Square, GitHub, X, and LinkedIn, or join Telegram for updates on my latest publications. Constructive feedback is always appreciated.

Thank you for reading, and happy coding! ¯\_(ツ)_/¯

6 views

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

The Complete Binance Python API Guide (2026)

REST, WebSocket, order books, trailing stops, and cluster-scale infrastructure — the production-grade Python stack for Binance.

May 12, 202628 min read136

The Complete Binance Python API Guide (2026)

Binance Fixed the IP Whitelist Gap. The Disclosure Process Is Still Broken.

I reported the listenKey issue in December 2024. Thirteen days of recent supply-chain findings pushed me to re-test it — and the vulnerability now appears closed after being rejected as “Social Engineering.”

May 5, 202611 min read234

Binance Fixed the IP Whitelist Gap. The Disclosure Process Is Still Broken.

The PyPI Package Was Clean. That Was the Problem.

A near-identical clone of my Binance WebSocket library had no payload — but it spoofed identity, shadowed the import path, linked to a 404 repo, and came from the same account as pybotnet.

May 5, 202613 min read26

The PyPI Package Was Clean. That Was the Problem.

Your Binance DepthCache is rotting — here's the proof in 25 hours

A 25-hour forensic benchmark showing why Binance Spot DepthCaches need an explicit retention policy — not just correct synchronization.

Apr 29, 202614 min read64

Your Binance DepthCache is rotting — here's the proof in 25 hours

I had a fake job interview. It was a malware delivery chain.

A fake recruiter tried to turn VSCode workspace trust into silent code execution. Here is the attack chain, the infrastructure, and the IOCs.

Apr 29, 202617 min read120

I had a fake job interview. It was a malware delivery chain.

Technopathy

27 posts

DevSecOps · Python · AI-driven Development · Real-world findings from production systems.

Command Palette

Comments

More from this blog