LinkedIn cross-posting, safer public endpoints, and clearer trust signals

This week I shipped LinkedIn cross-posting, tightened public rate limits, and polished safety documentation. You can now connect LinkedIn, control when posts go out, and rest easier knowing public endpoints are resilient and our security promises are explicit.

What shipped

• –LinkedIn cross-posting: OAuth connect, token storage, a settings toggle, and a background hook that sends posts when enabled.
• –Per-IP rate limiting on public, unauthenticated endpoints so one noisy client can’t drown the service.
• –Fail-open behavior for the limiter: if the database has an error, the public endpoints keep responding instead of returning 500s.
• –Analytics updates: Google Analytics is added but dormant until you set an ID, and Microsoft Clarity replaces the previous product for session replay and heatmaps.
• –Trust and security work: a clear security page that lists exactly what metadata we collect, a stronger FAQ, a support email (not a personal one), and UI trust cues near the call-to-action.
• –Open-source prep: AGPL-3.0 license, public README, self-host guide, SECURITY and CONTRIBUTING files, and a published .env.example for self-hosters.
• –Privacy-preserving commit handling: we read commit IDs and stats via GraphQL so raw code diffs never leave your Git host.

Why this matters for solo makers

If you use git-to-x to share daily progress, LinkedIn is now a first-class channel. You can opt in per account and keep templates separate from other automations. The rate limits and fail-open behavior mean the public endpoints are more reliable for visitors and integrations. The security page and trust pills make it easier to explain to teammates, users, or early customers what data we see and what never leaves your repo. Finally, the open-source and self-hosting materials let you run this yourself if you prefer.

What's next

I’ll monitor LinkedIn posting for edge cases and tighten error handling in the background worker. Follow the build log to see reply threading and richer card previews land next.