https://searx.com/ (if I got the URL correctly) requires JavaScript.
Unlike Google, https://startpage.com/es/q=<search string> (secured HTTP
mandatory) doesn't accept Umlauts in strings. Translations are unavailable,
such as http://google.com/search?q=on+a+particular+base+translate+Ge... did.
(Pure translation services require JS for results to be rendered, altogether.)
Third, StartPage's result pages are ten times bigger than Google's were.
Viktor Lofgren's https://old-search.marginalia.nu/search?query=<string>
searches in a traditional manner. An interesting concept. It's output is much
different to what I was used from answers to natural language queries, however.
The interface of Will's https://4get.ca/ is as slim as Google's, but replies
to (mandatory) Captchas require JavaScript. In ten days since Google blocked
searches, I haven't found an appropriate alternative. Torsten
When resources are an issue, this does matter.
I use to store previous Lynx/ Links search results in history lists,
to allow browsing within local files later. Creating such lists with
Firefox is a mess. (This browser tends to block my Thinpad for hours.)
Really sad. Google was a key to the internet.
Torsten
