@HowellsMead For those familiar, it may be a useful shorthand, but it simplifies things too far. Webmention uses knowledge of prior history and abuses of Trackback/Pingbacks/Refbacks and improves on them.
Cross reference: https:/
@dixongexpat @eatpodcast Had you come across this yet? https:/
@voxpelli may be able to point out documentation or help as well.
@evertp After having gotten Webmention working, you might consider stopping by the IndieWeb chat to ask this question of folks like @aaronpk, @t, @kevinmarks, and others who might provide some guidance/suggestions. As a group, they've been able to shepherd 3 specs to W3C Recommendation in almost as many years. We could all use some help on so many different levels.
https:/
#webstandards
@essenmitsosse Sharp eye. There's an extension to webmention called vouch to guard against abuse. https:/
@cogdog I have a lot of email spammers talking about my site who can't spell CONVERSATIONS either. What's worse is that when I contact them, none have ever even heard of simple standards like Webmention.
;)
Nate, it was great meeting you in person. I'm glad you made it to the IndieWeb Summit. Congratulations on getting Webmention working on your site!
@DavidWolfpaw There's https:/
Beyond this several of us have tests sites we could use to test things manually if necessary. Feel free to join us in chat for help and other ideas: https:/
@jgmac1106 A few short thoughts:
1. The explanatory text is nice, but runs a bit long for the uninitiated. I'm always worried that the length turns folks off? Perhaps something shorter for the gist of the idea with a link instead to a particular page that lays it out in more detail? I've also considered hiding some of the extra explanation behind a pop up or by using an abbr (or other appropriate html) tag with appropriate CSS hover markup so that when one hovers over a portion, they get a title-like window with all the gory details. Ideally, over time, with the spread of the concept the explanation won't be necessary at all.
2. One potentially crucial piece you're missing is that the post on their webpage HAS to have the permalink URL for your post on the page, otherwise the webmention will fail. Worse, without this bit of knowledge they won't know why it failed.
@fionajvoss Just for fun I built an own your own AMA page using webmention:
https:/
@noahread @madebydusk @manton2 @m_ott @CraftCMS
It depends on what data you want back into Craft. Most just want the replies/comments. Micro.blog does this via webmentions, thus the reason for having the webmention plugin set up to collect those replies.
@madebydusk @CraftCMS I think @m_ott has experience (and a plugin) with the webmention portion: https:/
The micro.blog portion should hopefully be as simple as inputting an RSS/JSON or other feed. @manton2 may possibly know of others.
Thanks for your questions. Several of us took a stab at answering them in the IndieWeb wiki today. You can find the answers here: https:/
I recall you said you were in the IndieWeb Slack channel, so if you need more specifics or help, please don't hesitate to stop by and one or more folks there will be happy to help you out the best we can.
@dajbelshaw Noterlive is primarily a posting interface to Twitter (mostly for livetweeting though it could continue to add some of that functionality in the future) that gives you back your data. You would still want to pay some attention to your account for side conversations and replies as well as other conference activity. In many cases I use it primarily as a note taking tool to keep content for archival purposes after the fact.
For additional two-way interaction you could use WordPress plugins like Webmention and Brid.gy Publish to get the comments, likes, etc. back to your website. I've outlined a piece of that type of workflow here: http:/
Otherwise, you might also consider going full IndieWeb, in which case you could post everything directly from your website and syndicate to Twitter and then getting all the responses directly back to your site. Some of this depends on how much work you want to do to get the moving pieces working properly. You'll notice this is roughly what I'm doing on my own site with you now. Example: http:/
@sadlerjw You've certainly found a few of the remaining pain points within the broader community and specifically with WordPress. There are obviously some UI bits like properly threaded conversations across multiple syndicated silos that could be better. I've written a tad about how threaded comments work between sites using WordPress, though didn't touch on the idea of doing so also using Twitter or micro.blog: http:/
Ideally in the end, everything would support Webmention and needing to syndicate to outside services would be somewhat moot.
As long as the conversation for something on micro.blog starts on your own site, the replies that occur there will generally flow back to your site via Webmention, but sadly one needs to use some manual chicanery to get a similar back and forth effect with other services like Twitter.
I suspect that in the coming months/year(s) things on this end will improve as the community marches forward.
Either way, congratulations on what you've done with you're site! Hope to see you around either via reader or micro.blog.
@openetc Have you considered adding the webmention plugins for site to site conversation between participants? https:/
https:/