Google Ads reinstates RACE after false-positive ban
Developer Przemysław Alexander Kamiński created RACE, an infinite-canvas native macOS terminal multiplexer written in Rust, and launched a $500 Google Ads campaign to promote it. Shortly after launching, Google Ads suspended the account citing "Malicious software" and "Compromised Site," despite the notarized macOS binary, static Bridgetown landing page, and R2 download infrastructure passing Google Safe Browsing, Google Search Console, and VirusTotal checks without issue. After facing multiple automated appeal rejections with zero actionable feedback, the developer published an account of the ordeal and potential false positives stemming from background PTY process persistence, leading to account reinstatement only after the post reached the top of Hacker News.
Automated platform moderation creates a Kafkaesque trap for independent developers, where public outrage on social media remains the only viable customer support channel against opaque algorithmic bans.
- –Brittle malware heuristics: Legitimate developer utility behaviors—like a terminal multiplexer launching and detaching background PTY processes—routinely trip blunt behavioral heuristics searching for malware persistence.
- –The opacity trap: Google's automated appeal process demanded fresh evidence while refusing to disclose the flagged payload, URL, or behavior, forcing the developer into blind troubleshooting.
- –Support through virality: Frontline developer support across dominant ad and app ecosystems continues to fail until public attention threatens brand reputation enough to trigger human intervention.
DISCOVERED
1h ago
2026-09-09
PUBLISHED
5h ago
2026-09-09
RELEVANCE
AUTHOR
xlii