[Tyriar]

> This one literally changes just one setting and you get the same results if you do it manually

I just checked and this isn't actually true though, it looks like it also installs a service worker that runs some code in background.js. It sucks I needed to look at the extension's contents to verify that and backs up why I wouldn't want to install it in the first place.

My proposal seems win-win, you can even push the extension hard in the search page if it's not installed due to your concern, provided you allow it to be easily and permanently dismissed.

[bryanmccann]

Hi Tyriar,

Just wanted to provide some more info on the background service worker, though if you've pulled the code you've probably already seen the same.

Right now that worker does two things. It redirects to a survey if you uninstall the extension (going away in the next update once it makes it through the webstore review), and it allows detection of the installed extension since its required in Chrome unless you search from the url/navbar.

And just so there's full details on the restriction here too:

We determine if the search is from the url/navbar only through that fromSearchBar query parameter, so either manually entering the url without that query param, following links without that query param, or by setting your default in your settings manually and searching from the url/navbar will all work. It is just that search bar on the page that gets disabled without the extension. There's also no restriction right now on non-Chrome browsers or in a Chrome Incognito Window.

Thanks for digging in, bringing that up for clarification, and for your proposal!

[hulahoof]

I hope your team is aware how underhanded your approach and responses seem; why not just be honest off the bat?

When I saw this pop up I went and had a go, even created an account. Then I read through the correspondence here and I won't ever be browsing to you.com again.