Today's act of kindness: I helped two victims of surveillance (mainstream users) with some basic privacy:
Google search > DuckDuckGo
Chrome > Firefox + uBlock Origin
Gmail > @Tutanota
Minimize number of apps
Simple actions that cuts a big chunk of surveillance. As usual they were surprised how it works.
@Tutanota @jonas @Tutanota #Duckduckgo is a terrible recommendation. see https://dev.lemmy.ml/post/29179
Privacy is almost always relative to the threat model of the individual.
Searxes often get blocked or simply don't return anything due to bad configuration.
Despite that I prefer them and recomended it to all my tech friends.
However it's simply a poor choice for an average person that preffers stuff like search bubbles and targeted ads
No, I'm afraid I wasn't confusing a tree for the forest.
However can you expand on your Searxes avoids that problem comment?
Are you talking about constant public instance switching, self-hosting, meta-searxes or something else entierly?
@jonas
@wuwei @jonas Searxes is coded to randomly select from a pool of quality searx instances on each query. It then does some post-processing to filter #CloudFlare results. Searxes never says "due to #CAPTCHA there are no results". IDK how it avoids that. Either the source pool is only instances that don't scrape or it jumps to another instance in the background.
@wuwei @jonas Like #DDG, all searx instances are inherently meta-search engines. Searxes is a meta-search of searx instances, which you could call a meta-meta-search. Meta-searching does not necessarily imply scraping. A meta-search can be accomplished by scraping &/or using an API. The searx s/w is #freesoftware not designed for corporate protectionism. It's unlikely that Searxes scrapes.
@jonas @wuwei many searx nodes scrape b/c they tend to be non-profit projects. But Searxes most likely uses an open API to get results from searx nodes.