I think @Kimi_Moonshot just reset my token for the week 😊
Thank God! I already had a lot planned out for the weekend; now I can achieve more
Hoping that was intentional and not a mistake.
Learning backend dev & security can be wild. Just learned about "Burst Vulnerabilities" in rate limiting.
If you use a Fixed Window algorithm, attackers can time a massive spike right at the window boundary to bypass your limits. Switching my FastAPI setup! 🛠️
About to provision the first PurpleToad Mail server 🐸
Now the real work begins.
Let's see how many things break before everything works.
I'll share the journey.
@purpletoadmail#buildinpublic
One of the craziest feelings as a builder is the strong urge to keep coding, building, and refining instead of actually doing marketing.
It always feels more “sane” to stay in the product than to talk about it 😄
But at the end of the day, building in silence doesn’t really get you anywhere.
There’s always that tension between building and being visible.
How do you personally balance both?
#buildinpublic
Introducing PurpleToad Mail 🐸
Modern email hosting. Built for AI agents.
Email hasn’t really changed in years. It’s still locked inside rigid providers, built for humans clicking buttons, not systems that need to act on data.
PurpleToad Mail changes that.
It’s email infrastructure designed to be programmable from the ground up:
• Custom domains support
• Multiple domains per account
• Mailboxes and inbox management
• MCP integration for AI-native workflows
• Webhook-based delivery for real-time automation
• Full data export and control with no vendor lock-in
• Built for founders, builders, and AI agents that actually do work
This isn’t “email with AI added on top.”
It’s email designed to be used by AI systems from day one.
Join the waitlist: https://t.co/vOTtiZVl6u
#buildinpublic
Seeing all my recent posts, someone might think I've switched from Mobile Engineer to Infrastructure Engineer 😄
Not quite.
I'm still building mobile apps every day.
I've just been spending a lot more time understanding everything around them.
Turns out the deeper you go into infrastructure, backend systems, and email delivery, the more it changes how you think about software as a whole.
Still a Flutter guy.
Just with a few more tabs open these days.
@dannytommyX https://t.co/rHqj9WrUCi is your modern email hosting platform, with near unlimited domain and mailbox support and it’s AI agent native and with unmatched price line.
You can easily manage your emails using our mcp server.
Still in the making though
I never understood why email has to feel so restrictive.
Want multiple domains?
Upgrade.
Need more mailboxes?
Upgrade.
Want your AI agents to have their own email addresses?
Figure it out yourself.
Need to leave one provider for another?
Good luck.
So I started building PurpleToadMail.
Email for builders.
Multiple domains.
Countless mailboxes.
AI-agent-friendly.
No vendor lock-in.
More soon. 🐸
#buildinpublic
Over the past few months, I've been exploring infrastructure, backend systems, and especially email delivery.
What started as curiosity became experiments.
Experiments became prototypes.
And prototypes slowly became something real.
I'm finally putting together a landing page for a project I've been quietly working on.
More details soon.
For now, let's just say it sits at the intersection of email infrastructure and helping builders move faster.
👀
@_KanyeDev Riverpod is great, BLoC is probably greater but too verbose.
I’ll use whatever state management approach the company think is great.
Always prefer Riverpod tho
I rarely watch videos for technical stuff; I usually prefer books and random articles.
I believe technical people have become less patient lately, so if an LLM can give them an answer, they won’t bother searching, crazy! But yeah, except when working on really technical or new stuff (shiny new things in Dart or Flutter, etc.) or illustrations of very complex topics.
My take though.
@dannytommyX I can totally relate, man. But I’m between stages 3 and 4.
Though I’m still holding tight to my 9to5 to make ends meet.
And for caring less about money and the average modern person’s life, I’m with you there.
Crazy 🙂
I accidentally fell into the email infrastructure rabbit hole.
At first I thought email was simple:
Send email.
User receives email.
Done.
Turns out that's not how it works.
SPF.
DKIM.
DMARC.
Reputation.
Bounce handling.
Deliverability.
Dedicated IPs.
Shared IPs.
Domain warming.
The list keeps going.
It's fascinating how much engineering exists behind something most people take for granted.
The best infrastructure is invisible.
Nobody notices when email works.
Everybody notices when it doesn't.
For most of my career, I've been deep in mobile development.
Flutter. App architecture. State management. Performance optimization. Native codes.
But over the last few months, I've found myself spending more time outside mobile than inside it.
I've been diving into:
• DevOps
• Infrastructure
• Backend systems
• AI tooling
• Email delivery
• Self-hosting
The funny thing is that the deeper you go, the more you realize how much software exists beneath the software users actually see.
A mobile app is often the easiest part.
The infrastructure, automation, reliability, monitoring, deployments, queues, and messaging systems underneath are where things get really interesting.
Still learning. Still breaking things. Still rebuilding them better.
I think Kimi Code is seriously underrated.
While everyone is busy talking about the usual coding models, Kimi Code has been surprisingly good in my experience.
Curious why it doesn't get mentioned more often
@Kimi_Moonshot
Installed Ollama tonight for the first time just to tinker locally.
Feels like the beginning of another rabbit hole.
Been quietly exploring a lot over the past year:
AI, products, automation, experiments, systems.
Think I’m finally ready to start sharing again 😎