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.
Doy mi apoyo, ¿hay alguna solución temporal?
También podría usarse con Discourse AI 
Este componente temático es la solución alternativa.
No había visto este tema y no sabía lo del componente de tema, así que me deshice por completo de lo de la búsqueda de Google… Sin embargo, ahora soy reacio a añadir otro componente de tema no oficial. Sería bueno si el predeterminado fuera DuckDuckGo o si hubiera una configuración del sitio.
…que permitiera cambiar el proveedor, o eliminar por completo esta sugerencia de búsqueda de respaldo.
Mientras tanto, ¿cómo “eliminaste por completo la cosa de la búsqueda”? Presumiblemente, creaste un componente temático, pero ¿puedes compartir el código real aquí (para no tener que averiguarlo yo mismo)?
Lo he bifurcado y he cambiado la URL. El estándar general debería ser dejarlo vacío y permitir que el usuario lo cambie.
Así es como funciona profundamente el marketing, a través de la ingeniería social en sus niveles más finos.
He publicado una actualización para usar un plugin outlet, pero esto requiere que el outlet se agregue a Discourse en sí.