The situation with Facepunch implementing automated AI voice moderation in Rust is raising serious questions about data privacy and account security. Jake_Rich's branch "hackweek_voice_moderation" is merged into the main repository, and community votes show an overwhelming negative response. Check the public commits here:https://commits.facepunch.com/Jake_Rich/rust_reboot/main/hackweek_voice_moderation* #151302 (93 Likes / 571 Dislikes) — Records in-game audio via PTT, batches clips up to 60s, sends data to third-party AI API.* #151406 (5 Likes / 71 Dislikes) — Moved from temporary Hack Week files into main repository branch (rust_reboot).* #151484 (3 Likes / 76 Dislikes) — Implements startup mute checks and processes API response tokens to handle muting.* #151493 (3 Likes / 67 Dislikes) — Moves API mute verification above IsAdmin check for editor testing.* #151495 (3 Likes / 71 Dislikes) — Displays permanent mic icon with an 'X' during automated API mute.* #151496 (1 Like / 75 Dislikes) — Fixes voice stream cutoff exceptions when players spam the PTT system.This means a paid game will actively capture microphone packets, archiving unique biometric voice files on external servers to train automated censor bots. If the algorithm misinterprets background noise, hardware static, or local non-native slang as a violation, a Steam account with thousands of hours of progress faces a potential permanent ban. This corporate slop is dragging the entire gaming industry toward endless censorship. Instead of a raw, unpredictable experience, games are being turned into a completely sterilized sandbox. When this feature officially moves to the public Staging branch, what is the most logical approach for the community? Will players shift to third-party communication tools like Discord to avoid empty AI server polling, or focus on feedback regarding data privacy laws? Post your thoughts.
15 years ago this would have been considered wiretapping and have federal charges. Zoomers have no idea how bad things are.
