@gerowen @wuwei @jonas @sudo you are *trusting* #DDG to do what they say they do, & they've already been caught violating their privacy policy by issueing tracker cookies. The CEO also has a history of #privacy abuse. DDG is obviously untrustworthy. DDG also finances privacy abusers (#Verizon, #Amazon, & #MS), & supports #CloudFlare.
@sudo @jonas @wuwei That's grasping for straws. I struggle to see how someone can be so mentally challenged as to be unable do a #Searxes query, even if the field has an Esperanto background. Results are in English. There are also other options that don't simultaneously feed Amazon, Verizon-Yahoo, and MS. DDG is a poor recommendation from a #privacy PoV.
@jonas @wuwei and to say any searx instance "don't return anything due to bad configuration", it's wrong to say the config is bad. It's a consequence of /scraping/ instead of /buying API access/, & this is good for #privacy. #DDG buys API access, which entails helping #Verizon (a privacy abuser) profit.
@Tutanota @jonas @Tutanota #Duckduckgo is a terrible recommendation. see https://dev.lemmy.ml/post/29179
@Mr_Teatime @nipos the Firefox plugin that redirects CF sites is called "Block Cloudflare MITM Attack" and is posted here: https://addons.mozilla.org/en-US/firefox/user/14218621/. Description is in cyrillic but don't let that scare you off. This plugin will outright block CF sites: https://gitlab.com/gkrishnaks/cloud-firewall
@nipos @Mr_Teatime there is a very useful browser plugin that detects #CloudFlare & automatically redirects to the archive of the page.
@Mr_Teatime @nipos archive.org does #Tor users a service b/c it helps bypass the #CAPTCHA (if needed) & ensures the target site is not rewarded w/traffic or interaction.
@nipos @Mr_Teatime #CloudFlare w/ #Tor whitelisted is even worse, b/c then Tor users don't know they are interacting w/a CF MitM. Tor users then unwittingly support a Tor adversary.
#CloudFlare is now hitting the archive.org wayback machine with the same #CAPTCHA as #Tor users, thus censoring history too.
@Yes2020 @theprivacyfoundation actually there are no obvious problems with mastodon.scot (it's not a #CloudFlare site & not hosted by a tech giant). The issues discussed in the thread are specifically with mastodon.social.
@theprivacyfoundation
VPN is still lousy advice b/c there is no anonymity. The entry node knows the origin and the network thereafter sees the whole path. Even when combined with #Tor or #I2p, both of which anonymize independently, the VPN results in 1 IP or a small set of IPs that make you trackable particularly when combined w/your client fingerprint.
Your advice is still dangerous. It's also pointless & unethical. Suggesting less effective tools to feed #CloudFlare is foolish
@theprivacyfoundation
That's dangerous advice. Have a look at CVE-2019-14899. All VPNs compromised.
No one claims you can have "perfectionism". Of course, there are good options and bad options. #CloudFlare sites like mastodon.social are profoundly stupid choices to endorse.
Even if you neglect the #Tor hostility & #VPN weakness, CF still sees all traffic. Also, using CF feeds a #privacy abuser financially, which works against your alleged cause.
@theprivacyfoundation
Sure there are many instances. Some are respecting of #freedom & #privacy, and some are not. #CloudFlare is an abuser of privacy & #netneutrality. You've specifically endorsed a CF node (mastodon.social). As a "privacy foundation", you should know better and you should set a better example.
@bojkotiMalbona
If the house across the street installs #AmazonRing or #Google #Nest in a way that surveils my house, it will be an act of war.
@bojkotiMalbona
If the house across the street installs #AmazonRing or #Google #Nest in a way that surveils my house, it will be an act of war.