LinkedIn cross-posting, per-IP limits, and landing redesign shipped

This week I shipped three things that make git-to-x safer, more visible, and easier to use. You can now cross-post to LinkedIn, the public endpoints have per-IP rate limits that fail open on errors, and the landing page got a full redesign that explains safety and how posting works.

What shipped

• –LinkedIn cross-posting: OAuth connect, token storage, a settings toggle, and a background worker hook so posts can go to LinkedIn without interrupting your workflow.
• –Landing redesign: clearer hero messaging, trust pills under the CTA (open source, read-only, code never leaves GitHub), a rate calculator, and new integrations listed (Threads, Bluesky) so people can see reach potential at a glance.
• –Per-IP rate limits on unauthenticated public endpoints. The limiter is conservative and built to fail open on database errors so a hiccup never turns into a 500 for visitors.
• –Analytics placeholder: Google Analytics 4 is wired but dormant until you set the ID; the example .env is published for self-hosters.
• –Safety and security updates: the security page now lists exactly what fields are stored (stats and metadata, no code), commit reading uses numbers-only GraphQL queries, and commit stats are fetched without sending diffs to our servers.
• –UX fixes: the "Post my first card now" CTA is prominent, the daily auto-post timing is clarified (morning runs), and templates/settings no longer clobber each other when LinkedIn is enabled.

Why this matters

If you use git-to-x to share daily work, these changes lower friction and increase trust. LinkedIn cross-posting means you reach a different professional audience without extra work. The landing redesign and trust copy make it clearer what’s public and what stays on GitHub, which helps people feel comfortable enabling integrations. Rate limiting and the fail-open behavior protect the public API while avoiding outages that would interrupt your audience.

What's next

Next I’ll finish making preview deploys safe again and re-enable controlled git-triggered deploys, and I’ll polish the onboarding flow for first-time posters. Follow the build log if you want the next updates as they land.