Skip to content
Weekly ship log

Changelog

What we shipped, week by week. No marketing fluff. Features, fixes, and security changes as they land.

feature

Engage from the inbox, YouTube series, X everywhere

  • ·Like and Repost buttons on inbox items, next to the reply that already worked. Live on Bluesky today. X needs you to reconnect the account, because likes need a permission the old connection was never granted
  • ·Honest about the gaps: Instagram and YouTube have no API for liking a comment, Facebook comment likes need a permission we do not request, and LinkedIn does not let third-party tools read a member's activity at all. The buttons are hidden on those rather than shown and failing
  • ·YouTube posts can pick the series (playlist) they belong to. Optional, nothing preselected, and the video is added right after it finishes uploading
  • ·The app says X, not Twitter, everywhere you read it
feature

Smarter AI adapter + pre-publish lint banner

  • ·Per-platform taxonomy (X, LinkedIn, Mastodon) now feeds real throttle/ban rules into the AI rewriter: LinkedIn drafts stop putting links in the body, Mastodon drafts drop hashtag stuffing and clickbait phrasings, X drafts avoid engagement-bait that tanks reach
  • ·New amber pre-publish warning banner: flags risky patterns before Post Now / Schedule fires, offers Fix with AI or Post Anyway, never blocks, you always have final authority
  • ·Per-platform image adapter: upload once, get per-platform blobs (blur-fill or crop) matching each network's aspect-ratio. EXIF auto-orients portrait phone shots. Proactive flags warn on low-res / wrong-aspect images before post
  • ·AI content adapter tiered structural directive: ultra-short platforms (X, Bluesky) commit to ONE insight; tight platforms (Mastodon, Pinterest) allow up to two; long-form (LinkedIn, Facebook) unrestricted: fixes posts that truncated mid-list
  • ·Telegram, Discord, and Slack live, all three webhook-based, zero OAuth friction. Bot token + chat ID for Telegram; webhook URL for Discord and Slack
  • ·Plan caps rebalanced to match reality: Starter 3→5 social platforms, Growth 7→10, Scale 8→unlimited
  • ·Clear button next to Auto-Adapt so you can wipe the composer and start fresh without losing media or platform selection
fix

Launch-day stability pass

  • ·AI per-platform content rewriter is now ~6× faster (parallelized across every connected platform)
  • ·Pinterest and YouTube char limits properly enforced; AI output now targets 80-95% of platform budget instead of staying artificially short
  • ·Mastodon integration: preview crash + overflow on account card fixed
  • ·OAuth signup no longer chokes on long Google/LinkedIn avatar URLs
  • ·MFA is now opt-in (was mandatory, killing signup conversion)
  • ·Google Business Profile connect card marked coming-soon pending API approval
feature

TAAFT launch day

  • ·Featured on TAAFT. First 100 signups in the door
  • ·New `/automated-social-posting` SEO landing page with 7-platform comparison
  • ·"What Made4Founders Replaces" grid added to homepage (Carta, Hootsuite, DocuSign, Gusto, DocSend, 1Password with real prices)
  • ·Check-your-email confirmation screen after signup (was silently redirecting)
  • ·Signup flow now creates Organization + Business automatically
  • ·Rate limits loosened for launch traffic (3/min → 10/min on register)

Weekly cadence

Made4Founders ships on a seven-day cadence. Every Friday a batch of new features, bug fixes, and security updates rolls to production behind a feature-flag canary, then widens to all customers over the weekend. The entries on this page are the authoritative log of what landed. If it's not in the changelog, it wasn't shipped. Blog posts and marketing claims always reference this log.

Three entry types

Entries are tagged as feature, fix, or security. Features get the most real estate because they are what founders notice. Fixes get a one-line summary plus the original symptom, so if you hit the bug you can confirm the fix covers your case. Security entries always include scope, affected versions, and whether any customer data was exposed. We never hide security changes behind general update language.

Written by the shippers

Each entry is written by the engineer who shipped the change, not a marketing team passing along tickets. That means the language stays technical where it needs to be. Actual module names, real behavior changes, concrete numbers. Founders reading this log should be able to tell within ten seconds whether this week's ship affects their workflow, their billing, or their data.

Get the weekly ship summary

One email, every Friday. What shipped, what's next, what I'm wrestling with. Unsubscribe in one click.

Sign up (digest included)