Jack, Your response (above on your site) is a good example of watching what is going on and knowing what your site can and can't do.
Because you put your response directly into the comment box on your site (ostensibly in a general sense to the main post rather than to my response), your site didn't send me a webmention for it and so I didn't know you had responded except that I happened to come back to your post. If you visit it, you'll see that your reply doesn't show up on http:/
The better method using Known would have been for you to have clicked the permalink on your site for my comment (the date of my comment or the name of my site) that would have gone to my original, you could then have used the bookmarklet for Known (found at https:/
Because I'm replying to both your post and mine, it should show up via webmention on both. The manual comment box on Known is really only for people whose sites don't support Webmention. Some people actually disable the comment box functionality and only receive Webmentions as a means of preventing spam comments.
In an ideal world, your comment box would send both Webmentions and salmentions to maintain the integrity of the comment thread. Since it doesn't (yet) then you need to do that manually, especially if you want me to see your reply.
Hopefully all this makes some sense...
Here's a photo post of some of the UI that may make it make a bit more sense: http:/
I think a lot of the problem comes down to all of the siloed walls out there which are causing most of the friction. We're still relatively early days yet and only a tiny few are using the concept of salmention which would help keep running threads working properly. Admittedly having the context live somewhere and then having proper threaded communications isn't easy, so many do what they're able to for the moment.
I'm usually attempting to manually accomplish salmention as best as I'm able, but I may not hit every syndicated target unless you're displaying it directly. Additionally some targets just don't make sense--I'll webmention your original, for example, but this lengthy reply just won't look right at micro.blog if you syndicated a simple headline and URL there, so why bother since you'll see it at the original anyway? Others who are on micro.blog may miss out on part of the conversation, but presumably if they're looking at your copy on micro.blog, they'll be able to see the original as it was intended.
Colin, you mention that not all of your content needs to go to micro.blog. Perhaps, but to think so in my mind is part of the older silo way of thinking. The only reason you're syndicating there is as a stopgap to reach the people who don't currently have the time or luxury to be doing things the way you are. Otherwise they could subscribe to you directly at the source (and potentially even circumscribe the types of posts, keywords, or content to get exactly what they want from your site.) In some sense you syndicate there to reach and communicate with the non-IndieWeb crowd. Perhaps some of your content doesn't make as much sense there as Micro.blog is limited in what it is able to do, but that is its limitation, not yours. Eventually in a fully IndieWeb-ified world, everyone would have their own domain, their own data, and syndication of any sort won't have a real need to exist at all.
As to Jack's comment, syndicating things out to multiple places is often difficult as is getting all the responses back. (Fortunately services like Brid.gy make things far easier though they don't cover all the bases.) I do it in large part because while I prefer to own all of my content and have all the conversation take place on my personal site, I can't necessarily make that choice for everyone else. My mom is likely to never have her own domain much less a site. The only way she'll see my content (whether it's meant for her or not) is to syndicate it to Facebook. For those who aren't yet aware of the IndieWeb or using it, they're still reading and interacting on other platforms, which, for me is fine since I can still have my cake and eat it too. Eventually there will be inexpensive platforms that will let people who don't want to deal with the development cost and overhead that allow much of the IndieWeb-types of functionalities they're not currently getting from their silo platforms for free. I suspect that these will be easier and easier (as well as cheaper) to use over time. I suspect more people will use them for their freedom, flexibility, and increased control. Until then, I have the privilege of using my site much the way I would Facebook, Twitter, Instagram, Google+, Flickr, GoodReads, etc., etc., I just get to do it through a more unified experience instead of having to juggle dozens of accounts and only being able to interact with my fractions of friends, family, and colleagues who coincidentally happen to be spending the time and effort to interact on those websites. As an example, I have dozens of friends who interact with me on Facebook about things I'm currently reading or finished reading, but if I was only doing this on GoodReads, they'd never have a chance to see it as they don't have accounts there or even know it exists. (Coincidentally, this is also the reason that GoodReads and most other silos allow one to syndicate their accounts to Twitter, Facebook, etc.)
Not all social sites are as lucky as Facebook to have such massive adoption. This creates a value imbalance with respect to the classic "network effect" (see: https:/
Invariably some people are likely to stick with Twitter, Facebook, or others because they don't have the same values I do. (Currently I suspect the majority do it because it's frictionless and easy.) But this doesn't change the fact that one can't have a "universal" conversation if one prefers. When I look at various platforms, some of them have different personalities and types of conversations because of the (possibly) self-selecting group of people on them. I loved Twitter more in the early days because of it's smaller and more engaged community--things have naturally changed drastically since those early days. Micro.blog is a bit more like it now, but to me it's not so much a social media replacement for Twitter. To me it's really a social reader that I use to quickly follow a subset of interesting and thoughtful people until I have a better social reader built into my own site. The conversation would be somewhat different if these silos were working on niche audience content like knitting or quantum mechanics, but typically they're not. Most social silos are geared toward mass adoption and broad topic discussion or content posting for everyone/everywhere. Their goal is for their site to be the proverbial "phone number and dial-tone of the web". Why do this when I already have a connection and a "phone number" that is my own site URL?
Jack, while some bloggers have turned off comments, they've often done so saying "Post your reply on your own site, or on Twitter, Facebook, etc." This has just pushed the conversation on their ideas off somewhere else which is disconnected and not as easily searchable or discoverable. And without some kind of notification mechanism, the author of the original post has no idea it exists. (I'll elide a conversation about blocking trolls and abuse here.) I've written some thoughts on comments sections in reply to such a blogger who recently re-enabled comments which also links to several interesting articles about the pros/cons of having comments at all. To me, between webmentions, spam filtering, and even moderation, we're lightyears ahead of where we were in the early 2000s.
One other thing I do find interesting is that the way all of this is set up is allowing us the ability to write extended thoughts and extended multiple replies (with civility as relative strangers). I don't think there are many sites on the web that allow this type of interaction, and they certainly don't do it with anything remotely close to the open architecture we're using. While at times it can be a headache for maintenance and problems, I find far more value in it than using anything else.
I suspect that markdown or semi-complicated html (like you, I occasionally like to do this too, even if it's just bold or italics) in replies are a second class citizen because most major CMSes (including Known) strip out or severely limit (for security reasons) the html that is accepted in comment fields. In fact, to conserve on space, I've even noticed that many even strip out blank lines between paragraphs! Many also will mark as spam comments that have one or more URLs in them. As a result doing fancy or even mildly complicated html or markdown in replies is something for which most platforms just don't build.
The other issue in status updates and replies is that they're often syndicated to other platforms and it's a more difficult issue to properly do this with each snowflake social media silo depending on how they individually handle html/markdown (or not). I do this sometimes in WordPress to properly format syndicated content, and it easily triples the amount of manual work, so be careful what you wish for. (This may also be the reason I love Known so much too!)
Every now and then I'll write an extended reply to someone's post that gets to the point that headings, additional structure, and the frills become much more valuable. In those cases, I'd probably then default to make them posts/articles and add the additional touches and then do a manual mark up of u-in-reply-to to have them show up as a reply instead of just a mention. This happens so generally rarely that it's not too much of a headache.
Either way, the end result on the other person's site isn't something I can ever control for, so I try not to sweat it too much. :)
I'll check to see if it's the case with altplatforms' bug, but I've discovered that it's having Jetpack's commenting feature "Let readers use WordPress.com, Twitter, Facebook, or Google+ accounts to comment" activated that prevents the Webmention Form from appearing on the page. If I deactivate it, it not only appears properly, but shows up twice with the standalone plugin installed.
Incidentally it also causes issues on my 2016 theme where if one types too much in the enclosed field, the UI moves down and it becomes impossible to actually post the comment!
While I'm thinking about it, as an Indieweb-forward thought, would it be possible to put the Webmention Form at the top of the comment section instead of underneath it? While I'm (and I'm sure most of us are) receptive to comments in general, it would be nice to encourage others to own theirs at the top and then provide the default comment form underneath it. Just a thought...
I'll do some additional testing and report the bug to JetPack shortly.
@cleverdevil Thanks for the kind words Jonathan. I nearly used your example in the piece, but it was already clocking in around the 4,600 word/20 minute mark, so I had to let it go. I've been thinking about this issue since last November and your post a while back was part of the kick-in-the-pants that made me write up all the moving pieces together so that feed readers not aware of the possibilities could see the bigger picture.
If you remember, do manually POSSE your comment to the main article so those who come across it have the extra example!
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.
@johnjohnston Interesting that you saw my Huffduffer reply via micro.blog as I would have suspected you supported webmentions and would have seen it directly on your blog as a comment--though perhaps you did and, like me, you forgot the source once you'd gotten back to actually reply. Or from the looks of it you've finished some additional set up and have those pieces working now. From what I can see it looks like you got Brid.gy working properly!
Thanks for sharing some of your podcast recommendations. I saw your post on Castro and I'll have to take a look at it. I'd recently switched from DoubleTwist on Android to AntennaPod for it's ability to listen at faster speeds as well as the ability to jump forward/back in 30 second increments.
I'm sure I'll see you around both micro.blog, or more likely directly on your site. Cheers!
Perhaps I'm not quite reading your meaning properly, but I'm curious about the portion about your having turned off comments. I also notice your link requesting to "Comment on this at Medium". Both seemed odd to me as some of the benefit of having an indieweb site is having things set up to have better two way communication with others, while still owning the and having control and agency over the conversation.
This being said, I have, however, been considering turning off generic public (and anonymous) comments in favor of receiving comments only via webmentions. I think the fact that users who wish to comment on my content needing to post it on their own site first helps cut down on the spam and poorly thought out me-too commentary.
To some extent I think this was the tremendous value of Tumblr's not having a native commenting system. In their paradigm, to comment on something, one needed to put their commentary into their own personal stream first to be able to push the comment to the receiver's site as a secondary action. The social consequences of this are much stronger in terms of cutting back on a lot of junk, spam, and personal attacks because it becomes personally identifiable as representing themselves first and foremost (especially on their own site). Some of the problems Twitter and others have stem from users not really owning their content or their identities on those platforms which makes it much easier to become a nameless/faceless bully.
In some sense I think of it by analogy as a "Christmas tree effect". One purchases a wonderful Christmas tree and only puts up the useful and pretty decorations on it because it's what they and others who visit will see in broad view--often even publicly through their window from the street outside their home. Very few will go out of their way to buy a shabby looking tree and festoon it with dreadful ornaments as it's something ugly that not only they see constantly within their own home, but which will publicly brand them as such to friends, family, and even outsiders within their community.
Separately, thanks for the example your site provides. There are many subtleties you've got within your theme that I've been slowly working my way toward as well. I appreciate the way you've laid out and delineated the content. I also love the idea of a microcast which is something I've been contemplating for ages, but have never gotten around to actually doing. Your version and conceptualization are inspiring me to take another hard look at actually doing something.
After more than 2 years, I finally got my first spam comment on Known. Otherwise, it's been rock solid. @WithKnown + #webmentions #FTW
#40031 (Consider Adding Web Annotations to WordPress) – WordPress Trac https:/
Mostly to provide some additional resources to the conversation I'll add the following:
Web Annotation Working Group's [https:/
Prior to the WPTavern post which motivated the conversation, there was a [https:/
Keep in mind that some of the standard is geared specifically toward browsers and browser vendors, though WordPress could certainly implement some of the pieces from the CMS side.