This week: LinkedIn cross-posting, stronger safety pages, and rate limits that fail safe

This week I shipped LinkedIn cross-posting and a bunch of safety and stability work. You can now opt in to have your commit cards posted to LinkedIn, and the site is safer and more reliable for public use.

What shipped

• –LinkedIn cross-posting: OAuth connect, a token store, a settings toggle, and a background hook so posts go out without blocking your workflow
• –Per-IP rate limiting for public endpoints so abusive traffic is tamed before it affects others
• –Fail-open behavior on rate limiter DB errors so a hiccup never turns into a hard 500 for visitors
• –Analytics changes: added Google Analytics 4 (dormant until you set an env var) and replaced PostHog with Microsoft Clarity for session replay and heatmaps
• –Security and privacy features: commit content is read via numeric GraphQL summaries and commit stats only — code diffs never leave GitHub
• –Public safety and trust content: a clear /security page, bold landing safety points, better FAQ, and use of a support email instead of a personal address
• –Open-source prep: AGPL-3.0 license, public README, self-host guide, SECURITY and CONTRIBUTING files, and a .env.example to help anyone self-host
• –Usability tweaks: fixed onboarding copy, made "Post my first card now" a top CTA, and added subtle trust indicators near the main action
• –Developer ops: disabled automatic preview deploys that fail without production env, and published a small MCP stdio server package for CLI-first flows

Why this matters

If you use git-to-x to share daily progress, these changes make that sharing more reliable, safer for your readers, and broader in reach. LinkedIn cross-posting gets your work in front of more professional audiences without extra steps. Rate limits and fail-open behavior keep the public service running even when parts of the infrastructure hiccup. The privacy choices mean your code diffs never pass through our servers, which is important if you work on private or sensitive projects.

What's next

Next I’ll expand the LinkedIn post templates so cross-posts look great by default and add controls for which commits should cross-post. Follow the build log to see those refinements land next week.