privacy-resources: delist The Great Cloudwall #1804

jonah · 2020-03-27T17:30:14Z

Mikaela commented

2020-03-27 17:30:14 +00:00

(Migrated from github.com)

https://deploy-preview-1804--privacytools-io.netlify.com/#resources

* https://deploy-preview-1804--privacytools-io.netlify.com/#resources

netlify[bot] commented

2020-03-27 17:30:48 +00:00

(Migrated from github.com)

Deploy preview for privacytools-io ready!

Built with commit 18d1a1600a

https://deploy-preview-1804--privacytools-io.netlify.com

Deploy preview for *privacytools-io* ready! Built with commit 18d1a1600acbd90213c50d6529976a16de9ef1da https://deploy-preview-1804--privacytools-io.netlify.com

dngray (Migrated from github.com) reviewed 2020-03-27 17:35:48 +00:00

dngray (Migrated from github.com) reviewed 2020-03-27 17:44:07 +00:00

dngray (Migrated from github.com) left a comment

To be honest, I'm not a fan of this page, due to the way it's presented.

I also was getting basic authentication requests on this link.

To be honest, I'm not a fan of this page, due to the way it's presented. I also was getting basic authentication requests on this link.

dngray commented

2020-03-27 17:47:37 +00:00

(Migrated from github.com)

I think in order to approve this, I would have to see some of the fluff meme stuff that does not look professional at all removed.

While it does raise some good points, I think in general it should be more succinct. Maybe we can replace it entirely with a blog post or something.

I think in order to approve this, I would have to see some of the fluff meme stuff that does not look professional at all removed. While it does raise some good points, I think in general it should be more succinct. Maybe we can replace it entirely with a blog post or something.

dngray commented

2020-03-27 18:00:27 +00:00

(Migrated from github.com)

After looking at this further I think we should remove it. It diverges into tirades that don't seem relevant. The meme rubbish sounds unprofessional and it does reflect on us by linking to it.

And their DNS service, 1.1.1.1, is also filtering out users from visiting the website by returning fake IP address owned by Cloudflare, localhost IP such as “127.0.0.x”, or just return nothing. Cloudflare DNS also break online software from smartphone app to computer game because of their fake DNS answer.

Also that I don't believe is factually correct. There can be other reasons why this happens, Eg. https://news.ycombinator.com/item?id=19828702

After looking at this further I think we should remove it. It diverges into tirades that don't seem relevant. The meme rubbish sounds unprofessional and it does reflect on us by linking to it. > And their DNS service, [1.1.1.1](https://1.1.1.1/), is also filtering out users from visiting the website by returning [fake IP](https://trac.torproject.org/projects/tor/ticket/32915) address owned by Cloudflare, localhost IP such as “127.0.0.x”, or just return nothing. Cloudflare DNS also [break](https://nitter.net/bowranger/status/1213031783576428550) [online](https://nitter.net/jb510/status/1212521533907668992) [software](https://nitter.net/No_Style/status/1201525422795710466) [from](https://nitter.net/daemuth/status/1187758306535903233) [smartphone](https://nitter.net/gregortorrence/status/1183102089439805441) [app to computer game because of their fake DNS answer](https://git.nixnet.xyz/you/stop_cloudflare/src/branch/master/PEOPLE.md). Also that I don't believe is factually correct. There can be other reasons why this happens, Eg. https://news.ycombinator.com/item?id=19828702

dngray (Migrated from github.com) approved these changes 2020-03-27 18:08:16 +00:00

dngray commented

2020-03-27 18:38:37 +00:00

(Migrated from github.com)

This was also somewhat related https://community.cloudflare.com/t/what-data-does-cloudflare-actually-see/28660

Comes down to threat model. It is good enough to be secure from outside adversaries... but no don't rely on CloudFlare to help you be the next Edward Snowden.

For that you want true E2EE. Double Ratchet, OTR, OpenPGP etc.

I do agree that their captchas can be annoying. Recaptcha is okay when it works, but it is annoying when it just gives you another one to do. Fortunately I haven't seen too many of those lately so maybe they've relaxed a little on that.

This was also somewhat related https://community.cloudflare.com/t/what-data-does-cloudflare-actually-see/28660 Comes down to threat model. It is good enough to be secure from outside adversaries... but no don't rely on CloudFlare to help you be the next Edward Snowden. For that you want true E2EE. Double Ratchet, OTR, OpenPGP etc. I do agree that their captchas can be annoying. Recaptcha is okay when it works, but it is annoying when it just gives you another one to do. Fortunately I haven't seen too many of those lately so maybe they've relaxed a little on that.

jonah approved these changes 2020-03-27 18:41:14 +00:00

jonah left a comment

Finally 👌

This repo is archived. You cannot comment on pull requests.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1804