-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the extensions description #405
Comments
seconded. the website singles out google too. i constantly recommend this extension and its pretty annoying having to clarify "supports much more than google" |
This issue is stale because it has been open for 30 days with no activity. |
no activite doesn't mean its resolved at all |
This issue is stale because it has been open for 30 days with no activity. |
No. |
i urge you to reconsider using a stale bot: all it causes is issues to be forgotten |
Hey there! I think that having "Google" in the lead description might have been a good thing for the extension's visibility, since I'm pretty sure that most people use google as their main search engine. Now granted, I have absolutely no data on this, this is just something that I've been thinking lately. Now, if we were to change this, what about... Blocks specific sites from appearing in Google search results and other search engines. Maybe even something like: Blocks specific sites from appearing in Google search results and other search engines, like Bing, DuckDuckGo, etc Although, this last one seems a little too big for me.. |
What about
or maybe
one part of this is also making the extensions website and docs a bit more clear on it supporting multiple engines, so that its nicer when linking it to others directly |
I really like this one.
I'd be willing to help with this too. |
Change it from:
Blocks specific sites from appearing in Google search results
To:
Blocks specific sites from appearing in results of search engines
Why?
Since it's kinda missleading and people will think it only works for Google
The text was updated successfully, but these errors were encountered: