Not by an order of magnitude, esp, for chat applications that are limited by http application protocols.
> ..that detects attempts to automate the browser.
Nobody sends spam from the gmail web browser client, but suppose google successfully bans (somehow?) all other email clients, the enterprising spam sending people would still easily automate the browser, esp. with things like autohotkeys (which doesn't require modifying the browser itself, nor run code in the browser).
The point is, banning a client side mod for any service is irrational if the justification is to prevent spammers.
"the enterprising spam sending people would still easily automate the browser, esp. with things like autohotkeys"
It's not at all easy for them, and people who try approaches as simple as that don't make any money. Or didn't when I worked on it at least.
"The point is, banning a client side mod for any service is irrational if the justification is to prevent spammers."
That belief is widespread, but I built a part of my career on proving it wrong. We got unexpectedly excellent results from cracking down on alternative clients that were pretending to be browsers.
Gmail actually does rely on various forms of "anti cheat" to control spam, including obfuscated code that detects attempts to automate the browser. That doesn't help for inbound mail but it helps a lot to stop people sending spam from Gmail.