I’ve recently learned that DDG does not follow its own guidelines for privacy. I’m curious what search engines people here would recommend. I would prefer a search engine that not only respects my privacy but also doesn’t hide or shadow ban content it doesn’t like. Any recommendations?
I recommend finding a different instance then. Not every instance is going to be great at it, and you do have to do a lot of fiddling around with preferences and be-bopping between various instances when the current instance is timing out.
…Or you could just hit F5 and try your search query again. For some reason that seems to work sometimes. It is possible to configure an instance to not get slammed; and you can host one yourself too
The problem is that it doesn’t matter which instance I use. I tried multiple instances, even self-hosted one myself. Sooner or later I always had the problem with timeouts (even with my self-hosted local instance) and it’s so damn annoying. Even refreshing the page doesn’t always help. I really don’t feel like hopping from instance to instance just because my preferred instance has timeouts again. Reliability is crucial to me.
Did you check the preferences on the instance and change the default engine selections? You can check the engines and de-select engines that are turning out to be unreliable with results; which should result in fewer errors.
Of course I did. The thing is that the reliability of the search engines per instance varies from time to time so there’s not a single instance that will always work perfectly and never has timeouts.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
I recommend finding a different instance then. Not every instance is going to be great at it, and you do have to do a lot of fiddling around with preferences and be-bopping between various instances when the current instance is timing out.
…Or you could just hit F5 and try your search query again. For some reason that seems to work sometimes. It is possible to configure an instance to not get slammed; and you can host one yourself too
The problem is that it doesn’t matter which instance I use. I tried multiple instances, even self-hosted one myself. Sooner or later I always had the problem with timeouts (even with my self-hosted local instance) and it’s so damn annoying. Even refreshing the page doesn’t always help. I really don’t feel like hopping from instance to instance just because my preferred instance has timeouts again. Reliability is crucial to me.
Did you check the preferences on the instance and change the default engine selections? You can check the engines and de-select engines that are turning out to be unreliable with results; which should result in fewer errors.
Of course I did. The thing is that the reliability of the search engines per instance varies from time to time so there’s not a single instance that will always work perfectly and never has timeouts.