Search Engines on FreeBSD's Chromium

DuckDuckGo and Ecosia are standard search engine options on Google's Chrome, but FreeBSD's Chromium only supports Google, Bing and Yahoo.

There doesn't seem to be any way to add additional, general purpose engines, and editing the name+URL for one of the three doesn't work.

I'm wondering if this is a port configuration problem. grepping the source code finds many apparently relevant hits, e.g.:

From components/search_engines/prepopulated_engines.json
Code:
   "duckduckgo": {
      "name": "DuckDuckGo",
      "keyword": "duckduckgo.com",
      "favicon_url": "https://duckduckgo.com/favicon.ico",
      "search_url": "https://duckduckgo.com/?q={searchTerms}",
      "suggest_url": "https://duckduckgo.com/ac/?q={searchTerms}&type=list",
      "new_tab_url": "https://duckduckgo.com/chrome_newtab",
      "type": "SEARCH_ENGINE_DUCKDUCKGO",
      "id": 92
    },

    "ecosia": {
      "name": "Ecosia",
      "keyword": "ecosia.org",
      "favicon_url": "https://cdn.ecosia.org/assets/images/ico/favicon.ico",
      "search_url": "https://www.ecosia.org/search?q={searchTerms}&addon=opensearch",
      "suggest_url": "https://ac.ecosia.org/autocomplete?q={searchTerms}&type=list",
      "new_tab_url": "https://www.ecosia.org/newtab/",
      "type": "SEARCH_ENGINE_ECOSIA",
      "id": 101
    },
 
doesn't the "add" button next to "site search" in preferences work for you?
(yes, it isn't the most logical UX decision I have seen)
 
That does work to an extent, but doesn't make it a "first-class" search engine the way that the big three are. If you look in the code block there are other settings beside "search_url" - most notably "suggest_url".

I don't hugely care about working around this myself. Google started giving me captchas due to the reputation of my VPN shared IP address, so I had to change and I noticed something that could probably be improved.
 
Back
Top