privacyguides/privacytools.io
Archived
1
0
Fork 0
Code Issues 304 Pull Requests 47 Activity

hosting-provider: add a quick warning #1464

Closed
Mikaela wants to merge 3 commits from hosting-warning into master
pull from: hosting-warning
merge into: privacyguides:master
Conversation 13 Commits 3 Files Changed 1 +4
Mikaela commented 2019-11-04 11:42:52 +00:00 (Migrated from github.com)
Copy Link

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)
Copy Link

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)
Copy Link

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)
Copy Link

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
_includes/sections/hosting-provider.html
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
_includes/sections/hosting-provider.html
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
_includes/sections/hosting-provider.html
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
_includes/sections/hosting-provider.html
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
_includes/sections/hosting-provider.html
Mikaela (Migrated from github.com) commented 2019-11-12 12:28:03 +00:00

Changed to read, please rereview

Changed to read, please rereview
jonah commented 2019-11-13 23:25:02 +00:00
Copy Link

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.
👍 1
Mikaela commented 2019-11-14 21:03:54 +00:00 (Migrated from github.com)
Copy Link

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)
Copy Link

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.
Reviewers
No Reviewers
nitrohorse
Labels
Clear labels
🔍🤖 Search Engines
approved
approved, waiting for a PR
dependencies
Pull requests that update a dependency file
duplicate
feedback wanted
high priority
I2P
The Invisible Internet Project (I2P)
iOS
low priority
OS
Operating Systems
Self-contained networks
Social media
stale
A label for stalebot if it gets added
streaming
Anything related to media streaming.
todo
Tor
Anything covering the Tor network
WIP
active work in progress, do not merge or PR (yet)!
wontfix
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
XMPP
Extensible Messaging and Presence Protocol
[m]
Matrix protocol
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
Browser Extension related issues
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
Correction of content on the website
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
Firefox & forks, about:config etc.
💻 hardware
🌐 hosting
🏠 housekeeping
Anything primarily related to site cleanup.
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
Virtual Private Network
🌐 website issue
*Technical* issues with the website.
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
Domain Name System
🗨️ instant messaging (im)
🇦🇶 translations
Anything covering a translated version of the site
No Label
🌐 hosting
Milestone
No items
No Milestone
Assignees
Clear assignees
jonah
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1464
No description provided.
Delete Branch "hosting-warning"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?