aaronpkI seem to remember something about the nonce adding to the entropy of the resulting string making it harder to reverse engineer the secret. If that's true, then it wouldn't matter whether the code has expired since you could gather a bunch of codes and analyze them even if they've expired
mblaneyI would be interested in understanding more about /Private-Webmention, if someone wants to answer my questions (maybe even add the answers to the page)
mblaneyie if as a webmention receiver, I'm going to provide an access token for any auth code I provide, what extra security is the back and forth providing?
gRegorLoveI don't know about the oauth reasonings behind it, but switching a short-lived auth code for the token seems like it's safer than just sending a longer-lived access token to the recipient.
gRegorLoveaccess tokens can (optionally) not expire, too, so in that case you definitely want to receiver to initiate the process, not just send it to them directly; anyone in-between or with access to logs could access the private post then.
sknebelpart of me thinks "they are just posts, dump them in the timeline and make sure your display code understands not to show it publicly", part of me wants to put them in their own, seperated space
aaronpksknebel: i'm planning on showing private webmentions on post permalinks the same as normal webmentions except only visible to me, and with a visibility indicator so that i know it's not public