1. Watermarking reshapes token choice – often at the cost of “best‑word” quality
“The exact words we choose when writing matter.” –andy99
“The quality of the system is in the quality of the probabilities. That quality is being degraded.” –beering
2. EU regulation drives mandatory watermarking and provenance claims
“The provider must mandate in their terms‑of‑service that users not remove the watermarking.” –krackers
“You know you can just ignore EU laws outside of the EU.” –inigyou
3. Detectability and interoperability are shaky – secrecy fuels distrust
“If a watermark is not self‑evident, or universally detectable, then it is no good.” –ButlerianJihad
“Providers must implement an interoperability solution … by February 2, 2027.” –troupo
4. Ownership, copyright and reuse become murky
“So, you don't own the generated text, and can't use it freely then.” –krackers
“If it is possible to confirm 100 % confidence that a chunk of text is LLM output, then it is ‘PD until proven otherwise’.” –ButlerianJihad
5. Users fear real‑world impact on editing, privacy and model choice
“I moved to Sol for my writing … it makes more mistakes.” –kalleboo
“This could be why claude code has recently started to write reams of inane comments alongside the code it generates.” –Cakez0r
Short take: The debate centers on whether watermarking merely adds a detectable signal (often by biasing token selection) or truly degrades language quality, how EU rules force compliance and shared detection standards, and what that means for authorship, copyright, and everyday users who rely on LLMs for editing and code‑generation.