@sandeepshetty @pfefferle cweiske Something new to consider: Jeremy Keith added a webmention sending form to his journal entries to help people who’s websites don’t support webmention already. Being able to test and use webmention through a human visible, interactable form is a huge benefit of using HTTP form encoded data.
We can make this an even stronger case by encouraging success and error responses to be full HTML documents with helpful copy.
Also, many implementations are already parsing the target HTML for reply-contexts (e.g. Aaron Parecki (example), @jschweinsberg (example) and myself (example)), demonstrating that parsing HTML is not a significant barrier.
@benhowdle @trailedapp congrats on the launch! Great that you’re encouraging people to own their comments. Have you come across indiewebcamp.com at all, especially the work we’re doing on cross-site replying, webmentions and reply-contexts? E.G. this post is a reply on my own site to one of your tweets :)
Great work getting webmention set up and your content marked up with microformats!
At the moment of the method is built around a POSSE architecture. This works well for long form articles which can stand alone but address issues or ideas that are posted on an external website.
The evidence is against you here, as almost all known usage of webmention has been for short replies which don’t make sense without context.
But if that is all there is to webmentions it is just a nicer implementation of Pingback.
Pingback succeeded because it was simple. Webmention is even simpler, for good reason.
However the current workflow is awkward and i doubt it will catch on with the general public. Sophisticated Indieweb users can and will read an article on an external site and then return to their own to post a comment, but that king of behaviour is not intuitive.
I absolutely agree! I’m trying various different approaches to making this easier (and making web content more actionable in general), currently I’m using web action toolbelt to really quickly reply to content on other sites. There’s been a lot of discussion about this, and it’s something which everyone can work on as more people start implementing indieweb comments.
I make the comment on the external site and as part of making the comment I add my author url, that being the url of my own site. The external site then sends a webmention of the comment to my site. My own site could then scrapes my comment and saves a copy in my CMS. Otionall I could republish the comment in my blog or activity feed at my discretion. Thus fully implementing PESOS.
We actually discussed this exact flow at IWCUK 2012, but no-one ever implemented it because, with browser extensions, there’s no need to log in to other people’s sites (complex to implement) and have those sites post to each other (security hole).
Thanks for bringing these issues up, it’s great to have new people join the discussion! I’ll start documenting your points on the Indiewebcamp wiki — it’s there and on the #indiewebcamp IRC room where most discussion takes place.