A big thank you to everyone who's helped me reach my current fundraiser for support. I couldn't have done this without y'all.
I replied to the following: ↷
Few quick thoughts from first read, will try to give more detailed feedback later.
Header
X-Webmention-Status
Obligatory reference to RFC6648
status codes
How does
401happen?201wouldn't appear in a callback, would it (since it basically says "nothing happened yet to send you callback about")?rel-values
Using rel="status webmention-status" in my headers and HTML to allow for the discovery of the Webmention status page
Where would you place those? Not entirely clear to me. I.e. in the response to which request?
sknebel
•
posted
•
archived copy
•
currentTIL about RFC6648!
A 401 would happen if someone attempted to receive a private Webmention, but the credentials they've received were incorrect (like the code expiring too soon). I would show a 201 in a callback response only if we'd detected an asynchronous Webmention endpoint from the provided parameters, and this would signal that they haven't called us back yet. They could never call us back—which, for me, is okay, and I can treat that as a 200 after a period of time.
Posted with Quill at in Everything
Shared to GitHub
Engagement is powered by Webmentions — a premier standard of the Web to let other sites know you've mentioned them. Learn how to reply from your own site. or from a supported silo Aaron has an interactive post about this. If you've mentioned this URL via another one, use the form below to submit it.
If you don't currently own your replies, then you can click below to do so.
I currently aim to own my comments and plan to eventually show those I've received once I finish Lighthouse.