<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Search engines should be configurable]]></title><description><![CDATA[<p dir="auto">Let's first clarify what is the current state:</p>
<ul>
<li>the default search engines are configured in <code>default_partner_content.json</code> for each country</li>
<li>the shortcut for the default search engines is configured in <code>default_partner_content.json</code></li>
<li>you cannot change the shortcut of default search engines</li>
<li>you cannot have the same shortcut twice (what is reasonable)</li>
<li>you cannot choose a custom search engine to be the default search engine</li>
<li>the search popup always uses google (at least in my country: DE)</li>
</ul>
<ol>
<li>To make it usable the shortcut has to be configurable. For example <code>y</code> is configured to be Yahoo in Germany. Sorry: I don't know anyone in Germany using Yahoo at all. And I'm used to have youtube on <code>y</code>.</li>
<li>Unless you are paid by the partners it should be possible to choose another search engine as default search engine.  Nobody expects that you add all known search engines to <code>default_partner_content.json</code> but also you should not expect to fulfill everyones needs.</li>
<li>It should be possible to select the default search engines. Make it transparent that choosing a location (I can't remember to choose one) defines your search engines. A Russian  living in Germany might wan't to have <code>wikipedia_ru</code> instead of <code>wikipedia_de</code>. Better it would be to add and remove "default search engines" (I don't know the namings in English opera) from your predefined list.</li>
<li>Last but not least: why is the search popup (alt+space) not using the default search engine? It sounds obvious that this is using the default search engine.</li>
</ol>
<p dir="auto">I don't know why all this is fixed but I assume it is for security reasons. This is not the way to solve security issues. When you are afraid that a client software changes something and harms the user you could ask the user if the value changes to confirm it with some captcha or password (just to ensure it was not a malware). Instead you are forcing the user to use your configuration.</p>
<p dir="auto">Please take this serious - I want to use Opera. It's a great browser!</p>
]]></description><link>https://forums.opera.com/topic/32287/search-engines-should-be-configurable</link><generator>RSS for Node</generator><lastBuildDate>Sun, 12 Jul 2026 10:21:38 GMT</lastBuildDate><atom:link href="https://forums.opera.com/topic/32287.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 06 May 2019 06:02:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Search engines should be configurable on Wed, 08 May 2019 16:19:31 GMT]]></title><description><![CDATA[<p dir="auto">I understand this, just wanted to say that it something is encrypted there should be a key. If key is stored locally malware can read it and do whatever it needs.</p>
<p dir="auto">Anyway I am not sure if developers read this forum. Opera can't change default search engines, can't hibernate tabs after eliminating extended-lazy-session-loading flag (I am aware of "Tab Suspender (memory saver)" extension, but it has major drawback causing lost tabs), can't show sidebar only for speed dial. 2 of 3 issues raised after update.</p>
]]></description><link>https://forums.opera.com/post/170176</link><guid isPermaLink="true">https://forums.opera.com/post/170176</guid><dc:creator><![CDATA[[[global:former_user]]]]></dc:creator><pubDate>Wed, 08 May 2019 16:19:31 GMT</pubDate></item><item><title><![CDATA[Reply to Search engines should be configurable on Wed, 08 May 2019 04:33:25 GMT]]></title><description><![CDATA[<p dir="auto">@opera-user-from-2002 I mean that it could be necessary for security reasons to store some configurations encrypted. I'm not a master of encryption but there should be a solution that finds out manipulations to the configuration and either resets the configuration to the last version the user solved a security question or asks the user to confirm these changes. In the configuration page it could also ask these configuration before setting the default search engine to a custom search engine.</p>
]]></description><link>https://forums.opera.com/post/170137</link><guid isPermaLink="true">https://forums.opera.com/post/170137</guid><dc:creator><![CDATA[IrascibleMan]]></dc:creator><pubDate>Wed, 08 May 2019 04:33:25 GMT</pubDate></item><item><title><![CDATA[Reply to Search engines should be configurable on Tue, 07 May 2019 04:40:45 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forums.opera.com/uid/217289">@IrascibleMan</a> Thank you for the suggestion, I also would like to see it implemented. Btw, how would you implement the following: "ask the user if the value changes to confirm it with some captcha or password"? How we can prevent malware from modifying option where the flag "default search engine has been changed" is stored?</p>
]]></description><link>https://forums.opera.com/post/170067</link><guid isPermaLink="true">https://forums.opera.com/post/170067</guid><dc:creator><![CDATA[[[global:former_user]]]]></dc:creator><pubDate>Tue, 07 May 2019 04:40:45 GMT</pubDate></item></channel></rss>