Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, Indieweb, and the entertainment industry including: finance, distribution, representation
Within the past month [it's guestimated that over 1 million webmentions](https:/
Mastodon already supports most microformats for webmention to be implemented more easily. https:/
There are already a number of open source tools that might also be bootstrapped for something like this as well: https:/
For those interested in more and who know a bit of code, David's also got a "master class" on adding microformats to modern themes in his commit trail for updating/upgrading the TwentySixteen theme to be more IndieWeb friendly: https:/
While it isn't comprehensive and may not cover every eventuality for every theme, following along with his commits here will get you a long way towards better understanding microformats v2 use with WordPress. I think I've learned more about WordPress themes and microformats by following his changes here than anything else I've tried.
I suspect that next, with a tad bit of parsing using microformats, you can add some display elements to your webmentions to indicate the author, their url, date/time, and actually include the reply text to have a better UI for them. Then they'll look a bit more like the traditional comments you may have envisioned. (Something along the lines seen in my comments at http:/
I think that #DtMH2017 group could use a Slack channel (or other chat) in addition to a wiki to collaborate throughout the year
Wiki is better than email, see: http:/
@khurtwilliams POSSE for WordPress can be tricky in part because, compared to most other IndieWeb pieces for WordPress, there are multiple different and varying ways to do it. Using one method could potentially conflict with another depending on how you set things up, though I think these are relatively few.
Your best bet is to hop into the #WordPress channel of the IndieWeb chat https:/
In general, the more control and flexibility you want over the display of your POSSE posts, the more set up and work you have to put into it (e.g. SNAP), while the less control you have the more simple the set up (e.g. JetPack Publicize).
Things like Brid.gy publish functionality (or via the Brid.gy Publish plugin) can be more finicky for POSSE copies to silos because Brid.gy is parsing your site for the proper data to publish. (It does have a preview button built in to do manual tests if you need to.) This means that if your WordPress theme doesn't have the correct microformats markup (and often they don't), then you can get spurious results, particularly when it comes to crossposting photos.
Most of the main POSSE plugins and tech are very stable in fact, but they do require that you do a bit of reading and understanding what they do and don't do and what you can and can't control with them. Most all of them have GitHub repositories that you can post issues to and almost all the devs, maintainers, and community are happy to help you out and/or make changes to make the UI and documentation better.
As for backfeed from Brid.gy, it generally requires that the URLs of your post and the syndicated post have matching permalinks to be able to match the two up to send you the webmentions properly. You may have changed your settings, but one piece you appear to be missing is the Syndication Links Plugin which allows you to add u-syndication links to your posts so that Brid.gy knows which ones to send your responses to. Much of this is documented at https:/
I'm sure I've got a few odd posts from ages ago when I tested things out, but when you say "I can also see from some of the failed posts on your website that you may experience the same issues." I'm curious which particular posts you mean? To my knowledge things I intend to syndicate out are currently working as I expect them to (aside from one quirk that occasionally spams the Indieweb chat with micropubbed posts which continually redirect, but that's specific only to me because of some experimental code I've been running). It is the case that I don't always syndicate everything to each and every silo target I could. I do very much pick and choose which things to syndicate to particular networks.
We'll help you get there yet!
For wider adoption, your best bet is probably to pare down WordPress a tad and see what you can make of it. I know David Shanske has a starter version of Underscores with microformats in it already. I think a large portion of the micro.blog crowd that has gone IndieWeb are using it as their CMS of choice.
The other interesting platform to look at is WithKnown which was built from scratch with IndieWeb specifically in mind.
For adopt-a-bility and reach, you could also look at building things like webmentions into projects like Mastodon which already has some IndieWeb pieces built into it.
You could also try asking in the IndieWeb chat at https:/
Here's a rough chart that may give you some useful ideas too: https:/
Aaron, I suspect that the visible code <span class='p-author h-card'>Aaron Davis</span> which appears on your byline on your site is the result of the uf2 plugin https:/
Andreas, The best way I'm aware of to do read posts with #WithKnown currently is to post a status update to the effect. I've been considering doing a plugin similar to Jonathan LaCour's Watching https:/
I've started hacking away at a Read plugin similar to the bookmark or like functionalities that simply bookmarks articles which I've read online, but it's got some quirky upstream issues that need to be solved before I can finish it. Ultimately it's really for online content more so than books (or even magazines) though. I may circle back around to it sometime toward the end of the summer as I'm trying to finish up some last pieces on my Reading workflows for WordPress.
Some of the issue is that WordPress has a huge number of plugins which adds a lot of additional complexity (especially for Micropub clients) which isn't always going to be handled by every client.
As for webmentions, they're being bolted onto WordPress which doesn't have (or allow) a custom comment type, so they're jury-rigged in the best manner possible. There is still ongoing work, especially with the Semantic Linkbacks Plugin which does a lot of the heavy lifting here, if you've got thoughts/ideas, you should certainly weigh in on those Github issues as they are evolving.
I know there were a handful of quirks that have been changed in Known in the past months to fix some issues with microformats that were being parsed incorrectly, and thus caused other platforms like WordPress not to let them display as nicely when received. I think most have been merged and a new release of Known was pushed yesterday and should hopefully clear up some of these issues. I think the developers of the WordPress plugins and even the Known community are very responsive, so feel free to jump in with feedback, suggestions, or even pull requests on any of the pieces which are all on GitHub.
I'm sure there will be some remaining rough edges, but in general a lot of them have been smoothed over in the past year and most improvements now seem to be geared towards making the suite of tools more user friendly or to better extend the functionality.