Leaked Lies at Google
Google accidentally leaked their search API on Github, giving everyone insight into that they:
--Lied that they track users clicks as a factor for search rankings [1][3]
--Lied about using data from Chrome browser for search, including clicks. This contradicted their sworn testimony to the Department of Justice on anti-trust. [1][3]
--Lied about having a sandbox (to prevent "some" new sites from ranking) [1][2][3]
--Purposefully gave smaller "personal" sites their own category which ranked lower, EVEN IF they had more relevant information. To favor larger brands. [3]
They after removed the leaked data, but it was already published under an Apache open source license. [2] So now anyone can do whatever with it. The irony of Google having crappy privacy.
What should you use instead? Use a variety of engines.
Mojeek: Best privacy, but they aren't as well-funded. You gotta know what you want in advance
MetaGer: On Hetzner, so if you're coming through Tor which Hetzner dominates, its a conflict of interest
SearXNG: FOSS front-end for an aggregate. Farside.link has many instances.
Duckduckgo: They are not that private, but it pains me to say the results are not that bad.
Brave's Search: It's on Amazon AWS, but not bad indepedent results. As a heads up, if you use the Tor Onion it lets you do it without JavaScript.
And for Fs sake man, avoid Chrome browser.
(Sources in the comments from a burner account)
SimplifiedPrivacy.com Podcast / SimplifiedPrivacy.com
npub14s…jt5d6
2024-06-12 00:06:21
Author Public Key
npub14slk4lshtylkrqg9z0dvng09gn58h88frvnax7uga3v0h25szj4qzjt5d6Published at
2024-06-12 00:06:21Event JSON
{
"id": "e9d1b9db3816ae370e46426300694c769d3784fe13e547d0f84ed1ee773a9ea8",
"pubkey": "ac3f6afe17593f61810513dac9a1e544e87b9ce91b27d37b88ec58fbaa9014aa",
"created_at": 1718150781,
"kind": 1,
"tags": [],
"content": "Leaked Lies at Google\n\nGoogle accidentally leaked their search API on Github, giving everyone insight into that they:\n\n--Lied that they track users clicks as a factor for search rankings [1][3]\n\n--Lied about using data from Chrome browser for search, including clicks. This contradicted their sworn testimony to the Department of Justice on anti-trust. [1][3]\n\n--Lied about having a sandbox (to prevent \"some\" new sites from ranking) [1][2][3]\n\n--Purposefully gave smaller \"personal\" sites their own category which ranked lower, EVEN IF they had more relevant information. To favor larger brands. [3]\n\nThey after removed the leaked data, but it was already published under an Apache open source license. [2] So now anyone can do whatever with it. The irony of Google having crappy privacy.\n\nWhat should you use instead? Use a variety of engines.\n\nMojeek: Best privacy, but they aren't as well-funded. You gotta know what you want in advance\n\nMetaGer: On Hetzner, so if you're coming through Tor which Hetzner dominates, its a conflict of interest\n\nSearXNG: FOSS front-end for an aggregate. Farside.link has many instances.\n\nDuckduckgo: They are not that private, but it pains me to say the results are not that bad.\n\nBrave's Search: It's on Amazon AWS, but not bad indepedent results. As a heads up, if you use the Tor Onion it lets you do it without JavaScript.\n\nAnd for Fs sake man, avoid Chrome browser.\n\n(Sources in the comments from a burner account)",
"sig": "4d6c18ef1cd90ec5a6c31ce0e8d34d5c8f25028302417e26fce36716669957957c86dd333956ecb9c5b0a66d57e25a393bff894457b6a5579c1797b97a0f6dd8"
}