Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add search engine comparison table #2505

Merged
merged 1 commit into from Apr 11, 2024

Conversation

redoomed1
Copy link
Contributor

@redoomed1 redoomed1 commented Apr 9, 2024

Changes proposed in this PR:

As marked on GitHub, this is a draft PR as wording and formatting is not set in stone. I'm unsure of what to rearrange, add, or remove, so any feedback is welcome. Here are some questions as a starting point:
- Logging: Is it better to list information that is logged in the table, and list what isn't logged in the description under each card; or, as in the DNS comparison table, just link to a footnote explaining the logging policies?
- Countries of operation: List it in a column, or include it in the descriptions of each recommendation? (The latter is done for the VPN recommendations.)
- Metasearch engines: Being that SearXNG is not like the other providers on this page, does it necessitate a new "Metasearch engines" heading; or should it still be included in the table?

  • I have disclosed any relevant conflicts of interest in my post.
  • I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project.
  • I am the sole author of this work.
  • I agree to the Community Code of Conduct.

Copy link

github-actions bot commented Apr 9, 2024

Your preview is ready!

Name Link
🔨 Latest commit 93136f2
😎 Preview https://2505--glowing-salamander-8d7127.netlify.app/

docs/search-engines.md Outdated Show resolved Hide resolved
docs/search-engines.md Outdated Show resolved Hide resolved
@redoomed1
Copy link
Contributor Author

redoomed1 commented Apr 10, 2024

Changes made since the initial commit:

  • Removed "Country of Operation" column from the table and incorporated the information into the descriptions of each recommendation
  • United the "Logging" and "Privacy Policy" columns to one (idea from Add logging information to DNS criteria #2509)
  • Added footnotes to each entry in the "Logging / Privacy Policy" column, using the DNS Resolvers page as a reference

@redoomed1
Copy link
Contributor Author

redoomed1 commented Apr 10, 2024

Changes made before marking PR as ready for review:

  • Re-added "Country of Operations" column to the table since it looked sparse with just four columns
  • Abbreviated "personally identifying information" in accordance with the style guide
  • Added internal links for Tor Browser and Safari in the DuckDuckGo card
  • Added a link to Wikipedia page about metasearch engines
  • Added a link to documentation explaining Brave Search's Discussions feature
  • Added link to documentation on Brave's Anonymous local results to contextualize IP address processing by Brave Search
  • Changed wording in several places

@redoomed1 redoomed1 marked this pull request as ready for review April 10, 2024 17:13
@dngray dngray added the c:providers service providers and similar centralized/federated services label Apr 10, 2024
Signed-off-by: Jonah Aragon <jonah@triplebit.net>
@jonaharagon jonaharagon merged commit 93136f2 into privacyguides:main Apr 11, 2024
11 checks passed
@privacyguides-bot
Copy link
Collaborator

This pull request has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/2024-04-11/17822/1

@redoomed1 redoomed1 deleted the search-engine-table branch April 11, 2024 23:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:providers service providers and similar centralized/federated services
Development

Successfully merging this pull request may close these issues.

None yet

4 participants