Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove hosting providers #254

Merged
merged 1 commit into from
Nov 10, 2021
Merged

Remove hosting providers #254

merged 1 commit into from
Nov 10, 2021

Conversation

TommyTran732
Copy link
Contributor

Related Discussion: https://github.com/privacyguides/privacyguides.org/discussions/207

The hosting provider is subpar right now, it is unclear who the intended audience for this is. I don't think the suggestions are good either.

It is best to remove this for now. I have some idea on which providers to recommend for which purpose, and I will make a PR to readd this section with better quality content later.

@TommyTran732
Copy link
Contributor Author

The ran before I made my second commit :(
Would be great if we could run it again

@netlify
Copy link

netlify bot commented Nov 8, 2021

✔️ Deploy Preview for privacyguides ready!

🔨 Explore the source changes: 4a09eb2

🔍 Inspect the deploy log: https://app.netlify.com/sites/privacyguides/deploys/61893e594aa4ea0007057aa9

😎 Browse the preview: https://deploy-preview-254--privacyguides.netlify.app

@Mikaela Mikaela added the c:providers service providers and similar centralized/federated services label Nov 8, 2021
@Mikaela Mikaela requested review from a team and Mikaela and removed request for a team November 8, 2021 09:52
@dngray
Copy link
Member

dngray commented Nov 8, 2021

Agreed, we don't even eat our own dog-food on this. If this was to be re-added I think it would be necessary that there is a criteria.

@freddy-m
Copy link
Member

freddy-m commented Nov 9, 2021

@dngray IIRC we had this in the pipeline for PTio (#1196), though generally I think every section should have it's own criteria as per #24.

@dngray
Copy link
Member

dngray commented Nov 10, 2021

Well looking at that previous suggestion:

Prioritize Products by privacy respecting nationality.

This is something we already do in general across the site.

Cannot be based in USA or UK.

Those aren't the only two bad countries in the world. We're progressively phasing out mention of "eyes" countries because it is not the only intelligence gathering agreement. See: privacytools/privacytools.io#1437

Must be acessable via free software (i.e OpenVPN, WireGuard)

I can't think of any that aren't? That would be up to the owner, not the hosting service.

Use Encryption

Up to individual sysop to make certificates, so in other words the client. I don't know of any hosting providers that don't allow sftp/ssh.

Accept Cryptocurrency

Not inherently private, that depends on what cryptocurrency. You're gonna lose a lot of services if you say they must all take privacy coins like Monero or Zcash for example.

No logging policy

Hosting providers will do this to mitigate DDoS attacks etc. I don't think you'll find any "no logs" hosting providers out there.

@dngray dngray merged commit 7394473 into privacyguides:main Nov 10, 2021
@TommyTran732 TommyTran732 deleted the Hosting-Providers branch November 17, 2021 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:providers service providers and similar centralized/federated services
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants