pbopps

Hi

I'm building a tool called ArchitectGBT — it helps developers and founders pick the best AI models for their projects in 60 seconds, with cost breakdowns and starter templates.

I've personally wasted hours, on trial-and-error choosing models, often ending up overspending or getting subpar results. I'm curious—how many of you have lost money or time because of bad model choices? Would love to hear your stories.

If you’re interested in testing something that could prevent this, join the waitlist:

architectgbt.com

Thanks!

Hi everyone,

I just launched AllPub on Product Hunt a week ago and got some great traction. Now looking to refine based on community feedback from HN.

The Problem: Developers who write technical content waste hours manually copy-pasting articles between Dev.to, Hashnode, and other platforms. Formatting breaks. Tags are different. Summaries need adjustment. It's just tedious.

What I Built: AllPub connects to your Notion workspace. Write your article. Our AI generates 5 title options, hashtags, and platform-specific summaries. Hit publish and it goes to Dev.to and Hashnode simultaneously with correct formatting.

Current Status: Free beta. No paywall yet. I want feedback before I monetize.

What I am looking for:

Is this actually solving a real problem you face?

What features would make this essential for your workflow?

What's missing?

Would you pay for this? At what price point?

Try it free: allpub.co (no credit card required)

https://www.producthunt.com/products/allpub?utm_source=twitt...

Would love to hear what the HN community thinks.

Hi HN,

I built AllPub (https://allpub.co) to solve a personal problem: I write technical articles and waste 3+ hours manually copying them to Dev.to, Hashnode, Medium, Ghost.

Each platform has different: - Markdown flavors (syntax highlighting, embeds) - Image handling (CDN requirements, optimization) - SEO requirements (canonical URLs, meta tags) - Formatting quirks (tables, code blocks)

AllPub connects to your Notion workspace (notion, dev.to, hashnode)and handles all of this automatically.

*Tech stack:* - Next.js (frontend) - Supabase (backend) - clerk (auth) - Platform APIs: Dev.to, Hashnode, Notion - Vercel (hosting)

*Challenges I faced:*

1. Notion's API is powerful but complex - Block-based structure (not linear Markdown) - Nested content handling - Image URLs are ephemeral (expire after 1 hour)

2. Each platform's Markdown parser is different - Dev.to: Liquid tags, front matter - Hashnode: GraphQL API, custom syntax - Medium: HTML-based (not Markdown) - Ghost: JSON content format

3. Image hosting/CDN - Notion images expire - Had to proxy/re-upload to stable CDN - Optimization per platform (sizes, formats)

4. Rate limiting across 4+ APIs - Orchestrated parallel publishing - Retry logic for failures - Status tracking per platform

*Technical decisions:*

- Why Supabase? (Postgres + Realtime, great DX) - Why Next.js? (SSR for landing page, API routes for webhooks) - Why not build a Notion plugin? (API limitations, better UX as standalone)

*Current state:*

The product is live and functional. Launching on Product Hunt this week.