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
@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.
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.
Thinking about going #IndieWeb, but haven't made a platform choice? @GrabaPerch is an interesting choice with Webmention support and more. Also currently on sale! #DeleteFacebook
@kaushalmodi @_dgoldsmith It looks like @schussman has gotten Webmention and display as well as a manual box working on his Hugo site as well, so he may be of some help too: https:/
@huby plain old semantic HTML with microformats in combination with the webmention protocol allow one to post "likes" to one's own website and send them to others. Here's a simple example: http:/
@mlncn @hongpong I suspected Dries would find you both via the wiki having blazed some of the trail beforehand, so I didn't want to extend the post to point out what I suspected he would find quickly enough.
Simultaneously, my intention was to do a "BCC Webmention" of sorts so that the two of you were at least aware of his original post if you hadn't seen it. Sorry if it read as spam to some extent, but I didn't really have specific posts on all of your sites that would have made a huge amount sense to highlight to get them in via a traditional mention or a reply. Thus I did a few homepage webmentions to get them in under the wire, so to speak.
I don't think it's a common pattern to ping someone's site this way, but given the precedent and prior art within email, it seemed like a somewhat useful way to send the notification without making it so explicit. I'm glad you received it and understood at least some of the intention.
I didn't see a webmention endpoint on Dan's homepage, so I'm glad to have the chance to explicitly @mention him on Twitter with this post.
#bcc + #webmention = #bccwebmention
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:/
@mrkrndvs I'm curious if you manually cut & paste your replies for others' sites (who may not support webmention or even pingback/trackback) into their old-school comments sections?
I often worry that without that, or without replying to versions on Twitter if they syndicated, they won't see my response via pingback/trackback or other means. Instead my reply sits all alone on my site and they don't have the benefit of seeing it at all unless they come across it organically otherwise.
Generally when I manually cut and paste replies, I'll often use the comment's "website" field to include the permalink for my comment and then I'll take the permalink for my comment and add it to my syndication links since I've manually syndicated it.
Sometimes I notice that including multiple links in a reply can also run afoul of spam filters.
One of my favorite set of machinations occurred recently when I wrote this reply to Jon Udell: http:/
Jon came back to his original post and appended his own comment to document my comment in the most circuitous of manners which included using his annotation tool Hypothes.is: https:/
Interestingly we both used WordPress, Hypothes.is, and Twitter to carry on the conversation. I was quite impressed that he took the time to circle back around and document my end of the conversation since he must have missed my pingback (he doesn't have webmentions) and my manual cut & paste, but did manage to see the notification on Twitter.
It all just goes to show that you've got to keep your eye on the tech that you and everyone else is using until it's broadly and evenly distributed. One day perhaps...