ZegnatI do not think we have documented any sort of best practices like that. But I could totally see how it would be interesting to check periodically if previously undeliverable mentions can be delivered
ZegnatNot really. I think there is also the question of different strategies depending on why it failed to deliver a mention. E.g. if a site does not advertise a webmention endpoint at all, just doing the GET request to check if they have implemented one can be done at some regular interval. If they did advertise an endpoint but the endpoint failed to respond to your POST request, maybe you want to try again a little sooner, but have some
nolithaaronpk: I was implementing quill editor features in my micropub. I got confused by content.html not being an array like all the other fields. Is that expected?
nolithsknebel: ok so it's an array of objects. Ok then quill is sending the right thing, there are only two errors in the docs (type and the lack ok {} in the content object). Thanks
capjamesg[d]"This post's Webmention endpoint has query string parameters. Your Webmention client must preserve the query string parameters, and not send them in the post body."
aaronpkif the endpoint is something like example.com/webmention?foo=bar then you need to not move the foo=bar into the post body, it has to stay in the query string. so you'd make a POST to example.com/webmention?foo=bar with source=X&target=Y in the body
[tantek]more general dev/inventor/creator methodology related rather than indieweb-specific, however, could very much apply to many things we build here (especially since so much of it is OSS). assume the tools you create can & will fall into the hands of those who may have different values / ethics than yourself: https://theintercept.com/2021/08/17/afghanistan-taliban-military-biometrics/
sknebelif you dont have that you can of course do it manually, but then the consideration for when to send mentions still applies, just to you in your head ;)
[snarfed]"There was an interesting discussion in a working group session at the recent IETF 111 meeting over a proposal that this working group should require at least two implementations (presumably independently developed implementations) of a working group draft before the working group would consider the document ready for submission to the IESG for progression to publication as an RFC. What's going on here?"