Add additional information

[jermanuts]

Changes proposed in this PR:

• I have disclosed any relevant conflicts of interest in my post.
• I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project.
• I am the sole author of this work.
• I agree to the Community Code of Conduct.

[netlify]

✅ Deploy Preview for privacyguides ready!

Name	Link
🔨 Latest commit	e304373
🔍 Latest deploy log	https://app.netlify.com/sites/privacyguides/deploys/6430636fe808cb0008dc476f
😎 Deploy Preview	https://deploy-preview-2112--privacyguides.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

Outdated approval, additional links added

[jonaharagon]

The changes from your original PR were merged in b074ed9 - I don't think that these additional links really add substance to the site, and I don't think we could consider many of them to really be "reliable sources."

[jermanuts]

I don't think we could consider many of them to really be "reliable sources."

Could you be more specific?

I picked articles where there is no security vulnerability to be patched, but rather insecurity by design. Specifically, Pass and deterministic password managers (there's an issue opened for it)

It's important to note that these financial services are not anonymous and are subject to "Know Your Customer" (KYC) laws and may require your ID or other identifying information.

"Privacy”.com–Yeah Right" proves cases where privacy.com ask for your ID (which happens too often).

[dngray]

I really dislike these Latacora articles, because they labor about "email security" and suggest things (Signal), which are not email. This is not helpful when you want email-styled/compatible providers as opposed to a transient instant messenger protocol the other recipient may not even use. We cover enough of that with the warning at the top of the page.

As far as email encryption across multiple providers go, PGP is and remains currently the only option, unless you opt for "form" based emails on the provider's server. I think providers like Proton and clients like Thunderbird have done a lot of work in making that usable for most people.

[jonaharagon]

proves cases where privacy.com ask for your ID

We already say this is the case on the website, so I don't know what value this adds. @dngray mentioned an issue with the other articles about email. In terms of reliability, these seem to be mostly blogs which are either non-independent or just generally can't be trusted: anyone can claim to be an expert on their blog.

Generally speaking though, after talking this through with the team I think we want to move away from "related links" sections and clean up or remove the ones we do have, not add additional ones. If information is important, we should be adding it to the site directly.

[dngray]

We don't list any of these currently, and they by far are not very popular. IMHO not worth mentioning.

[dngray]

We don't recommend pass, but we do recommend gopass. While this does have some of the issues mentioned, its rather obvious. We mention this is still useful as a very cut-down manager for scripting applications.

[dngray]

I do think this is one we could incorporate into the page.

[dngray]

We already say this is the case on the website, so I don't know what value this adds.

Indeed. Don't think this is worth adding. Privacy.com is not intended to make your purchases anonymous simply shield your credit card number from merchants. Financial industry does have regulation, especially payment providers like Visa and Mastercard, so this is to be expected. I do not think that blog article is worth adding.