https://github.com/notriddle/discourse-duckduckgo-search
Solves Is there a way to suggest DuckDuckGo instead of Google for failed search UI?.
A Discourse theme component to use DuckDuckGo as the suggested search system, instead of Google!
p.s. You’ll probably want to customize some of the text strings to stop mentioning Google, too.
Here’s what I’ve noted to be the places to alter the text:
Is that it?
Okay, I’m writing this down, because 404 handling in Discourse is weird. Try this link on for size:
https://meta.discourse.org/nonexistant-page
If you open it in a new tab, you’ll notice that your user menu (the one in the upper-right of the page) doesn’t render. In fact, the Discourse Ember app doesn’t get loaded at all in this case. It’s being rendered by the Rails server following app/views/exceptions/not_found.html.erb
Obviously, if you click the link directly in this page, the Ember app remains resident. Try hitting the link with a .json at the end, and instead of sending the app a full 404 page, it sends an HTML fragment, with the heading and stuff removed, which the Ember app just plops into place.
Oh weird. But if that’s less trivial to fix, at least it can be documented and the easier parts all fixed. Thanks for working on this!
Added a commit to do the form rewriting to make the 404 page work, both within and without the Ember app.
Great! So the only remaining thing is to document (probably both here and at the repo README) the confirmed list of text items theme-users will need to customize in the admin UI?
I got this working, but it’s a little strange to have the page-not-found version start with the form using site:xxx… with no search term alongside that. Maybe that’s as good as it gets, but it would be ideal if it were feasible to get the text of the URL after the TLD for the not-found page and use that as the default search before the site: part…
Given
Google is no longer used at 404 pages. So, this theme probably needs updating to leave 404 pages alone, let them be the regular internal search as is now standard.
Discourse is still using Google for extra searching when internal searches fail though. So, for that, this DDG option still applies.
It wasn’t actually breaking anything, but I did go ahead and revert it. It also made the code simpler, since I can just replace the template again.
is there any reason Google is still the default for Discourse when extra searching occurs? DuckDuckGo is more in tune with the mindset of Discourse than Google is.
Sono d’accordo, c’è una soluzione temporanea?
Potrebbe essere utilizzato anche con Discourse AI 
Questo componente del tema è la soluzione temporanea.
Non avevo visto questo argomento e non ero a conoscenza del componente del tema, quindi mi sono sbarazzato completamente della cosa della ricerca di Google… Sono riluttante ad aggiungere un altro componente del tema non ufficiale ora, però. Sarebbe bello se quello predefinito fosse DuckDuckGo o se ci fosse un’impostazione del sito.
…che consentisse di modificare il provider o di rimuovere del tutto questo suggerimento di ricerca di fallback.
Nel frattempo, come hai fatto a “rimuovere completamente la cosa della ricerca”? Presumibilmente, hai creato un componente tematico, ma puoi condividere qui il codice effettivo (in modo da non doverlo scoprire da solo)?
L’ho forkato e ho cambiato l’URL. Lo standard generale dovrebbe essere lasciarlo vuoto e consentire all’utente di modificarlo.
È così che funziona profondamente il marketing, attraverso l’ingegneria sociale ai massimi livelli.
Ho effettuato un push di un aggiornamento per utilizzare un plugin outlet, ma questo richiede l’aggiunta dell’outlet a Discourse stesso.