Quick question for builders: When did you ACTUALLY launch your waitlist? a) When you thought it was ready b) Weeks later after "one more feature" c) Right now because you saw this tweet I just went with (a) - ShipStory waitlist is LIVE Join the first 100 → Get 50% off…
shipstory.app
ShipStory - Turn Your Git Commits into Engaging Stories
AI-powered tool that transforms your GitHub commits into compelling tweets and blog posts. Build in public effortlessly.
ShipStory update - 124 followers (growing slowly but real people) - 12 waitlist signups (10% conversion!) - $0 revenue (not launched yet) - 1 determined builder (me) slow progress is still progress 📈
new week. clean slate. Last week i fell into old habits - consumed content instead of creating. watched tutorials, read threads, told myself it was "research" It wasn't. Monday reset: closed all tabs. opened VS Code. back to building ShipStory. Content consumption is…
you ever fall back into old patterns? spent the last few days deep in content consumption mode "just one more tutorial" "this thread has great insights" "let me read how THEY built their SaaS" told myself it was research really? it was avoidance because consuming is easier…
Just implemented HTTP-only cookie auth for ShipStory Users will never see this. No flashy UI. No feature announcement. But it's the security foundation that lets me sleep at night. Sometimes the most important code is invisible. Building trust > building features
Quick appreciation post: To the #buildinpublic community - you make coding feel less lonely. Your replies, your feedback, your own builds... it all matters. Building alone is hard. Building together is possible. Thank you for being here!
An honest question for builders👇 How do you decide what to work on when you have 100 ideas but no confirmation? 🤔 Or rather, no confirmation because you develop without having an audience? 📉 Do you follow your gut feeling, talk to users, or just put something on the market…
Become Known For Something Pick Your Lane: "The person who shares transparent metrics" "The person who helps with technical challenges" "The person building in public consistently" "The person with great onboarding insights" Consistency > Variety Better to be known for ONE…
Real decision I'm facing with ShipStory: Should I build X OAuth + auto-posting first (what users expect), or perfect the manual review flow (safer, more control)? The API Costs will explode when using X API Auto-posting = faster adoption Manual review = better quality, less…
I'm building ShipStory to help developers share their coding journey without the friction But right now? I'm still manually crafting every "building in public" post It's exhausting but also... kinda perfect? Because I'm living the exact pain point my tool solves Every manual…
It's Thursday and I'm trying to decide: push through or save energy? ShipStory is calling but so is my couch Sometimes the most productive thing is admitting you need a break what's your energy level this week? 🔋 #BuildInPublic #IndieHackers
Week One is ending after publishing waitlist for ShipStory. 100 followers → 122 (+22%). 🚀 12 waitlist signups (conversion: 10%). 📈 Shipped: HTTP-only cookie auth, frontend security improvements. Learned: security work is invisible but essential. Still building.
At my day job: 15 min standup about a button color. on my side project: shipped entire auth system in 6 hours. The irony of being 10x more productive on something that makes $0. Motivation is a hell of a drug <3
Building ShipStory taught me that the most auth tutorials store JWT in localStorage. That's a security risk (XSS attacks) ❌ Spent extra time implementing HTTP-only cookies instead‼ Users won't see the difference - but their data is safer 🔐
11 people joined the waitlist That's 11 developers who are tired of: - Switching between builder mode and content creator mode - Spending 2hrs/day on tweets - Letting their commits go to waste 89 spots left for 50% off lifetime shipstory.app
shipstory.app
ShipStory - Turn Your Git Commits into Engaging Stories
AI-powered tool that transforms your GitHub commits into compelling tweets and blog posts. Build in public effortlessly.
Spent yesterday implementing HTTP-only cookies for auth Most tutorials store JWT in localStorage and that's a security risk (XSS attacks). ⚠️ HTTP-only cookies can't be accessed by JavaScript and the usage should be the default Feels good shipping something most services skip…
An honest question for you guys... How do you deal with bots that like every one of your posts? These bots are not valuable interactions. They may increase my interaction rate, but that's about it. How do you deal with them? Ignore them, block them?
💡 Today's "why didn't I know this earlier" moment: Database imports in Docker don't copy server configs. Tables: utf8mb4_german2_ci ✅ Database default: utf8mb4_unicode_ci ❌ Spent 30 hours debugging collation errors. One-line fix for database container in docker-compose.yml…
🎯 Quick debugging tip: MariaDB throwing collation errors after importing a database? Check this: docker compose exec db mariadb -e "SHOW VARIABLES LIKE 'collation_database';" Your imported tables keep their collation. Your database uses container defaults. Mismatch = errors.…
United States 趋势
- 1. Cowboys 68.7K posts
- 2. Nick Smith 14.3K posts
- 3. Kawhi 4,329 posts
- 4. Cardinals 30.8K posts
- 5. #LakeShow 3,411 posts
- 6. #WWERaw 62K posts
- 7. Jerry 45.3K posts
- 8. Kyler 8,445 posts
- 9. Blazers 7,951 posts
- 10. Jonathan Bailey 22.9K posts
- 11. Logan Paul 10.2K posts
- 12. No Luka 3,589 posts
- 13. #WeTVAlwaysMore2026 211K posts
- 14. Jacoby Brissett 5,607 posts
- 15. Valka 4,843 posts
- 16. Cuomo 175K posts
- 17. Pickens 6,666 posts
- 18. Dalex 2,537 posts
- 19. Bronny 14.8K posts
- 20. Pacers 12.8K posts
Something went wrong.
Something went wrong.