That’s a fair question, and for some cases a pseudonym + throwaway email can be enough. The main difference is that git config only affects a small part of the

That’s a fair question, and for some cases a pseudonym + throwaway email can be enough. The main difference is that git config only affects a small part of the metadata. Even with a pseudonym, GitHub still receives and exposes: - Commit timestamps and timezone - Correlation across repos and long-term activity - Client and workflow patterns - A persistent GitHub account (even if “throwaway”) gitGost operates server-side and normalizes everything before GitHub ever sees it. Commits are re-authored with sanitized metadata and PRs are opened from a neutral bot account, so there’s no persistent identity to correlate over time. The goal isn’t just pseudonymity, but reducing long-term traceability and cross-repo linkage, especially for people contributing in sensitive or hostile contexts. That said, if someone is comfortable with a pseudonym and doesn’t need stronger anonymity guarantees, local git config is simpler. gitGost is meant for the cases where that’s not enough. Appreciate the question.