# A schism in the OpenPGP world

**URL:** https://discuss.privacyguides.net/t/a-schism-in-the-openpgp-world/21005
**Category:** General
**Created:** 2024-09-20T08:52:01Z
**Posts:** 7
**Showing post:** 4 of 7

## Post 4 by @beantaco — 2024-09-21T01:55:27Z

> [@Regime6045](#):
>
> What are the most important players like Protonmail, Thunderbird, Mailvelope and OpenKeyChain using?

Most likely most downstreams have not yet substantially adopted either standard. Below is what I found after a brief search through the above sources, project webpages and other sources.

- Proton Mail: involved in crypto refresh; uses and maintains OpenPGP.js
- Thunderbird: uses RNP but is freezing implementation of new OpenPGP features
- Mailvelope: ?
- OpenKeychain: ?
- GnuPG: involved in LibrePGP
- Hockeypuck: the [draft standard for OpenPGP keyservers](https://datatracker.ietf.org/doc/html/draft-gallagher-openpgp-hkp) has some support for v6 keys but imposes limits in consideration of clients that do not support v6 keys
- `keys.openpgp.org`: its [governance board](https://keys.openpgp.org/about/news#2023-04-28-governance) includes people from Proton and Sequoia
- OpenPGP.js: supports crypto refresh; maintained by Proton Mail
- RNP: openly supports LibrePGP
- Sequoia PGP: involved in crypto refresh

I found [this article](https://blog.pgpkeys.eu/critique-critique) by a keyserver operator that discusses technical differences, describes the conflict as personal rather than technical, and proposes a way forward that hopes to achieve harmony between v5 and v6.

> [@anon48875053](#):
>
> All of those aren’t using the same exact same thing.

Yes, some implementations do their own quirky things, others simply don’t implement OpenPGP in full.

---

_[View the full topic](https://discuss.privacyguides.net/t/a-schism-in-the-openpgp-world/21005)._