Added/fixed search engine icons and added support for search suggestions #101

ekhh commented 2026年01月02日 06:21:27 +01:00

Until LW ships its own search-config-v2.json, this is a QoL change for search engines:

• DuckDuckGo Lite used a slightly different (and blurry) icon compared to the one used by ddg@search.mozilla.org in tippytop, which had caused inconsistency in UI. I fetched browser/components/topsites/content/tippytop/favicons/duckduckgo-com.ico and encoded it as the icon for DuckDuckGo Lite.
• DuckDuckGo Lite, SearXNG, and MetaGer did not show search suggestions even when browser.search.suggest.enabled is set to true. This should fix that. Closes librewolf/issues#2424.
• The p in Startpage should not be capitalized.
• The Startpage icon was slightly bent (and I was slightly bothered). Now it is no longer.
• Use a transparent icon for Mojeek.
• Use the official icon for MetaGer.
• Added icon for SearXNG.

Note:

• I have ensured that each engine is shipped with a single .ico file containing two resolutions, as suggested here.
• Command for converting icons into the correct format (with two sizes): magick input.png -define icon:auto-resize=16,32 -compress zip output.ico. I used GIMP to compress them further.
• SuggestURLTemplate for MetaGer was extracted from the firefoxextension@metager.de extension.
• Description for search engines were derived from the first sentence of <meta name="description"> (aside from DuckDuckGo Lite, which does not have the tag).
• Mojeek does not provide search suggestions.

Until LW ships its own search-config-v2.json, this is a QoL change for search engines: - DuckDuckGo Lite used a slightly different (and blurry) icon compared to the one used by ddg@search.mozilla.org in tippytop, which had caused inconsistency in UI. I fetched browser/components/topsites/content/tippytop/favicons/duckduckgo-com.ico and encoded it as the icon for DuckDuckGo Lite. - DuckDuckGo Lite, SearXNG, and MetaGer did not show search suggestions even when browser.search.suggest.enabled is set to true. This should fix that. Closes librewolf/issues#2424. - The `p` in Startpage should not be capitalized. - The Startpage icon was slightly bent (and I was slightly bothered). Now it is no longer. - Use a transparent icon for Mojeek. - Use the official icon for MetaGer. - Added icon for SearXNG. **Note:** - I have ensured that each engine is shipped with a single .ico file containing two resolutions, as suggested [here](https://github.com/mozilla-firefox/firefox/blob/6a0626aaa09a87200258dbf6161fde44722c763e/browser/components/search/docs/application-search-engines.rst#icon-requirements). - Command for converting icons into the correct format (with two sizes): `magick input.png -define icon:auto-resize=16,32 -compress zip output.ico`. I used GIMP to compress them further. - SuggestURLTemplate for MetaGer was extracted from the firefoxextension@metager.de extension. - Description for search engines were derived from the first sentence of `<meta name="description">` (aside from DuckDuckGo Lite, which does not have the tag). - Mojeek does not provide search suggestions.

alyx161 commented 2026年01月02日 10:17:27 +01:00

I don't think its a good idea to pick just any random SearXNG instance.
That is kinda the reason why the issue was still open. If we want to include one in LW it should be an instance that is reliable, trustworthy and functional.
searx.be was matching this pretty easily since it was run by one of the core maintainers.

Public Sear instances currently struggle a lot. Many of the important search backends are either complete dysfunctional (Google, Bing) or so hard rate limited that they are extremely unreliable (Brave, Startpage) since many SearXNG instances facing a lot of (SEO?) bots, triggering those rate limits.

The paulgo.io for example is using Google and Bing by default, both broken backends, and therefore its returning just garbage.

image

Because of this, I would recommend postponing changes to the included Sear instance, until they pushed the necessary updates, and we can make a decision which instance to include.

I don't think its a good idea to pick just any random SearXNG instance. That is kinda the reason why the issue was still open. If we want to include one in LW it should be an instance that is reliable, trustworthy and functional. searx.be was matching this pretty easily since it was run by one of the core maintainers. Public Sear instances currently struggle a lot. Many of the important search backends are either complete dysfunctional (Google, Bing) or so hard rate limited that they are extremely unreliable (Brave, Startpage) since many SearXNG instances facing a lot of (SEO?) bots, triggering those rate limits. The paulgo.io for example is using Google and Bing by default, both broken backends, and therefore its returning just garbage.  Because of this, I would recommend postponing changes to the included Sear instance, until they pushed the necessary updates, and we can make a decision which instance to include.

ekhh commented 2026年01月03日 00:37:22 +01:00

@alyx161 wrote in #101 (comment):

I don't think its a good idea to pick just any random SearXNG instance. That is kinda the reason why the issue was still open. If we want to include one in LW it should be an instance that is reliable, trustworthy and functional. searx.be was matching this pretty easily since it was run by one of the core maintainers.

Noted. I have changed it back for now. Hopefully someone more knowledgeable on the matter will be able to pick a better instance.

@alyx161 wrote in https://codeberg.org/librewolf/settings/pulls/101#issuecomment-9468728: > I don't think its a good idea to pick just any random SearXNG instance. That is kinda the reason why the issue was still open. If we want to include one in LW it should be an instance that is reliable, trustworthy and functional. searx.be was matching this pretty easily since it was run by one of the core maintainers. Noted. I have changed it back for now. Hopefully someone more knowledgeable on the matter will be able to pick a better instance.