HackerFriction Feedback

Products · Product

GPG

Raised as a usability problem by 307 people on Hacker News over 19 years (2008–2026), in 251 threads.

Ranked by people · period

No issue was raised by at least 3 people in 3 threads this year.

  1. 1
    Users set long key expirations or stop using PGP after expired-key errorsUnreviewed

    3 people in the last 5 years · 3 threads

  1. 1
    Key management is hard for usersUnreviewed

    19 people since the beginning · 18 threads

  2. 2
    Users cannot tell why emails fail to decryptUnreviewed

    16 people since the beginning · 13 threads

  3. 3
    Verifying keys requires manually tracking trust paths and importing keysUnreviewed

    6 people since the beginning · 6 threads

  4. 4
    Web of trust signing is unusable for non-technical peopleUnreviewed

    5 people since the beginning · 5 threads

  5. 5
    YubiKey setup is complicated and GPG often fails to find the keyUnreviewed

    5 people since the beginning · 5 threads

  6. 6
    Commit signing with ssh-agent is a nightmare to set upUnreviewed

    5 people since the beginning · 4 threads

  7. 7
    Unclear what a key means, so people get into troubleUnreviewed

    4 people since the beginning · 4 threads

  8. 8
    Key management needs a tutorial lookup due to counterintuitive commandsUnreviewed

    4 people since the beginning · 4 threads

  9. 9
    Crypto API is easy for non-experts to misuseUnreviewed

    4 people since the beginning · 4 threads

  10. 10
    Calling gpg as a subprocess is slow, fiddly to parse and awkwardUnreviewed

    3 people since the beginning · 3 threads

  11. 11
    Journalist could not figure out how to use PGP aloneUnreviewed

    3 people since the beginning · 3 threads

  12. 12
    Keyrings are cumbersome and error-prone to manageUnreviewed

    3 people since the beginning · 3 threads

  13. 13
    User documentation is confusingUnreviewed

    3 people since the beginning · 3 threads

  14. 14
    Users set long key expirations or stop using PGP after expired-key errorsUnreviewed

    3 people since the beginning · 3 threads

  15. 15
    Two confusing trust questions must be answeredUnreviewed

    3 people since the beginning · 3 threads

Every issue, all time, most people first

  1. Key management is hard for usersUnreviewed

    19 people since 2010, in 10 different years · none this year

    2008: 0 people2009: 0 people2010: 1 person2011: 0 people2012: 0 people2013: 3 people2014: 3 people2015: 4 people2016: 1 person2017: 0 people2018: 1 person2019: 1 person2020: 1 person2021: 3 people2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  2. Users cannot tell why emails fail to decryptUnreviewed

    16 people since 2013, in 8 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 5 people2014: 2 people2015: 1 person2016: 0 people2017: 1 person2018: 1 person2019: 2 people2020: 4 people2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  3. Verifying keys requires manually tracking trust paths and importing keysUnreviewed

    6 people since 2015, in 6 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 2 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 2 people2022: 0 people2023: 1 person2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  4. Web of trust signing is unusable for non-technical peopleUnreviewed

    5 people since 2013, in 5 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 0 people2015: 1 person2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 1 person
    20082026
    Something wrong here?
  5. YubiKey setup is complicated and GPG often fails to find the keyUnreviewed

    5 people since 2015, in 4 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 1 person2016: 1 person2017: 0 people2018: 0 people2019: 2 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  6. Commit signing with ssh-agent is a nightmare to set upUnreviewed

    5 people since 2018, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 2 people2019: 2 people2020: 0 people2021: 0 people2022: 1 person2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  7. Unclear what a key means, so people get into troubleUnreviewed

    4 people since 2014, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 1 person2016: 1 person2017: 0 people2018: 1 person2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  8. Key management needs a tutorial lookup due to counterintuitive commandsUnreviewed

    4 people since 2012, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 1 person2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  9. Crypto API is easy for non-experts to misuseUnreviewed

    4 people since 2013, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 2 people2014: 0 people2015: 1 person2016: 0 people2017: 1 person2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  10. Calling gpg as a subprocess is slow, fiddly to parse and awkwardUnreviewed

    3 people since 2014, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 1 person2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  11. Journalist could not figure out how to use PGP aloneUnreviewed

    3 people since 2015, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 1 person2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 1 person2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  12. Keyrings are cumbersome and error-prone to manageUnreviewed

    3 people since 2021, in 3 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 1 person2023: 0 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  13. User documentation is confusingUnreviewed

    3 people since 2018, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  14. Users set long key expirations or stop using PGP after expired-key errorsUnreviewed

    3 people since 2021, in 3 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 1 person2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  15. Two confusing trust questions must be answeredUnreviewed

    3 people since 2011, in 2 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 2 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?

This list counts all time; the period switch above only changes the ranking. Each issue is a group of similar complaints raised by at least 3 people in 3 different months and threads. Each line under an issue is Claude Haiku's summary of one of its latest comments, not a quote; follow it to read the comment on Hacker News.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 50 complaints