←back to thread

Et Tu, Grammarly?

(dbushell.com)
279 points dbushell | 1 comments | 29 Mar 25 10:27 UTC | HN request time: 0.202s | source
Show context
dbushell ◴[29 Mar 25 10:27 UTC] No.43514309[source]▶
How do you deal with hostile browser extensions?
replies(5): >>43514670 #>>43515016 #>>43515058 #>>43516270 #>>43516486 #
WJW ◴[29 Mar 25 11:36 UTC] No.43514670[source]▶
Uninstall them?
replies(1): >>43514789 #
dbushell ◴[29 Mar 25 11:55 UTC] No.43514789[source]▶
If only I could opt-out, disable, or uninstall those used by visitors to my website when the extension breaks it :(
replies(1): >>43515010 #
diggan ◴[29 Mar 25 12:30 UTC] No.43515010[source]▶
Not much you can do, user agents continue to act as agents for the users, meaning you can serve them stuff but beyond that it's up to them to dictate their experience, for better or worse.

It really sucks when extensions do fudgy stuff in global space and sometimes break your stuff though, agree. Best approach I've found is to have a help page you can link to so people can go through the typical steps of "disabling all extensions, clearing cache, etc, etc" when things break in very unexpected way and you find no causes for it.

replies(1): >>43515107 #
dbushell ◴[29 Mar 25 12:45 UTC] No.43515107[source]▶
Indeed. It's the user's browser and experience, it's not up to the website owner. But it's frustrating to get bug reports when a 3rd party extension is the problem, not the website. Many visitors will just bounce blaming the website too.
replies(1): >>43515786 #
1. ziml77 ◴[29 Mar 25 14:21 UTC] No.43515786[source]▶
Without someone pointing the user to what the issue is, it's very difficult for the user to know it's an extension causing the problem.

Many years ago I had performance issues with a site and the only reason I knew it was due to an extension is I dug into it with the dev tools and managed to identify Dashlane as the problem.