Show HN: I spent more time writing tweets than building. So I fixed it
tweetbl.ink
Last month, I tracked my time. I spent 6 hours building a new React component. Then spent 1 hours trying to tweet about it. Not a thread. Just one tweet. I wrote 12 drafts. Deleted all of them. Eventually posted nothing.
This isn't writer's block. It's decision paralysis. Every tweet requires dozens of micro-decisions: Tone? Format? Audience? Length? Thread or single? Question or statement? Should I be casual or professional? Technical or accessible?
When I talked to other developers, they had the same problem. One friend told me he has 20 draft tweets sitting in his notes app. He builds cool stuff but rarely shares it because "tweeting is exhausting."
I built a browser extension that handles those micro-decisions. You give it your idea. It generates multiple versions in different formats (question, thread, how-to, etc.) and tones. You pick one, maybe edit it, and post.
The key insight: you don't need AI to write tweets. You need it to remove the friction of formatting and structuring your existing ideas.
If you want try it: