You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can imagine times when this plugin basically duplicates what the user could have gotten by calling a different, service-specific, command. A big example is bots that run both this and the youtube plugin, where users might be annoyed at getting a youtube.com result when they specifically did not use the .yt command because they don't want a video.
It might be useful if this plugin allowed configuring a default list of domains to be treated as -site:$domain. How practical is this idea? I'm not sure. Is there a limit on the number of site: operators in DDG? Could the plugin request a full page of results instead of just one, and do its own filtering?
These questions and more to be considered if (and only if) such a feature is deemed useful enough to implement.
The text was updated successfully, but these errors were encountered:
I can imagine times when this plugin basically duplicates what the user could have gotten by calling a different, service-specific, command. A big example is bots that run both this and the
youtube
plugin, where users might be annoyed at getting a youtube.com result when they specifically did not use the.yt
command because they don't want a video.It might be useful if this plugin allowed configuring a default list of domains to be treated as
-site:$domain
. How practical is this idea? I'm not sure. Is there a limit on the number ofsite:
operators in DDG? Could the plugin request a full page of results instead of just one, and do its own filtering?These questions and more to be considered if (and only if) such a feature is deemed useful enough to implement.
The text was updated successfully, but these errors were encountered: