hosting-provider: add a quick warning #1464

Closed
Mikaela wants to merge 3 commits from hosting-warning into master
Mikaela commented 2019-11-04 11:42:52 +00:00 (Migrated from github.com)

Description

Resolves: #1341

## Description Resolves: #1341 * Netlify preview for the mainly edited page: https://deploy-preview-1464--privacytools-io.netlify.com/providers/hosting/
nitrohorse (Migrated from github.com) reviewed 2019-11-04 11:42:52 +00:00
netlify[bot] commented 2019-11-04 11:43:43 +00:00 (Migrated from github.com)

Deploy preview for privacytools-io ready!

Built with commit ebae9b8f74

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

Deploy preview for *privacytools-io* ready! Built with commit ebae9b8f7483ccd93de65ab4d43fca5139321bef https://deploy-preview-1464--privacytools-io.netlify.com
Mikaela commented 2019-11-05 11:47:23 +00:00 (Migrated from github.com)

Linda:

https://github.com/privacytoolsIO/privacytools.io/pull/1464
The problem at https://github.com/privacytoolsIO/privacytools.io/issues/1341 is more about "won't track your visitors or give into government data requests" being dangerous to say. The quick warning is "fine", but it's not fine because... it's self-explanatory and not really a warning at all.
It's best to question why such warning would be there in first place, as if PTIO didn't know what it was recommending or why.
And honestly, I don't have an idea why PTIO is recommending any of those but Njalla.
I know Bahnhof, but I don't know why it's on that list.
Companies also have to keep records for tax purposes, etc.

Linda: > https://github.com/privacytoolsIO/privacytools.io/pull/1464 > The problem at https://github.com/privacytoolsIO/privacytools.io/issues/1341 is more about "won't track your visitors or give into government data requests" being dangerous to say. The quick warning is "fine", but it's not fine because... it's self-explanatory and not really a warning at all. > It's best to question why such warning would be there in first place, as if PTIO didn't know what it was recommending or why. > And honestly, I *don't* have an idea why PTIO is recommending any of those but Njalla. > I know Bahnhof, but I don't know why it's on that list. > Companies also have to keep records for tax purposes, etc.
Mikaela commented 2019-11-05 11:51:56 +00:00 (Migrated from github.com)

I don't know these providers well personally, but I would argue that a warning is necessary as we aren't all-knowing.

See also https://github.com/privacytoolsIO/privacytools.io/issues/1196

I don't know these providers well personally, but I would argue that a warning is necessary as we aren't all-knowing. See also https://github.com/privacytoolsIO/privacytools.io/issues/1196
nitrohorse (Migrated from github.com) reviewed 2019-11-11 00:14:03 +00:00
nitrohorse (Migrated from github.com) commented 2019-11-11 00:13:58 +00:00

What about adding an additional suggestion to verify their privacy policies?

  <strong>Note: We cannot know what the hosting providers are doing and have to take their word on it. Please verify their privacy policies.</strong>
What about adding an additional suggestion to verify their privacy policies? ```suggestion <strong>Note: We cannot know what the hosting providers are doing and have to take their word on it. Please verify their privacy policies.</strong> ```
Mikaela (Migrated from github.com) reviewed 2019-11-11 09:37:54 +00:00
Mikaela (Migrated from github.com) commented 2019-11-11 09:37:54 +00:00

I committed this, but would "read" make more sense than "verify" ?

I committed this, but would "read" make more sense than "verify" ?
nitrohorse (Migrated from github.com) reviewed 2019-11-12 00:53:07 +00:00
nitrohorse (Migrated from github.com) reviewed 2019-11-12 00:54:18 +00:00
nitrohorse (Migrated from github.com) commented 2019-11-12 00:54:18 +00:00

I meant verifying their claims on their main home pages, but yeah “read” probably is more clear.

I meant verifying their claims on their main home pages, but yeah “read” probably is more clear.
Mikaela (Migrated from github.com) reviewed 2019-11-12 12:27:20 +00:00
Mikaela (Migrated from github.com) commented 2019-11-12 12:27:19 +00:00
  <strong>Note: We cannot know what the hosting providers are doing and have to take their word on it. Please read their privacy policies.</strong>

Lazy suggestion, so I don't have to terminal it.

```suggestion <strong>Note: We cannot know what the hosting providers are doing and have to take their word on it. Please read their privacy policies.</strong> ``` Lazy suggestion, so I don't have to terminal it.
Mikaela (Migrated from github.com) reviewed 2019-11-12 12:28:03 +00:00
Mikaela (Migrated from github.com) commented 2019-11-12 12:28:03 +00:00

Changed to read, please rereview

Changed to read, please rereview

I do not think this is necessary, or we would have to add such a warning to every page on the site. VPN and DNS providers seem like special cases because they will receive your data when you are visiting third parties. Hosting providers will only see your data when you are directly accessing their servers. We also have a lot of VPN- and DNS-specific text respectively, whereas this is just a simple sentence.

If we want to add a generic warning, adding some text for clarification of our point and putting it on https://www.privacytools.io/providers/ would be a better solution.

I do not think this is necessary, or we would have to add such a warning to every page on the site. VPN and DNS providers seem like special cases because they will receive your data when you are visiting third parties. Hosting providers will only see your data when you are directly accessing their servers. We also have a lot of VPN- and DNS-specific text respectively, whereas this is just a simple sentence. If we want to add a generic warning, adding some text for clarification of our point and putting it on https://www.privacytools.io/providers/ would be a better solution.
Mikaela commented 2019-11-14 21:03:54 +00:00 (Migrated from github.com)

Hosting providers will only see your data when you are directly accessing their servers.

I don't understand how to interpret this. Hosting provider has root on your servers and thus see my data when I am using anything not-E2EE on a server hosted on them.

> Hosting providers will only see your data when you are directly accessing their servers. I don't understand how to interpret this. Hosting provider has root on your servers and thus see my data when I am using anything not-E2EE on a server hosted on them.
Mikaela commented 2020-04-19 18:14:52 +00:00 (Migrated from github.com)

I am unlikely to work on this any time soon.

I am unlikely to work on this any time soon.
This repo is archived. You cannot comment on pull requests.
No reviewers
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1464
No description provided.