Hey, sorry for taking a long time, but I am farting around with the pinentry option now.

I don't have screens, but I wanted to point out a few scenarios that are challenging with fuzzel:

1. as I was trying to describe before, the ability to write accompanying text is pretty important, as you need to be able to describe what gpg key is to be unlocked, and typically a string like "Enter PIN for Richard Nixon nobody@trickydicky.gov" is used - which is too long for fuzzel (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-descriptive-text-to-display) Also keep in mind the error scenario, which adds even more copy (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-error-text). Lastly there is a "set window title" feature, which is perhaps not important for us (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-button-texts)
2. There are message scenarios which are difficult to place with fuzzel. Even if I wanted to just fail out some scenarios like reties, I would want some "notification", and would probably like to have fuzzel also used for that in order to keep the UI consistend across use cases. (https://gorbe.io/posts/gnupg/pinentry/documentation/#message-box)
3. There are cases where pinentry is expected to set copy for buttons for OK and Cancel and "Do not do this", IIRC to get internationalization. I think that these are less important. (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-button-texts)

(ping @markstos@lemmy.world )

https://github.com/james-nesbitt/pinentry-fuzzel is a first try, shamelessly stealing everything from https://github.com/zamlz/pinentry-rofi/blob/main/src/pinentry-rofi.sh