{ "items": [ { "type": [ "h-entry" ], "properties": { "name": [ "An update to read posts for physical books" ], "category": [ "Micropub", "Quill", "read posts" ], "featured": [ { "value": "https://i0.wp.com/boffosocko.com/wp-content/uploads/2017/09/book-with-glasses.jpg?resize=825%2C510&ssl=1", "alt": "oblique view of a book on which someone has laid their black rimmed glasses" } ], "url": [ "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/" ], "syndication": [ "https://www.facebook.com/chrisaldrich/posts/10101528970353005", "http://flip.it/1Ukfez", "https://www.linkedin.com/updates?discuss=&scope=6625072&stype=M&topic=6346203821269622784&type=U&a=1UuQ", "https://chrisaldrich.tumblr.com/post/168453957542", "https://twitter.com/ChrisAldrich/status/940438136559161344", "https://www.twitter.com/chrisaldrich/status/940438136559161344", "https://chrisaldrich.wordpress.com/?p=55676232", "https://plus.google.com/+ChrisAldrich1/posts/Gs5nraLcPyr" ], "published": [ "2017-12-11T20:27:10-08:00" ], "updated": [ "2017-12-11T21:00:58-08:00" ], "content": [ { "html": "Inspired by gRegor Morrill\u2019s IndieWebCamp Austin project, I went back and took a look at some of my read posts, and particularly for books.\n

For online material, I use the Post Kinds Plugin which does a good job of adding h-cite and p-read-of (experimental) microformats classes to the data for the things I\u2019ve read.

\n

Because Post Kinds doesn\u2019t (yet?) support percentage finished or number of pages read, I generally do read posts for books by hand as notes with the relevant data. So I decided to add some better mark up to my book-specific read posts and added microformats classes of h-cite, u-url, u-read-of, p-name, p-author, h-card and dt-published. I\u2019m far from an expert on microformats, but hopefully the way I\u2019m nesting them makes sense to parsers off in the future. (Suggestions for improvement are more than welcome.)

\n

I like Gregor\u2019s idea of p-read-status for things he\u2019s posting and will have to see how I can pull that off for posts in the future (or suggest it as an addition to Post Kinds). Presently I\u2019m just adding a want to read tag, but that could be improved to better match the functionality I appreciate in silos like Goodreads. I\u2019ll also have to load up Gregor\u2019s recent modifications to Quill and test them out on my site as well. I know David Shanske has expressed interest in better aligning Quill and micropub clients to post to WordPress with Post Kinds in mind.

\n

Here\u2019s an example of the mark up of a recent read post:

\n

Read pages 381-461 to finish reading <span class=\"h-cite\"><cite><a class=\"u-url u-read-of p-name\" href=\"http://amzn.to/2zXnQDC\" target=\"_blank\" rel=\"noopener\">Origin: A Novel</a></cite> by <span class=\"p-author h-card\"><a class=\"p-name u-url\" href=\"http://danbrown.com/\">Dan Brown</a></span><time class=\"dt-published\" datetime=\"2017-10-103 00:00:00\"></time></span>

\n

It\u2019s also made me begin to feel itchy about some of my past quote posts and potentially revisiting them to add the appropriate h-cite and related mark up to them as well. (Or at least fix it moving forward.)

\n

Incidentally, my real camp project was some heavy editing work on \u201cThe Book.\u201d More on that later\u2026

", "value": "Inspired by gRegor Morrill\u2019s IndieWebCamp Austin project, I went back and took a look at some of my read posts, and particularly for books.\nFor online material, I use the Post Kinds Plugin which does a good job of adding h-cite and p-read-of (experimental) microformats classes to the data for the things I\u2019ve read.\nBecause Post Kinds doesn\u2019t (yet?) support percentage finished or number of pages read, I generally do read posts for books by hand as notes with the relevant data. So I decided to add some better mark up to my book-specific read posts and added microformats classes of h-cite, u-url, u-read-of, p-name, p-author, h-card and dt-published. I\u2019m far from an expert on microformats, but hopefully the way I\u2019m nesting them makes sense to parsers off in the future. (Suggestions for improvement are more than welcome.)\nI like Gregor\u2019s idea of p-read-status for things he\u2019s posting and will have to see how I can pull that off for posts in the future (or suggest it as an addition to Post Kinds). Presently I\u2019m just adding a want to read tag, but that could be improved to better match the functionality I appreciate in silos like Goodreads. I\u2019ll also have to load up Gregor\u2019s recent modifications to Quill and test them out on my site as well. I know David Shanske has expressed interest in better aligning Quill and micropub clients to post to WordPress with Post Kinds in mind.\nHere\u2019s an example of the mark up of a recent read post:\nRead pages 381-461 to finish reading Origin: A Novel by Dan Brown\nIt\u2019s also made me begin to feel itchy about some of my past quote posts and potentially revisiting them to add the appropriate h-cite and related mark up to them as well. (Or at least fix it moving forward.)\nIncidentally, my real camp project was some heavy editing work on \u201cThe Book.\u201d More on that later\u2026", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=96&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=96&d=identicon&r=pg", "alt": "" } ], "url": [ "https://boffosocko.com/author/chrisaldrich/" ] }, "lang": "en-US", "value": "https://boffosocko.com/author/chrisaldrich/" } ] }, "id": "post-55702323", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "name": [ "Just a note: I did not actually get around to changing the Quill micropub request. I only updated the microformats on some read posts. I will do it manually for a little bit longer just to see if any other issues pop up, then I will add it to Quill.\nFor the p-read-status, what do you think about these machine-readable values to start: to-read, reading, finished? want-to-read seems verbose to me for a machine-readable value." ], "url": [ "https://gregorlove.com/2017/12/just-a-note-i-did/" ], "published": [ "2017-12-12T10:11:00-08:00" ], "content": [ { "html": "

Just a note: I did not actually get around to changing the Quill micropub request. I only updated the microformats on some read posts. I will do it manually for a little bit longer just to see if any other issues pop up, then I will add it to Quill.
\nFor the p-read-status, what do you think about these machine-readable values to start: to-read, reading, finished? want-to-read seems verbose to me for a machine-readable value.

", "value": "Just a note: I did not actually get around to changing the Quill micropub request. I only updated the microformats on some read posts. I will do it manually for a little bit longer just to see if any other issues pop up, then I will add it to Quill.\nFor the p-read-status, what do you think about these machine-readable values to start: to-read, reading, finished? want-to-read seems verbose to me for a machine-readable value.", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "gRegor Morrill says: @ gregorlove.com" ], "photo": [ { "value": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg", "alt": "" } ] }, "lang": "en-US", "value": "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/gRegor Morrill says:\u00a0@\u00a0gregorlove.com" } ] }, "id": "div-comment-39988", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "name": [ "[duplicate]\nIndieWeb and Webmentions plugin for WordPress FTW!\nI don\u2019t think I\u2019d used it before or really seen it happening in the wild, but Khurt Williams used his website to reply to one of my posts via Webmention. I was then able to write my reply directly within the comments section of my original post and automatically Webmention his original back in return! Gone are the days of manually cutting and pasting replies so that they appear to thread correctly within WordPress!\nWithout all the jargon, we\u2019re actually using our own websites to carry on a back and forth threaded conversation in a way that completely makes sense.\nIn fact, other than that our conversation is way over the 280 character limit imposed by Twitter, the interaction was as easy and simple from a UI perspective as it it is on Twitter or even Facebook.\u00a0Hallelujah!\nThis is how the internet was meant to work!\nA hearty thanks to those who\u2019ve made this possible! It portends a sea-change in how social media works.\nThree cheers for the #IndieWeb!!!\nSyndicated copies to:\n\n\n\nAuthor: Chris Aldrich\nI'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.\n\nI\u2019m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.\nView all posts by Chris Aldrich" ], "url": [ "http://boffosocko.com/2017/12/13/finally-blog-to-blog-communication-with-simplicity/" ], "published": [ "2017-12-12T17:21:50-08:00" ], "content": [ { "html": "

[duplicate]
\nIndieWeb and Webmentions plugin for WordPress FTW!
\nI don\u2019t think I\u2019d used it before or really seen it happening in the wild, but Khurt Williams used his website to reply to one of my posts via Webmention. I was then able to write my reply directly within the comments section of my original post and automatically Webmention his original back in return! Gone are the days of manually cutting and pasting replies so that they appear to thread correctly within WordPress!
\nWithout all the jargon, we\u2019re actually using our own websites to carry on a back and forth threaded conversation in a way that completely makes sense.
\nIn fact, other than that our conversation is way over the 280 character limit imposed by Twitter, the interaction was as easy and simple from a UI perspective as it it is on Twitter or even Facebook. Hallelujah!
\nThis is how the internet was meant to work!
\nA hearty thanks to those who\u2019ve made this possible! It portends a sea-change in how social media works.
\nThree cheers for the #IndieWeb!!!
\nSyndicated copies to:
\n
\n

\n

\n

Author: Chris Aldrich

\n

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.
\n

\n

I\u2019m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
\n View all posts by Chris Aldrich

\n

\n

\n

", "value": "[duplicate]\nIndieWeb and Webmentions plugin for WordPress FTW!\nI don\u2019t think I\u2019d used it before or really seen it happening in the wild, but Khurt Williams used his website to reply to one of my posts via Webmention. I was then able to write my reply directly within the comments section of my original post and automatically Webmention his original back in return! Gone are the days of manually cutting and pasting replies so that they appear to thread correctly within WordPress!\nWithout all the jargon, we\u2019re actually using our own websites to carry on a back and forth threaded conversation in a way that completely makes sense.\nIn fact, other than that our conversation is way over the 280 character limit imposed by Twitter, the interaction was as easy and simple from a UI perspective as it it is on Twitter or even Facebook.\u00a0Hallelujah!\nThis is how the internet was meant to work!\nA hearty thanks to those who\u2019ve made this possible! It portends a sea-change in how social media works.\nThree cheers for the #IndieWeb!!!\nSyndicated copies to:\n\n\n\nAuthor: Chris Aldrich\nI'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.\n\nI\u2019m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.\nView all posts by Chris Aldrich", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich says: @ boffosocko.com" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=64&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" } ] }, "lang": "en-US", "value": "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/Chris Aldrich says:\u00a0@\u00a0boffosocko.com" } ] }, "id": "div-comment-40027", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "name": [ "IndieWeb and Webmentions plugin for WordPress FTW!\nI don\u2019t think I\u2019d used it before or really seen it happening in the wild, but Khurt Williams used his website to reply to one of my posts via Webmention. I was then able to write my reply directly within the comments section of my original post and automatically Webmention his original back in return! Gone are the days of manually cutting and pasting replies so that they appear to thread correctly within WordPress!\nWithout all the jargon, we\u2019re actually using our own websites to carry on a back and forth threaded conversation in a way that completely makes sense.\nIn fact, other than that our conversation is way over the 280 character limit imposed by Twitter, the interaction was as easy and simple from a UI perspective as it it is on Twitter or even Facebook.\u00a0Hallelujah!\nThis is how the internet was meant to work!\nA hearty thanks to those who\u2019ve made this possible! It portends a sea-change in how social media works.\nThree cheers for the #IndieWeb!!!\nSyndicated copies to:\n\n\n\nAuthor: Chris Aldrich\nI'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.\n\nI\u2019m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.\nView all posts by Chris Aldrich" ], "url": [ "http://boffosocko.com/2017/12/13/finally-blog-to-blog-communication-with-simplicity/" ], "published": [ "2017-12-12T17:21:50-08:00" ], "content": [ { "html": "

IndieWeb and Webmentions plugin for WordPress FTW!
\nI don\u2019t think I\u2019d used it before or really seen it happening in the wild, but Khurt Williams used his website to reply to one of my posts via Webmention. I was then able to write my reply directly within the comments section of my original post and automatically Webmention his original back in return! Gone are the days of manually cutting and pasting replies so that they appear to thread correctly within WordPress!
\nWithout all the jargon, we\u2019re actually using our own websites to carry on a back and forth threaded conversation in a way that completely makes sense.
\nIn fact, other than that our conversation is way over the 280 character limit imposed by Twitter, the interaction was as easy and simple from a UI perspective as it it is on Twitter or even Facebook. Hallelujah!
\nThis is how the internet was meant to work!
\nA hearty thanks to those who\u2019ve made this possible! It portends a sea-change in how social media works.
\nThree cheers for the #IndieWeb!!!
\nSyndicated copies to:
\n
\n

\n

\n

Author: Chris Aldrich

\n

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.
\n

\n

I\u2019m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
\n View all posts by Chris Aldrich

\n

\n

\n

", "value": "IndieWeb and Webmentions plugin for WordPress FTW!\nI don\u2019t think I\u2019d used it before or really seen it happening in the wild, but Khurt Williams used his website to reply to one of my posts via Webmention. I was then able to write my reply directly within the comments section of my original post and automatically Webmention his original back in return! Gone are the days of manually cutting and pasting replies so that they appear to thread correctly within WordPress!\nWithout all the jargon, we\u2019re actually using our own websites to carry on a back and forth threaded conversation in a way that completely makes sense.\nIn fact, other than that our conversation is way over the 280 character limit imposed by Twitter, the interaction was as easy and simple from a UI perspective as it it is on Twitter or even Facebook.\u00a0Hallelujah!\nThis is how the internet was meant to work!\nA hearty thanks to those who\u2019ve made this possible! It portends a sea-change in how social media works.\nThree cheers for the #IndieWeb!!!\nSyndicated copies to:\n\n\n\nAuthor: Chris Aldrich\nI'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.\n\nI\u2019m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.\nView all posts by Chris Aldrich", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich says: @ boffosocko.com" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=64&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" } ] }, "lang": "en-US", "value": "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/Chris Aldrich says:\u00a0@\u00a0boffosocko.com" } ] }, "id": "div-comment-40028", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "name": [ "Publishing read posts is still pretty new, so there\u2019s a lot of experimenting and some more manual steps currently. That\u2019s definitely not the end goal,\u2026\nSyndicated copies: X" ], "url": [ "https://gregorlove.com/2017/12/publishing-read-posts-is-still/" ], "syndication": [ "https://twitter.com/khurtwilliams/status/940780250383966208" ], "published": [ "2017-12-12T22:41:00-08:00" ], "content": [ { "html": "

Publishing read posts is still pretty new, so there\u2019s a lot of experimenting and some more manual steps currently. That\u2019s definitely not the end goal,\u2026

\n

Syndicated copies:

\n", "value": "Publishing read posts is still pretty new, so there\u2019s a lot of experimenting and some more manual steps currently. That\u2019s definitely not the end goal,\u2026\nSyndicated copies: X", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "gRegor Morrill says: @ gregorlove.com says: @ gregorlove.com" ], "photo": [ { "value": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg", "alt": "" } ] }, "lang": "en-US", "value": "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/gRegor Morrill says: @ gregorlove.com says:\u00a0@\u00a0gregorlove.com" } ] }, "id": "div-comment-40013", "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Kh\u00fcrt Williams" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/7fa94585b903e6e183d6164b16b1b573?s=84&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/7fa94585b903e6e183d6164b16b1b573?s=84&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" } ], "url": [ "https://islandinthenet.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Kh\u00fcrt Williams" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/7fa94585b903e6e183d6164b16b1b573?s=64&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/7fa94585b903e6e183d6164b16b1b573?s=64&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" } ], "url": [ "https://islandinthenet.com" ] }, "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "name": [ "\u201cDon\u2019t let your ideas take over the things you enjoy. Some ideas can be beneficial, others are passing experiments.\u201d" ], "url": [ "https://islandinthenet.com/focus-content/" ], "published": [ "2017-12-15T11:53:46-08:00" ], "content": [ { "html": "

\u201cDon\u2019t let your ideas take over the things you enjoy. Some ideas can be beneficial, others are passing experiments.\u201d

", "value": "\u201cDon\u2019t let your ideas take over the things you enjoy. Some ideas can be beneficial, others are passing experiments.\u201d", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Kh\u00fcrt Williams says: @ islandinthenet.com" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/7fa94585b903e6e183d6164b16b1b573?s=64&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" } ] }, "lang": "en-US", "value": "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/Kh\u00fcrt Williams says:\u00a0@\u00a0islandinthenet.com" } ] }, "id": "div-comment-40181", "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Kh\u00fcrt Williams" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/7fa94585b903e6e183d6164b16b1b573?s=100&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/7fa94585b903e6e183d6164b16b1b573?s=100&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" } ], "url": [ "https://islandinthenet.com" ] }, "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "name": [ "This just gave me an idea\u2026\nhttps://github.com/dshanske/indieweb-post-kinds/issues/134\n\u00a0" ], "url": [ "https://david.shanske.com/2017/12/13/update-read-posts-physical-books/" ], "published": [ "2017-12-13T17:53:43-08:00" ], "content": [ { "html": "

This just gave me an idea\u2026
\nhttps://github.com/dshanske/indieweb-post-kinds/issues/134
\n

", "value": "This just gave me an idea\u2026\nhttps://github.com/dshanske/indieweb-post-kinds/issues/134\n\u00a0", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "David Shanske says: @ david.shanske.com" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/681eba02e72ba1d894097034a8110e61?s=125&d=default&r=g", "alt": "" } ] }, "lang": "en-US", "value": "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/David Shanske says:\u00a0@\u00a0david.shanske.com" } ] }, "id": "div-comment-40152", "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" }, { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=56&d=identicon&r=pg", "alt": "" } ], "url": [ "http://www.boffosocko.com" ] }, "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "name": [ "Introduction to what one would consider basic web communication\nA few days ago I had written a post on my website and a colleague had written a reply on his own website. Because we were both using the W3C Webmention specification on our websites, my site received the notification of his response and displayed it in the comments section of my website. (This in and of itself is really magic enough\u2013cross website @mentions!)\nTo reply back to him I previously would have written a separate second post on my site in turn to reply to his, thereby fragmenting the conversation across multiple posts and making it harder to follow the conversation. (This is somewhat similar to what Medium.com does with their commenting system as each reply/comment is its own standalone page.)\nInstead, I\u2019ve now been able to configure my website to allow me to write a reply directly to a response within my comments section admin UI (or even in the comments section of the original page itself), publish it, and have the comment be sent to his reply and display it there. Two copies for the price of one!\nFrom the comments list in my Admin UI, I can write a reply and it not only lives on my site but it can now be sent as a comment to the site that made the original comment! As an example, here\u2019s my first one and the resultant copy on the site I was replying to.This means that now, WordPress-based websites (at least self-hosted versions running the WordPress.org code) can easily and simply allow multiple parties to write posts on their own sites and participate in multi-sided conversations back and forth while all parties maintain copies of all sides of the conversation on their own websites in a way that maintains all of the context. As a result, if one site should be shut down or disappear, the remaining websites will still have a fully archived copy of the entire conversation thread. (Let\u2019s hear it for the resilience of the web!)\nWhat is happening?\nThis functionality is seemingly so simple that one is left wondering:\n\u201cWhy wasn\u2019t this baked into WordPress (and the rest of the web) from the start?\u201d\n\u201cWhy wasn\u2019t this built after the rise of Twitter, Facebook, or other websites which do this as a basic function?\u201d\n\u201cHow can I get it tout suite?!\u201d (aka gimme, gimme, gimme, and right now!!!)\nWhile seeming simple, the technical hurdles aren\u2019t necessarily because there had previously never been a universal protocol for the web to allow it. (The Webmentions spec now makes it possible.) Sites like Facebook, Twitter, and others enable it because they\u2019ve got a highly closed and highly customized environment that makes it a simpler problem to solve. In fact, even old-school web-based bulletin boards allowed this!\nBut even within social media one will immediately notice that you can\u2019t use your Facebook account to reply to a Twitter account. And why not?! (While the web would be far better if one website or page could talk to another, these sites don\u2019t for the simple economic reason that they want you using only their site and not others, and not enabling this functionality keeps you locked into what they\u2019re selling.)\nI\u2019ll detail the basic set up below, but thought that it would be highly illustrative to have a diagram of what\u2019s physically happening in case the description above seems a bit confusing to picture properly. I\u2019ll depict two websites, each in their own column and color-coded so that content from site A is one color while content from site B is another color.\nA diagram of where comments live when sent via webmention.\nEach site composes and owns its own content and sends the replies to the other site.It really seems nearly incomprehensible to me how this hasn\u2019t been built into the core functionality of the web from the beginning of at least the blogosphere. Yet here we are, and somehow I\u2019m demonstrating how to do this from one WordPress site to another via the open web in 2017. To me this is the entire difference between a true Internet and just using someone else\u2019s intranet.\nImplementation\nPrerequisites\nWhile this general functionality is doable on any website, I\u2019ll stick to enabling it specifically on WordPress, a content management system that is powering roughly 30% of all websites on the internet. You\u2019ll naturally need your own self-hosted WordPress-based website with a few custom plugins and a modern semantic-based theme. (Those interested in setting it up on other platforms are more than welcome to explore the resources of the IndieWeb wiki and their chat which has a wealth of resources.)\nPlugins\nAs a minimum set you\u2019ll want to have the following list of plugins enabled and configured:\nWebmentions\nSemantic Linkbacks\nIndieWeb Plugin (optional)\nOther instructions and help for setting these up and configuring them can be found on the IndieWeb wiki, though not all of the steps there are necessarily required for this functionality.\nThemes\nIdeally this all should function regardless of the theme you have chosen, but WordPress only provides the most basic support for microformats version 1 and doesn\u2019t support the more modern version 2 out of the box. As a result, the display of comments from site to site may be a bit wonky depending on how supportive your particular theme is of the microformats standards. As you can see I\u2019m using a relatively standard version of the TwentySixteen theme without a lot of customization and getting some reasonable results. If you have a choice, I\u2019d recommend one of the following specific themes which have solid semantic markup:\nSempress\nZenPress\nIndependent Publisher\nPlugin\nThe final plugin that enables sending comments from one comment section to another is the WordPress Webmention for Comments plugin. As it is still somewhat experimental and is not available in the WordPress repository, you\u2019ll need to download it from GitHub and activate it. That\u2019s it! There aren\u2019t any settings or anything else to configure.\nUse\nWith the plugin installed, you should now be able to send comments and replies to replies directly within your comments admin UI (or directly within your comments section in individual pages, though this can not require additional clicks to get there, but you also don\u2019t have the benefit of the admin editor either).\nThere is one current caveat however. For the plugin to actually send the webmention properly, it will need to have a URL in your reply that includes the microformats u-in-reply-to class. Currently you\u2019ll need to do this manually until the plugin can properly parse and target the fragmentions for the comments properly. I hope the functionality can be added to the plugin to make the experience seamless in the future.\nSo what does this u-in-reply-to part actually look like? Here\u2019s an example of the one I used to send my reply:\nKh\u00fcrt\nThe class tells the receiving site that the webmention is a reply and to display it as such and the URL is necessary for your webmention plugin to know where to send the notification. You\u2019d simply need to change the URL and the word (or words) that appear between the anchor tags.\nIf you want to have a hidden link and still send a webmention you could potentially add your link to a zero width space as well. This would look like the following:\n&\u200b#8203;\u200b\nBased on my experiments, using a via HTML will work, but it will send it as a plain webmention to the site and it won\u2019t show up natively as a reply.\nSadly, a plain text reply doesn\u2019t work (yet), but hopefully some simple changes could be made to force it to using the common fragmentions pattern that WordPress uses for replies.\nInterestingly this capability has been around for a while, it just hasn\u2019t been well documented or described. I hope now that those with WordPress sites that already support Webmentions will have a better idea what this plugin is doing and how works.\nFuture\nEventually one might expect that all the bugs in the system get worked out and the sub-plugin for sending comment Webmentions will be rolled up into the main Webmentions plugin, which incidentally handles fragmentions already.\nCaveats\nIn addition to the notes above, I will say that this is still technically experimental code not running on many websites, so its functionality may not be exact or perfect in actual use, though in experimenting with it I have found it to be very stable. I would recommend checking that the replies actually post to the receiving site, which incidentally must be able to accept webmentions. If the receiving website doesn\u2019t have webmention support, one will need to manually cut and paste the content there (and likely check the receive notification of replies via email, so you can stay apprised of future replies).\nYou can check the receiving site\u2019s webmention support in most browsers by right clicking and viewing the pages source. Within the source one should see code in the section of the page which indicates there is a webmention endpoint. Here is an example of the code typically injected into WordPress websites that you\u2019d be looking for:\n\n\nAlso keep in mind that some users moderate their comments, so that even though your mention was sent, they may need to approve it prior to it displaying on the page.\nIf you do notice problems or issues or have quirks, please file the issue with as full a description of what you did and what resulted as you can so that it can be troubleshot and made to work not only for you, but hopefully work better for everyone else.\nGive it a try\nSo you\u2019ve implemented everything above? Go ahead and write a reply on your own WordPress website and send me a webmention! I\u2019ll do my best to reply directly to you so you can send another reply to make sure you\u2019ve got things working properly.\nOnce you\u2019re set, go forward and continue helping to make the web a better place.\nSpecial Thanks\nI wanted to take a moment to give special thanks to Aaron Parecki, Matthias Pfefferle, and David Shanske who have done most of the Herculean work to get this and related functionality working. And thanks also to all who make up the IndieWeb community that are pushing the boundaries of what the web is and what it can accomplish. And finally, thanks to Kh\u00fcrt Williams who became the unwitting guinea pig for my first attempt at this. Thank you all!\n\u200b\u200b\u200b\u200b\u200b\u200b\nSyndicated copies to:\n\n\n\n\nAuthor: Chris Aldrich\nI'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.\n\nI\u2019m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.\nView all posts by Chris Aldrich\n\n\n\nSyndicated copies:\n\nMedium WordPress X" ], "url": [ "http://boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/" ], "syndication": [ "https://news.indieweb.org/en/boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/", "https://medium.com/@chrisaldrich/threaded-replies-and-comments-with-webmentions-in-wordpress-cf6f6bbc375", "https://chrisaldrich.wordpress.com/?p=55676257", "https://twitter.com/ChrisAldrich/status/941787443879075840" ], "published": [ "2017-12-15T05:48:26-08:00" ], "content": [ { "html": "

Introduction to what one would consider basic web communication
\nA few days ago I had written a post on my website and a colleague had written a reply on his own website. Because we were both using the W3C Webmention specification on our websites, my site received the notification of his response and displayed it in the comments section of my website. (This in and of itself is really magic enough\u2013cross website @mentions!)
\nTo reply back to him I previously would have written a separate second post on my site in turn to reply to his, thereby fragmenting the conversation across multiple posts and making it harder to follow the conversation. (This is somewhat similar to what Medium.com does with their commenting system as each reply/comment is its own standalone page.)
\nInstead, I\u2019ve now been able to configure my website to allow me to write a reply directly to a response within my comments section admin UI (or even in the comments section of the original page itself), publish it, and have the comment be sent to his reply and display it there. Two copies for the price of one!
\nFrom the comments list in my Admin UI, I can write a reply and it not only lives on my site but it can now be sent as a comment to the site that made the original comment! As an example, here\u2019s my first one and the resultant copy on the site I was replying to.This means that now, WordPress-based websites (at least self-hosted versions running the WordPress.org code) can easily and simply allow multiple parties to write posts on their own sites and participate in multi-sided conversations back and forth while all parties maintain copies of all sides of the conversation on their own websites in a way that maintains all of the context. As a result, if one site should be shut down or disappear, the remaining websites will still have a fully archived copy of the entire conversation thread. (Let\u2019s hear it for the resilience of the web!)
\nWhat is happening?
\nThis functionality is seemingly so simple that one is left wondering:

\n

\u201cWhy wasn\u2019t this baked into WordPress (and the rest of the web) from the start?\u201d
\n\u201cWhy wasn\u2019t this built after the rise of Twitter, Facebook, or other websites which do this as a basic function?\u201d
\n\u201cHow can I get it tout suite?!\u201d (aka gimme, gimme, gimme, and right now!!!)

\n

While seeming simple, the technical hurdles aren\u2019t necessarily because there had previously never been a universal protocol for the web to allow it. (The Webmentions spec now makes it possible.) Sites like Facebook, Twitter, and others enable it because they\u2019ve got a highly closed and highly customized environment that makes it a simpler problem to solve. In fact, even old-school web-based bulletin boards allowed this!
\nBut even within social media one will immediately notice that you can\u2019t use your Facebook account to reply to a Twitter account. And why not?! (While the web would be far better if one website or page could talk to another, these sites don\u2019t for the simple economic reason that they want you using only their site and not others, and not enabling this functionality keeps you locked into what they\u2019re selling.)
\nI\u2019ll detail the basic set up below, but thought that it would be highly illustrative to have a diagram of what\u2019s physically happening in case the description above seems a bit confusing to picture properly. I\u2019ll depict two websites, each in their own column and color-coded so that content from site A is one color while content from site B is another color.
\nA diagram of where comments live when sent via webmention.
\n Each site composes and owns its own content and sends the replies to the other site.It really seems nearly incomprehensible to me how this hasn\u2019t been built into the core functionality of the web from the beginning of at least the blogosphere. Yet here we are, and somehow I\u2019m demonstrating how to do this from one WordPress site to another via the open web in 2017. To me this is the entire difference between a true Internet and just using someone else\u2019s intranet.
\nImplementation
\nPrerequisites
\nWhile this general functionality is doable on any website, I\u2019ll stick to enabling it specifically on WordPress, a content management system that is powering roughly 30% of all websites on the internet. You\u2019ll naturally need your own self-hosted WordPress-based website with a few custom plugins and a modern semantic-based theme. (Those interested in setting it up on other platforms are more than welcome to explore the resources of the IndieWeb wiki and their chat which has a wealth of resources.)
\nPlugins
\nAs a minimum set you\u2019ll want to have the following list of plugins enabled and configured:

\n

Webmentions
\nSemantic Linkbacks

\n

IndieWeb Plugin (optional)

\n

Other instructions and help for setting these up and configuring them can be found on the IndieWeb wiki, though not all of the steps there are necessarily required for this functionality.
\nThemes
\nIdeally this all should function regardless of the theme you have chosen, but WordPress only provides the most basic support for microformats version 1 and doesn\u2019t support the more modern version 2 out of the box. As a result, the display of comments from site to site may be a bit wonky depending on how supportive your particular theme is of the microformats standards. As you can see I\u2019m using a relatively standard version of the TwentySixteen theme without a lot of customization and getting some reasonable results. If you have a choice, I\u2019d recommend one of the following specific themes which have solid semantic markup:

\n

Sempress
\nZenPress
\nIndependent Publisher

\n

Plugin
\nThe final plugin that enables sending comments from one comment section to another is the WordPress Webmention for Comments plugin. As it is still somewhat experimental and is not available in the WordPress repository, you\u2019ll need to download it from GitHub and activate it. That\u2019s it! There aren\u2019t any settings or anything else to configure.
\nUse
\nWith the plugin installed, you should now be able to send comments and replies to replies directly within your comments admin UI (or directly within your comments section in individual pages, though this can not require additional clicks to get there, but you also don\u2019t have the benefit of the admin editor either).
\nThere is one current caveat however. For the plugin to actually send the webmention properly, it will need to have a URL in your reply that includes the microformats u-in-reply-to class. Currently you\u2019ll need to do this manually until the plugin can properly parse and target the fragmentions for the comments properly. I hope the functionality can be added to the plugin to make the experience seamless in the future.
\nSo what does this u-in-reply-to part actually look like? Here\u2019s an example of the one I used to send my reply:
\n<a class=\"u-in-reply-to\" href=\"https://islandinthenet.com/manually-adding-microfomats-markup/\">Kh\u00fcrt</a>
\nThe class tells the receiving site that the webmention is a reply and to display it as such and the URL is necessary for your webmention plugin to know where to send the notification. You\u2019d simply need to change the URL and the word (or words) that appear between the anchor tags.
\nIf you want to have a hidden link and still send a webmention you could potentially add your link to a zero width space as well. This would look like the following:
\n<a class=\"u-in-reply-to\" href=\"http://www.example.com\">&\u200b#8203;\u200b</a>
\nBased on my experiments, using a <link> via HTML will work, but it will send it as a plain webmention to the site and it won\u2019t show up natively as a reply.
\nSadly, a plain text reply doesn\u2019t work (yet), but hopefully some simple changes could be made to force it to using the common fragmentions pattern that WordPress uses for replies.
\nInterestingly this capability has been around for a while, it just hasn\u2019t been well documented or described. I hope now that those with WordPress sites that already support Webmentions will have a better idea what this plugin is doing and how works.
\nFuture
\nEventually one might expect that all the bugs in the system get worked out and the sub-plugin for sending comment Webmentions will be rolled up into the main Webmentions plugin, which incidentally handles fragmentions already.
\nCaveats
\nIn addition to the notes above, I will say that this is still technically experimental code not running on many websites, so its functionality may not be exact or perfect in actual use, though in experimenting with it I have found it to be very stable. I would recommend checking that the replies actually post to the receiving site, which incidentally must be able to accept webmentions. If the receiving website doesn\u2019t have webmention support, one will need to manually cut and paste the content there (and likely check the receive notification of replies via email, so you can stay apprised of future replies).
\nYou can check the receiving site\u2019s webmention support in most browsers by right clicking and viewing the pages source. Within the source one should see code in the <head> section of the page which indicates there is a webmention endpoint. Here is an example of the code typically injected into WordPress websites that you\u2019d be looking for:
\n<link rel=\"webmention\" href=\"http://example.com/wp-json/webmention/1.0/endpoint\" />
\n<link rel=\"http://webmention.org/\" href=\"http://example.com/wp-json/webmention/1.0/endpoint\" />
\nAlso keep in mind that some users moderate their comments, so that even though your mention was sent, they may need to approve it prior to it displaying on the page.
\nIf you do notice problems or issues or have quirks, please file the issue with as full a description of what you did and what resulted as you can so that it can be troubleshot and made to work not only for you, but hopefully work better for everyone else.
\nGive it a try
\nSo you\u2019ve implemented everything above? Go ahead and write a reply on your own WordPress website and send me a webmention! I\u2019ll do my best to reply directly to you so you can send another reply to make sure you\u2019ve got things working properly.
\nOnce you\u2019re set, go forward and continue helping to make the web a better place.
\nSpecial Thanks
\nI wanted to take a moment to give special thanks to Aaron Parecki, Matthias Pfefferle, and David Shanske who have done most of the Herculean work to get this and related functionality working. And thanks also to all who make up the IndieWeb community that are pushing the boundaries of what the web is and what it can accomplish. And finally, thanks to Kh\u00fcrt Williams who became the unwitting guinea pig for my first attempt at this. Thank you all!
\n\u200b\u200b\u200b\u200b\u200b\u200b
\nSyndicated copies to:
\n
\n
\n

\n

\n

Author: Chris Aldrich

\n

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.
\n

\n

I\u2019m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
\n View all posts by Chris Aldrich

\n

\n

\n

\n

Syndicated copies:

\n", "value": "Introduction to what one would consider basic web communication\nA few days ago I had written a post on my website and a colleague had written a reply on his own website. Because we were both using the W3C Webmention specification on our websites, my site received the notification of his response and displayed it in the comments section of my website. (This in and of itself is really magic enough\u2013cross website @mentions!)\nTo reply back to him I previously would have written a separate second post on my site in turn to reply to his, thereby fragmenting the conversation across multiple posts and making it harder to follow the conversation. (This is somewhat similar to what Medium.com does with their commenting system as each reply/comment is its own standalone page.)\nInstead, I\u2019ve now been able to configure my website to allow me to write a reply directly to a response within my comments section admin UI (or even in the comments section of the original page itself), publish it, and have the comment be sent to his reply and display it there. Two copies for the price of one!\nFrom the comments list in my Admin UI, I can write a reply and it not only lives on my site but it can now be sent as a comment to the site that made the original comment! As an example, here\u2019s my first one and the resultant copy on the site I was replying to.This means that now, WordPress-based websites (at least self-hosted versions running the WordPress.org code) can easily and simply allow multiple parties to write posts on their own sites and participate in multi-sided conversations back and forth while all parties maintain copies of all sides of the conversation on their own websites in a way that maintains all of the context. As a result, if one site should be shut down or disappear, the remaining websites will still have a fully archived copy of the entire conversation thread. (Let\u2019s hear it for the resilience of the web!)\nWhat is happening?\nThis functionality is seemingly so simple that one is left wondering:\n\u201cWhy wasn\u2019t this baked into WordPress (and the rest of the web) from the start?\u201d\n\u201cWhy wasn\u2019t this built after the rise of Twitter, Facebook, or other websites which do this as a basic function?\u201d\n\u201cHow can I get it tout suite?!\u201d (aka gimme, gimme, gimme, and right now!!!)\nWhile seeming simple, the technical hurdles aren\u2019t necessarily because there had previously never been a universal protocol for the web to allow it. (The Webmentions spec now makes it possible.) Sites like Facebook, Twitter, and others enable it because they\u2019ve got a highly closed and highly customized environment that makes it a simpler problem to solve. In fact, even old-school web-based bulletin boards allowed this!\nBut even within social media one will immediately notice that you can\u2019t use your Facebook account to reply to a Twitter account. And why not?! (While the web would be far better if one website or page could talk to another, these sites don\u2019t for the simple economic reason that they want you using only their site and not others, and not enabling this functionality keeps you locked into what they\u2019re selling.)\nI\u2019ll detail the basic set up below, but thought that it would be highly illustrative to have a diagram of what\u2019s physically happening in case the description above seems a bit confusing to picture properly. I\u2019ll depict two websites, each in their own column and color-coded so that content from site A is one color while content from site B is another color.\nA diagram of where comments live when sent via webmention.\nEach site composes and owns its own content and sends the replies to the other site.It really seems nearly incomprehensible to me how this hasn\u2019t been built into the core functionality of the web from the beginning of at least the blogosphere. Yet here we are, and somehow I\u2019m demonstrating how to do this from one WordPress site to another via the open web in 2017. To me this is the entire difference between a true Internet and just using someone else\u2019s intranet.\nImplementation\nPrerequisites\nWhile this general functionality is doable on any website, I\u2019ll stick to enabling it specifically on WordPress, a content management system that is powering roughly 30% of all websites on the internet. You\u2019ll naturally need your own self-hosted WordPress-based website with a few custom plugins and a modern semantic-based theme. (Those interested in setting it up on other platforms are more than welcome to explore the resources of the IndieWeb wiki and their chat which has a wealth of resources.)\nPlugins\nAs a minimum set you\u2019ll want to have the following list of plugins enabled and configured:\nWebmentions\nSemantic Linkbacks\nIndieWeb Plugin (optional)\nOther instructions and help for setting these up and configuring them can be found on the IndieWeb wiki, though not all of the steps there are necessarily required for this functionality.\nThemes\nIdeally this all should function regardless of the theme you have chosen, but WordPress only provides the most basic support for microformats version 1 and doesn\u2019t support the more modern version 2 out of the box. As a result, the display of comments from site to site may be a bit wonky depending on how supportive your particular theme is of the microformats standards. As you can see I\u2019m using a relatively standard version of the TwentySixteen theme without a lot of customization and getting some reasonable results. If you have a choice, I\u2019d recommend one of the following specific themes which have solid semantic markup:\nSempress\nZenPress\nIndependent Publisher\nPlugin\nThe final plugin that enables sending comments from one comment section to another is the WordPress Webmention for Comments plugin. As it is still somewhat experimental and is not available in the WordPress repository, you\u2019ll need to download it from GitHub and activate it. That\u2019s it! There aren\u2019t any settings or anything else to configure.\nUse\nWith the plugin installed, you should now be able to send comments and replies to replies directly within your comments admin UI (or directly within your comments section in individual pages, though this can not require additional clicks to get there, but you also don\u2019t have the benefit of the admin editor either).\nThere is one current caveat however. For the plugin to actually send the webmention properly, it will need to have a URL in your reply that includes the microformats u-in-reply-to class. Currently you\u2019ll need to do this manually until the plugin can properly parse and target the fragmentions for the comments properly. I hope the functionality can be added to the plugin to make the experience seamless in the future.\nSo what does this u-in-reply-to part actually look like? Here\u2019s an example of the one I used to send my reply:\nKh\u00fcrt\nThe class tells the receiving site that the webmention is a reply and to display it as such and the URL is necessary for your webmention plugin to know where to send the notification. You\u2019d simply need to change the URL and the word (or words) that appear between the anchor tags.\nIf you want to have a hidden link and still send a webmention you could potentially add your link to a zero width space as well. This would look like the following:\n&\u200b#8203;\u200b\nBased on my experiments, using a via HTML will work, but it will send it as a plain webmention to the site and it won\u2019t show up natively as a reply.\nSadly, a plain text reply doesn\u2019t work (yet), but hopefully some simple changes could be made to force it to using the common fragmentions pattern that WordPress uses for replies.\nInterestingly this capability has been around for a while, it just hasn\u2019t been well documented or described. I hope now that those with WordPress sites that already support Webmentions will have a better idea what this plugin is doing and how works.\nFuture\nEventually one might expect that all the bugs in the system get worked out and the sub-plugin for sending comment Webmentions will be rolled up into the main Webmentions plugin, which incidentally handles fragmentions already.\nCaveats\nIn addition to the notes above, I will say that this is still technically experimental code not running on many websites, so its functionality may not be exact or perfect in actual use, though in experimenting with it I have found it to be very stable. I would recommend checking that the replies actually post to the receiving site, which incidentally must be able to accept webmentions. If the receiving website doesn\u2019t have webmention support, one will need to manually cut and paste the content there (and likely check the receive notification of replies via email, so you can stay apprised of future replies).\nYou can check the receiving site\u2019s webmention support in most browsers by right clicking and viewing the pages source. Within the source one should see code in the section of the page which indicates there is a webmention endpoint. Here is an example of the code typically injected into WordPress websites that you\u2019d be looking for:\n\n\nAlso keep in mind that some users moderate their comments, so that even though your mention was sent, they may need to approve it prior to it displaying on the page.\nIf you do notice problems or issues or have quirks, please file the issue with as full a description of what you did and what resulted as you can so that it can be troubleshot and made to work not only for you, but hopefully work better for everyone else.\nGive it a try\nSo you\u2019ve implemented everything above? Go ahead and write a reply on your own WordPress website and send me a webmention! I\u2019ll do my best to reply directly to you so you can send another reply to make sure you\u2019ve got things working properly.\nOnce you\u2019re set, go forward and continue helping to make the web a better place.\nSpecial Thanks\nI wanted to take a moment to give special thanks to Aaron Parecki, Matthias Pfefferle, and David Shanske who have done most of the Herculean work to get this and related functionality working. And thanks also to all who make up the IndieWeb community that are pushing the boundaries of what the web is and what it can accomplish. And finally, thanks to Kh\u00fcrt Williams who became the unwitting guinea pig for my first attempt at this. Thank you all!\n\u200b\u200b\u200b\u200b\u200b\u200b\nSyndicated copies to:\n\n\n\n\nAuthor: Chris Aldrich\nI'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.\n\nI\u2019m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.\nView all posts by Chris Aldrich\n\n\n\nSyndicated copies:\n\nMedium WordPress X", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich says: @ boffosocko.com" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=64&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" } ] }, "lang": "en-US", "value": "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/Chris Aldrich says:\u00a0@\u00a0boffosocko.com" } ] }, "id": "div-comment-40213", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "name": [ "Introduction to what one would consider basic web communication\nA few days ago I had written a post on my website and a colleague had written a reply on his own website. Because we were both using the W3C Webmention specification on our websites, my site received the notification of his response and displayed it in the comments section of my website. (This in and of itself is really magic enough\u2013cross website @mentions!)\nTo reply back to him I previously would have written a separate second post on my site in turn to reply to his, thereby fragmenting the conversation across multiple posts and making it harder to follow the conversation. (This is somewhat similar to what Medium.com does with their commenting system as each reply/comment is its own standalone page.)\nInstead, I\u2019ve now been able to configure my website to allow me to write a reply directly to a response within my comments section admin UI (or even in the comments section of the original page itself), publish it, and have the comment be sent to his reply and display it there. Two copies for the price of one!\nFrom the comments list in my Admin UI, I can write a reply and it not only lives on my site but it can now be sent as a comment to the site that made the original comment! As an example, here\u2019s my first one and the resultant copy on the site I was replying to.\nThis means that now, WordPress-based websites (at least self-hosted versions running the WordPress.org code) can easily and simply allow multiple parties to write posts on their own sites and participate in multi-sided conversations back and forth while all parties maintain copies of all sides of the conversation on their own websites in a way that maintains all of the context. As a result, if one site should be shut down or disappear, the remaining websites will still have a fully archived copy of the entire conversation thread. (Let\u2019s hear it for the resilience of the web!)\nWhat is happening?\nThis functionality is seemingly so simple that one is left wondering:\n\u201cWhy wasn\u2019t this baked into WordPress (and the rest of the web) from the start?\u201d\n\u201cWhy wasn\u2019t this built after the rise of Twitter, Facebook, or other websites which do this as a basic function?\u201d\n\u201cHow can I get it tout suite?!\u201d (aka gimme, gimme, gimme, and right now!!!)\nWhile seeming simple, the technical hurdles aren\u2019t necessarily because there had previously never been a universal protocol for the web to allow it. (The Webmentions spec now makes it possible.) Sites like Facebook, Twitter, and others enable it because they\u2019ve got a highly closed and highly customized environment that makes it a simpler problem to solve. In fact, even old-school web-based bulletin boards allowed this!\nBut even within social media one will immediately notice that you can\u2019t use your Facebook account to reply to a Twitter account. And why not?! (While the web would be far better if one website or page could talk to another, these sites don\u2019t for the simple economic reason that they want you using only their site and not others, and not enabling this functionality keeps you locked into what they\u2019re selling.)\nI\u2019ll detail the basic set up below, but thought that it would be highly illustrative to have a diagram of what\u2019s physically happening in case the description above seems a bit confusing to picture properly. I\u2019ll depict two websites, each in their own column and color-coded so that content from site A is one color while content from site B is another color.\nA diagram of where comments live when sent via webmention.\nEach site composes and owns its own content and sends the replies to the other site.\nIt really seems nearly incomprehensible to me how this hasn\u2019t been built into the core functionality of the web from the beginning of at least the blogosphere. Yet here we are, and somehow I\u2019m demonstrating how to do this from one WordPress site to another via the open web in 2017. To me this is the entire difference between a true Internet and just using someone else\u2019s intranet.\nImplementation\nPrerequisites\nWhile this general functionality is doable on any website, I\u2019ll stick to enabling it specifically on WordPress, a content management system that is powering roughly 30% of all websites on the internet. You\u2019ll naturally need your own self-hosted WordPress-based website with a few custom plugins and a modern semantic-based theme. (Those interested in setting it up on other platforms are more than welcome to explore the resources of the IndieWeb wiki and their chat which has a wealth of resources.)\nPlugins\nAs a minimum set you\u2019ll want to have the following list of plugins enabled and configured:\nWebmentions\nSemantic Linkbacks\nIndieWeb Plugin (optional)\nOther instructions and help for setting these up and configuring them can be found on the IndieWeb wiki, though not all of the steps there are necessarily required for this functionality.\nThemes\nIdeally this all should function regardless of the theme you have chosen, but WordPress only provides the most basic support for microformats version 1 and doesn\u2019t support the more modern version 2 out of the box. As a result, the display of comments from site to site may be a bit wonky depending on how supportive your particular theme is of the microformats standards. As you can see I\u2019m using a relatively standard version of the TwentySixteen theme without a lot of customization and getting some reasonable results. If you have a choice, I\u2019d recommend one of the following specific themes which have solid semantic markup:\nSempress\nZenPress\nIndependent Publisher\nPlugin\nThe final plugin that enables sending comments from one comment section to another is the WordPress Webmention for Comments plugin. As it is still somewhat experimental and is not available in the WordPress repository, you\u2019ll need to download it from GitHub and activate it. That\u2019s it! There aren\u2019t any settings or anything else to configure.\nUse\nWith the plugin installed, you should now be able to send comments and replies to replies directly within your comments admin UI (or directly within your comments section in individual pages, though this can not require additional clicks to get there, but you also don\u2019t have the benefit of the admin editor either).\nThere is one current caveat however. For the plugin to actually send the webmention properly, it will need to have a URL in your reply that includes the microformats u-in-reply-to class. Currently you\u2019ll need to do this manually until the plugin can properly parse and target the fragmentions for the comments properly. I hope the functionality can be added to the plugin to make the experience seamless in the future.\nSo what does this u-in-reply-to part actually look like? Here\u2019s an example of the one I used to send my reply:\nKh\u00fcrt\nThe class tells the receiving site that the webmention is a reply and to display it as such and the URL is necessary for your webmention plugin to know where to send the notification. You\u2019d simply need to change the URL and the word (or words) that appear between the anchor tags.\nIf you want to have a hidden link and still send a webmention you could potentially add your link to a zero width space as well. This would look like the following:\n&\u200b#8203;\u200b\nBased on my experiments, using a via HTML will work, but it will send it as a plain webmention to the site and it won\u2019t show up natively as a reply.\nSadly, a plain text reply doesn\u2019t work (yet), but hopefully some simple changes could be made to force it to using the common fragmentions pattern that WordPress uses for replies.\nInterestingly this capability has been around for a while, it just hasn\u2019t been well documented or described. I hope now that those with WordPress sites that already support Webmentions will have a better idea what this plugin is doing and how works.\nFuture\nEventually one might expect that all the bugs in the system get worked out and the sub-plugin for sending comment Webmentions will be rolled up into the main Webmentions plugin, which incidentally handles fragmentions already.\nCaveats\nIn addition to the notes above, I will say that this is still technically experimental code not running on many websites, so its functionality may not be exact or perfect in actual use, though in experimenting with it I have found it to be very stable. I would recommend checking that the replies actually post to the receiving site, which incidentally must be able to accept webmentions. If the receiving website doesn\u2019t have webmention support, one will need to manually cut and paste the content there (and likely check the receive notification of replies via email, so you can stay apprised of future replies).\nYou can check the receiving site\u2019s webmention support in most browsers by right clicking and viewing the pages source. Within the source one should see code in the section of the page which indicates there is a webmention endpoint. Here is an example of the code typically injected into WordPress websites that you\u2019d be looking for:\n\n\nAlso keep in mind that some users moderate their comments, so that even though your mention was sent, they may need to approve it prior to it displaying on the page.\nIf you do notice problems or issues or have quirks, please file the issue with as full a description of what you did and what resulted as you can so that it can be troubleshot and made to work not only for you, but hopefully work better for everyone else.\nGive it a try\nSo you\u2019ve implemented everything above? Go ahead and write a reply on your own WordPress website and send me a webmention! I\u2019ll do my best to reply directly to you so you can send another reply to make sure you\u2019ve got things working properly.\nOnce you\u2019re set, go forward and continue helping to make the web a better place.\nSpecial Thanks\nI wanted to take a moment to give special thanks to Aaron Parecki, Matthias Pfefferle, and David Shanske who have done most of the Herculean work to get this and related functionality working. And thanks also to all who make up the IndieWeb community that are pushing the boundaries of what the web is and what it can accomplish. And finally, thanks to Kh\u00fcrt Williams who became the unwitting guinea pig for my first attempt at this. Thank you all!\n\u200b\u200b\u200b\u200b\u200b\u200b\nSyndicated copies to:\n\n\n\nSyndicated copies:\n\nMedium WordPress" ], "url": [ "https://boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/" ], "syndication": [ "https://news.indieweb.org/en/boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/", "https://medium.com/@chrisaldrich/threaded-replies-and-comments-with-webmentions-in-wordpress-cf6f6bbc375", "https://chrisaldrich.wordpress.com/?p=55676257" ], "published": [ "2017-12-15T12:48:26-08:00" ], "content": [ { "html": "

Introduction to what one would consider basic web communication
\nA few days ago I had written a post on my website and a colleague had written a reply on his own website. Because we were both using the W3C Webmention specification on our websites, my site received the notification of his response and displayed it in the comments section of my website. (This in and of itself is really magic enough\u2013cross website @mentions!)
\nTo reply back to him I previously would have written a separate second post on my site in turn to reply to his, thereby fragmenting the conversation across multiple posts and making it harder to follow the conversation. (This is somewhat similar to what Medium.com does with their commenting system as each reply/comment is its own standalone page.)
\nInstead, I\u2019ve now been able to configure my website to allow me to write a reply directly to a response within my comments section admin UI (or even in the comments section of the original page itself), publish it, and have the comment be sent to his reply and display it there. Two copies for the price of one!
\nFrom the comments list in my Admin UI, I can write a reply and it not only lives on my site but it can now be sent as a comment to the site that made the original comment! As an example, here\u2019s my first one and the resultant copy on the site I was replying to.
\nThis means that now, WordPress-based websites (at least self-hosted versions running the WordPress.org code) can easily and simply allow multiple parties to write posts on their own sites and participate in multi-sided conversations back and forth while all parties maintain copies of all sides of the conversation on their own websites in a way that maintains all of the context. As a result, if one site should be shut down or disappear, the remaining websites will still have a fully archived copy of the entire conversation thread. (Let\u2019s hear it for the resilience of the web!)
\nWhat is happening?
\nThis functionality is seemingly so simple that one is left wondering:

\n

\u201cWhy wasn\u2019t this baked into WordPress (and the rest of the web) from the start?\u201d
\n\u201cWhy wasn\u2019t this built after the rise of Twitter, Facebook, or other websites which do this as a basic function?\u201d
\n\u201cHow can I get it tout suite?!\u201d (aka gimme, gimme, gimme, and right now!!!)

\n

While seeming simple, the technical hurdles aren\u2019t necessarily because there had previously never been a universal protocol for the web to allow it. (The Webmentions spec now makes it possible.) Sites like Facebook, Twitter, and others enable it because they\u2019ve got a highly closed and highly customized environment that makes it a simpler problem to solve. In fact, even old-school web-based bulletin boards allowed this!
\nBut even within social media one will immediately notice that you can\u2019t use your Facebook account to reply to a Twitter account. And why not?! (While the web would be far better if one website or page could talk to another, these sites don\u2019t for the simple economic reason that they want you using only their site and not others, and not enabling this functionality keeps you locked into what they\u2019re selling.)
\nI\u2019ll detail the basic set up below, but thought that it would be highly illustrative to have a diagram of what\u2019s physically happening in case the description above seems a bit confusing to picture properly. I\u2019ll depict two websites, each in their own column and color-coded so that content from site A is one color while content from site B is another color.
\nA diagram of where comments live when sent via webmention.
\n Each site composes and owns its own content and sends the replies to the other site.
\nIt really seems nearly incomprehensible to me how this hasn\u2019t been built into the core functionality of the web from the beginning of at least the blogosphere. Yet here we are, and somehow I\u2019m demonstrating how to do this from one WordPress site to another via the open web in 2017. To me this is the entire difference between a true Internet and just using someone else\u2019s intranet.
\nImplementation
\nPrerequisites
\nWhile this general functionality is doable on any website, I\u2019ll stick to enabling it specifically on WordPress, a content management system that is powering roughly 30% of all websites on the internet. You\u2019ll naturally need your own self-hosted WordPress-based website with a few custom plugins and a modern semantic-based theme. (Those interested in setting it up on other platforms are more than welcome to explore the resources of the IndieWeb wiki and their chat which has a wealth of resources.)
\nPlugins
\nAs a minimum set you\u2019ll want to have the following list of plugins enabled and configured:

\n

Webmentions
\nSemantic Linkbacks

\n

IndieWeb Plugin (optional)

\n

Other instructions and help for setting these up and configuring them can be found on the IndieWeb wiki, though not all of the steps there are necessarily required for this functionality.
\nThemes
\nIdeally this all should function regardless of the theme you have chosen, but WordPress only provides the most basic support for microformats version 1 and doesn\u2019t support the more modern version 2 out of the box. As a result, the display of comments from site to site may be a bit wonky depending on how supportive your particular theme is of the microformats standards. As you can see I\u2019m using a relatively standard version of the TwentySixteen theme without a lot of customization and getting some reasonable results. If you have a choice, I\u2019d recommend one of the following specific themes which have solid semantic markup:

\n

Sempress
\nZenPress
\nIndependent Publisher

\n

Plugin
\nThe final plugin that enables sending comments from one comment section to another is the WordPress Webmention for Comments plugin. As it is still somewhat experimental and is not available in the WordPress repository, you\u2019ll need to download it from GitHub and activate it. That\u2019s it! There aren\u2019t any settings or anything else to configure.
\nUse
\nWith the plugin installed, you should now be able to send comments and replies to replies directly within your comments admin UI (or directly within your comments section in individual pages, though this can not require additional clicks to get there, but you also don\u2019t have the benefit of the admin editor either).
\nThere is one current caveat however. For the plugin to actually send the webmention properly, it will need to have a URL in your reply that includes the microformats u-in-reply-to class. Currently you\u2019ll need to do this manually until the plugin can properly parse and target the fragmentions for the comments properly. I hope the functionality can be added to the plugin to make the experience seamless in the future.
\nSo what does this u-in-reply-to part actually look like? Here\u2019s an example of the one I used to send my reply:
\n<a class=\"u-in-reply-to\" href=\"https://islandinthenet.com/manually-adding-microfomats-markup/\">Kh\u00fcrt</a>
\nThe class tells the receiving site that the webmention is a reply and to display it as such and the URL is necessary for your webmention plugin to know where to send the notification. You\u2019d simply need to change the URL and the word (or words) that appear between the anchor tags.
\nIf you want to have a hidden link and still send a webmention you could potentially add your link to a zero width space as well. This would look like the following:
\n<a class=\"u-in-reply-to\" href=\"http://www.example.com\">&\u200b#8203;\u200b</a>
\nBased on my experiments, using a <link> via HTML will work, but it will send it as a plain webmention to the site and it won\u2019t show up natively as a reply.
\nSadly, a plain text reply doesn\u2019t work (yet), but hopefully some simple changes could be made to force it to using the common fragmentions pattern that WordPress uses for replies.
\nInterestingly this capability has been around for a while, it just hasn\u2019t been well documented or described. I hope now that those with WordPress sites that already support Webmentions will have a better idea what this plugin is doing and how works.
\nFuture
\nEventually one might expect that all the bugs in the system get worked out and the sub-plugin for sending comment Webmentions will be rolled up into the main Webmentions plugin, which incidentally handles fragmentions already.
\nCaveats
\nIn addition to the notes above, I will say that this is still technically experimental code not running on many websites, so its functionality may not be exact or perfect in actual use, though in experimenting with it I have found it to be very stable. I would recommend checking that the replies actually post to the receiving site, which incidentally must be able to accept webmentions. If the receiving website doesn\u2019t have webmention support, one will need to manually cut and paste the content there (and likely check the receive notification of replies via email, so you can stay apprised of future replies).
\nYou can check the receiving site\u2019s webmention support in most browsers by right clicking and viewing the pages source. Within the source one should see code in the <head> section of the page which indicates there is a webmention endpoint. Here is an example of the code typically injected into WordPress websites that you\u2019d be looking for:
\n<link rel=\"webmention\" href=\"http://example.com/wp-json/webmention/1.0/endpoint\" />
\n<link rel=\"http://webmention.org/\" href=\"http://example.com/wp-json/webmention/1.0/endpoint\" />
\nAlso keep in mind that some users moderate their comments, so that even though your mention was sent, they may need to approve it prior to it displaying on the page.
\nIf you do notice problems or issues or have quirks, please file the issue with as full a description of what you did and what resulted as you can so that it can be troubleshot and made to work not only for you, but hopefully work better for everyone else.
\nGive it a try
\nSo you\u2019ve implemented everything above? Go ahead and write a reply on your own WordPress website and send me a webmention! I\u2019ll do my best to reply directly to you so you can send another reply to make sure you\u2019ve got things working properly.
\nOnce you\u2019re set, go forward and continue helping to make the web a better place.
\nSpecial Thanks
\nI wanted to take a moment to give special thanks to Aaron Parecki, Matthias Pfefferle, and David Shanske who have done most of the Herculean work to get this and related functionality working. And thanks also to all who make up the IndieWeb community that are pushing the boundaries of what the web is and what it can accomplish. And finally, thanks to Kh\u00fcrt Williams who became the unwitting guinea pig for my first attempt at this. Thank you all!
\n\u200b\u200b\u200b\u200b\u200b\u200b

\n

Syndicated copies to:
\n
\n
\n

\n

Syndicated copies:

\n", "value": "Introduction to what one would consider basic web communication\nA few days ago I had written a post on my website and a colleague had written a reply on his own website. Because we were both using the W3C Webmention specification on our websites, my site received the notification of his response and displayed it in the comments section of my website. (This in and of itself is really magic enough\u2013cross website @mentions!)\nTo reply back to him I previously would have written a separate second post on my site in turn to reply to his, thereby fragmenting the conversation across multiple posts and making it harder to follow the conversation. (This is somewhat similar to what Medium.com does with their commenting system as each reply/comment is its own standalone page.)\nInstead, I\u2019ve now been able to configure my website to allow me to write a reply directly to a response within my comments section admin UI (or even in the comments section of the original page itself), publish it, and have the comment be sent to his reply and display it there. Two copies for the price of one!\nFrom the comments list in my Admin UI, I can write a reply and it not only lives on my site but it can now be sent as a comment to the site that made the original comment! As an example, here\u2019s my first one and the resultant copy on the site I was replying to.\nThis means that now, WordPress-based websites (at least self-hosted versions running the WordPress.org code) can easily and simply allow multiple parties to write posts on their own sites and participate in multi-sided conversations back and forth while all parties maintain copies of all sides of the conversation on their own websites in a way that maintains all of the context. As a result, if one site should be shut down or disappear, the remaining websites will still have a fully archived copy of the entire conversation thread. (Let\u2019s hear it for the resilience of the web!)\nWhat is happening?\nThis functionality is seemingly so simple that one is left wondering:\n\u201cWhy wasn\u2019t this baked into WordPress (and the rest of the web) from the start?\u201d\n\u201cWhy wasn\u2019t this built after the rise of Twitter, Facebook, or other websites which do this as a basic function?\u201d\n\u201cHow can I get it tout suite?!\u201d (aka gimme, gimme, gimme, and right now!!!)\nWhile seeming simple, the technical hurdles aren\u2019t necessarily because there had previously never been a universal protocol for the web to allow it. (The Webmentions spec now makes it possible.) Sites like Facebook, Twitter, and others enable it because they\u2019ve got a highly closed and highly customized environment that makes it a simpler problem to solve. In fact, even old-school web-based bulletin boards allowed this!\nBut even within social media one will immediately notice that you can\u2019t use your Facebook account to reply to a Twitter account. And why not?! (While the web would be far better if one website or page could talk to another, these sites don\u2019t for the simple economic reason that they want you using only their site and not others, and not enabling this functionality keeps you locked into what they\u2019re selling.)\nI\u2019ll detail the basic set up below, but thought that it would be highly illustrative to have a diagram of what\u2019s physically happening in case the description above seems a bit confusing to picture properly. I\u2019ll depict two websites, each in their own column and color-coded so that content from site A is one color while content from site B is another color.\nA diagram of where comments live when sent via webmention.\nEach site composes and owns its own content and sends the replies to the other site.\nIt really seems nearly incomprehensible to me how this hasn\u2019t been built into the core functionality of the web from the beginning of at least the blogosphere. Yet here we are, and somehow I\u2019m demonstrating how to do this from one WordPress site to another via the open web in 2017. To me this is the entire difference between a true Internet and just using someone else\u2019s intranet.\nImplementation\nPrerequisites\nWhile this general functionality is doable on any website, I\u2019ll stick to enabling it specifically on WordPress, a content management system that is powering roughly 30% of all websites on the internet. You\u2019ll naturally need your own self-hosted WordPress-based website with a few custom plugins and a modern semantic-based theme. (Those interested in setting it up on other platforms are more than welcome to explore the resources of the IndieWeb wiki and their chat which has a wealth of resources.)\nPlugins\nAs a minimum set you\u2019ll want to have the following list of plugins enabled and configured:\nWebmentions\nSemantic Linkbacks\nIndieWeb Plugin (optional)\nOther instructions and help for setting these up and configuring them can be found on the IndieWeb wiki, though not all of the steps there are necessarily required for this functionality.\nThemes\nIdeally this all should function regardless of the theme you have chosen, but WordPress only provides the most basic support for microformats version 1 and doesn\u2019t support the more modern version 2 out of the box. As a result, the display of comments from site to site may be a bit wonky depending on how supportive your particular theme is of the microformats standards. As you can see I\u2019m using a relatively standard version of the TwentySixteen theme without a lot of customization and getting some reasonable results. If you have a choice, I\u2019d recommend one of the following specific themes which have solid semantic markup:\nSempress\nZenPress\nIndependent Publisher\nPlugin\nThe final plugin that enables sending comments from one comment section to another is the WordPress Webmention for Comments plugin. As it is still somewhat experimental and is not available in the WordPress repository, you\u2019ll need to download it from GitHub and activate it. That\u2019s it! There aren\u2019t any settings or anything else to configure.\nUse\nWith the plugin installed, you should now be able to send comments and replies to replies directly within your comments admin UI (or directly within your comments section in individual pages, though this can not require additional clicks to get there, but you also don\u2019t have the benefit of the admin editor either).\nThere is one current caveat however. For the plugin to actually send the webmention properly, it will need to have a URL in your reply that includes the microformats u-in-reply-to class. Currently you\u2019ll need to do this manually until the plugin can properly parse and target the fragmentions for the comments properly. I hope the functionality can be added to the plugin to make the experience seamless in the future.\nSo what does this u-in-reply-to part actually look like? Here\u2019s an example of the one I used to send my reply:\nKh\u00fcrt\nThe class tells the receiving site that the webmention is a reply and to display it as such and the URL is necessary for your webmention plugin to know where to send the notification. You\u2019d simply need to change the URL and the word (or words) that appear between the anchor tags.\nIf you want to have a hidden link and still send a webmention you could potentially add your link to a zero width space as well. This would look like the following:\n&\u200b#8203;\u200b\nBased on my experiments, using a via HTML will work, but it will send it as a plain webmention to the site and it won\u2019t show up natively as a reply.\nSadly, a plain text reply doesn\u2019t work (yet), but hopefully some simple changes could be made to force it to using the common fragmentions pattern that WordPress uses for replies.\nInterestingly this capability has been around for a while, it just hasn\u2019t been well documented or described. I hope now that those with WordPress sites that already support Webmentions will have a better idea what this plugin is doing and how works.\nFuture\nEventually one might expect that all the bugs in the system get worked out and the sub-plugin for sending comment Webmentions will be rolled up into the main Webmentions plugin, which incidentally handles fragmentions already.\nCaveats\nIn addition to the notes above, I will say that this is still technically experimental code not running on many websites, so its functionality may not be exact or perfect in actual use, though in experimenting with it I have found it to be very stable. I would recommend checking that the replies actually post to the receiving site, which incidentally must be able to accept webmentions. If the receiving website doesn\u2019t have webmention support, one will need to manually cut and paste the content there (and likely check the receive notification of replies via email, so you can stay apprised of future replies).\nYou can check the receiving site\u2019s webmention support in most browsers by right clicking and viewing the pages source. Within the source one should see code in the section of the page which indicates there is a webmention endpoint. Here is an example of the code typically injected into WordPress websites that you\u2019d be looking for:\n\n\nAlso keep in mind that some users moderate their comments, so that even though your mention was sent, they may need to approve it prior to it displaying on the page.\nIf you do notice problems or issues or have quirks, please file the issue with as full a description of what you did and what resulted as you can so that it can be troubleshot and made to work not only for you, but hopefully work better for everyone else.\nGive it a try\nSo you\u2019ve implemented everything above? Go ahead and write a reply on your own WordPress website and send me a webmention! I\u2019ll do my best to reply directly to you so you can send another reply to make sure you\u2019ve got things working properly.\nOnce you\u2019re set, go forward and continue helping to make the web a better place.\nSpecial Thanks\nI wanted to take a moment to give special thanks to Aaron Parecki, Matthias Pfefferle, and David Shanske who have done most of the Herculean work to get this and related functionality working. And thanks also to all who make up the IndieWeb community that are pushing the boundaries of what the web is and what it can accomplish. And finally, thanks to Kh\u00fcrt Williams who became the unwitting guinea pig for my first attempt at this. Thank you all!\n\u200b\u200b\u200b\u200b\u200b\u200b\nSyndicated copies to:\n\n\n\nSyndicated copies:\n\nMedium WordPress", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich says: @ boffosocko.com" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=64&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" } ] }, "lang": "en-US", "value": "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/Chris Aldrich says:\u00a0@\u00a0boffosocko.com" } ] }, "id": "div-comment-40199", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "name": [ "Experiments with Instagram and WordPress #IndieWeb #Manual #POSSE\nSyndicated copies: X" ], "url": [ "https://islandinthenet.com/instagram-wordpress/" ], "syndication": [ "https://twitter.com/khurtwilliams/status/943858720060198912" ], "published": [ "2017-12-21T09:55:55-08:00" ], "content": [ { "html": "

Experiments with Instagram and WordPress #IndieWeb #Manual #POSSE

\n

Syndicated copies:

\n", "value": "Experiments with Instagram and WordPress #IndieWeb #Manual #POSSE\nSyndicated copies: X", "lang": "en-US" } ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Kh\u00fcrt Williams says: @ islandinthenet.com" ], "photo": [ { "value": "https://secure.gravatar.com/avatar/7fa94585b903e6e183d6164b16b1b573?s=64&d=https://boffosocko.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=pg", "alt": "" } ] }, "lang": "en-US", "value": "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/Kh\u00fcrt Williams says:\u00a0@\u00a0islandinthenet.com" } ] }, "id": "div-comment-40536", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "url": [ "https://boffosocko.com/author/chrisaldrich/" ] }, "lang": "en-US", "value": "Chris Aldrich" } ] }, "id": "comment-40199", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "url": [ "http://boffosocko.com/author/chrisaldrich/" ] }, "lang": "en-US", "value": "Chris Aldrich" } ] }, "id": "comment-40213", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "url": [ "http://boffosocko.com/author/chrisaldrich/" ] }, "lang": "en-US", "value": "Chris Aldrich" } ] }, "id": "comment-40027", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Chris Aldrich" ], "url": [ "http://boffosocko.com/author/chrisaldrich/" ] }, "lang": "en-US", "value": "Chris Aldrich" } ] }, "id": "comment-40028", "lang": "en-US" }, { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Rama Kunapuli" ], "url": [ "https://profiles.google.com/104507251705812285679" ] }, "lang": "en-US", "value": "Rama Kunapuli" } ] }, "id": "comment-39964", "lang": "en-US" } ], "rels": { "profile": [ "http://gmpg.org/xfn/11" ], "pingback": [ "https://boffosocko.com/xmlrpc.php" ], "canonical": [ "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/" ], "dns-prefetch": [ "https://stats.wp.com", "https://fonts.googleapis.com", "https://use.fontawesome.com", "https://i0.wp.com", "https://c0.wp.com" ], "preconnect": [ "https://fonts.gstatic.com" ], "alternate": [ "https://boffosocko.com/feed/", "https://boffosocko.com/comments/feed/", "https://boffosocko.com/kind/article/feed/", "https://boffosocko.com/kind/note/feed/", "https://boffosocko.com/kind/reply/feed/", "https://boffosocko.com/microblog.xml", "https://boffosocko.com/linkblog.xml", "https://boffosocko.com/instagram.xml", "https://boffosocko.com/read.xml", "https://boffosocko.com/kind/checkin/feed/", "https://boffosocko.com/kind/listen/feed/", "https://boffosocko.com/kind/watch/feed/", "https://boffosocko.com/kind/photo/feed/", "https://boffosocko.com/kind/issue/feed/", "https://boffosocko.com/kind/rsvp/feed/", "https://boffosocko.com/kind/jam/feed/", "https://boffosocko.com/kind/annotation/feed/", "https://boffosocko.com/kind/favorite/feed/", "https://boffosocko.com/kind/like/feed/", "https://boffosocko.com/kind/bookmark/feed/", "https://boffosocko.com/kind/follow/feed/", "https://boffosocko.com/kind/repost/feed/", "https://boffosocko.com/kind/wish/feed/", "http://boffosocko.com/kind/eat,drink/feed/", "https://boffosocko.com/category/science/information-theory/feed/", "https://boffosocko.com/category/mathematics/feed/", "http://stream.boffosocko.com/content/all?_t=rss", "https://boffosocko.com/category/microcast/feed/", "https://boffosocko.com/category/podcast/feed/", "https://granary-demo.appspot.com/url?url=http://www.boffosocko.com/blog/&input=html&output=atom&hub=https://bridgy-fed.superfeedr.com/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/feed/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/feed/mf2/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/feed/jf2/", "https://boffosocko.com/wp-json/wp/v2/posts/55702323", "https://boffosocko.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fboffosocko.com%2F2017%2F12%2F11%2Fan-update-to-read-posts-for-physical-books%2F", "https://boffosocko.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fboffosocko.com%2F2017%2F12%2F11%2Fan-update-to-read-posts-for-physical-books%2F&format=xml", "https://boffosocko.com/category/indieweb/feed/rss/", "https://boffosocko.com/tag/micropub/feed/rss/", "https://boffosocko.com/tag/quill/feed/rss/", "https://boffosocko.com/tag/read-posts/feed/rss/", "https://boffosocko.com/kind/article/feed/rss/", "https://boffosocko.com/author/chrisaldrich/feed/rss/", "https://boffosocko.com/feed/json/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/feed/json/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/" ], "feed": [ "http://boffosocko.com/blog/" ], "microsub": [ "https://aperture.p3k.io/microsub/16" ], "me": [ "https://micro.blog/c", "http://tw.boffosocko.com/", "https://wiki.chrisaldrich.net/Main_Page", "http://www.boffosocko.com/publishing", "mailto:chris@boffosocko.com", "http://boffosocko.com/feed/", "https://hypothes.is/users/chrisaldrich", "https://mastodon.social/@chrisaldrich", "https://foursquare.com/chrisaldrich", "https://github.com/chrisaldrich", "https://www.instagram.com/chrisaldrich/", "https://profiles.wordpress.org/chrisaldrich/", "http://www.linkedin.com/in/chrisaldrich", "https://www.flickr.com/people/chrisaldrich/", "https://open.spotify.com/user/chrisaldrich", "https://www.last.fm/user/snark35", "https://www.youtube.com/user/christopherjaldrich/", "https://bsky.app/profile/chrisaldrich.bsky.social", "https://boffosocko.com/about/social-media-accounts-and-links/" ], "stylesheet": [ "https://c0.wp.com/p/jetpack/12.7.2/modules/theme-tools/compat/twentyfifteen.css", "https://c0.wp.com/c/6.2.9/wp-includes/css/dist/block-library/style.min.css", "https://boffosocko.com/wp-content/plugins/all-in-one-seo-pack/dist/Lite/assets/css/table-of-contents/global.e90f6d47.css?ver=4.9.4.1", "https://c0.wp.com/c/6.2.9/wp-includes/css/dist/components/style.min.css", "https://c0.wp.com/c/6.2.9/wp-includes/js/mediaelement/mediaelementplayer-legacy.min.css", "https://c0.wp.com/c/6.2.9/wp-includes/js/mediaelement/wp-mediaelement.min.css", "https://c0.wp.com/c/6.2.9/wp-includes/css/classic-themes.min.css", "https://boffosocko.com/wp-content/plugins/book-review/public/css/book-review-public.min.css?ver=2.3.9", "https://boffosocko.com/wp-content/plugins/webmention/assets/css/webmention.css?ver=5.6.2", "https://boffosocko.com/wp-content/plugins/wp-fragmention/assets/css/fragmention.css?ver=0.1.4", "https://boffosocko.com/wp-content/plugins/fragmentions/styles/fragmentions.css?ver=1.4.0", "https://boffosocko.com/wp-content/plugins/indieweb-post-kinds/css/kind.min.css?ver=3.0.9", "https://boffosocko.com/wp-content/plugins/indieweb/static/css/indieweb.css?ver=5.0.0", "https://fonts.googleapis.com/css?family=Noto+Sans%3A400italic%2C700italic%2C400%2C700%7CNoto+Serif%3A400italic%2C700italic%2C400%2C700%7CInconsolata%3A400%2C700&subset=latin%2Clatin-ext", "https://c0.wp.com/p/jetpack/12.7.2/_inc/genericons/genericons/genericons.css", "https://boffosocko.com/wp-content/themes/twentyfifteen-child/style.css?ver=6.2.9", "https://boffosocko.com/wp-content/themes/twentyfifteen/css/blocks.css?ver=20181230", "https://boffosocko.com/wp-content/plugins/syndication-links/css/syn-bw-medium.min.css?ver=4.5.3", "https://use.fontawesome.com/releases/v5.15.4/css/all.css?ver=2.0.3", "https://use.fontawesome.com/releases/v5.15.4/css/v4-shims.css?ver=2.0.3", "https://c0.wp.com/p/jetpack/12.7.2/css/jetpack.css" ], "https://api.w.org/": [ "https://boffosocko.com/wp-json/" ], "EditURI": [ "https://boffosocko.com/xmlrpc.php?rsd" ], "wlwmanifest": [ "https://boffosocko.com/wp-includes/wlwmanifest.xml" ], "shortlink": [ "https://boffosocko.com/?p=55702323" ], "icon": [ "https://i0.wp.com/boffosocko.com/wp-content/uploads/2015/04/LAAC-rooftop-cropped512x512-551cdb03v1_site_icon.png?fit=32%2C32&ssl=1", "https://i0.wp.com/boffosocko.com/wp-content/uploads/2015/04/LAAC-rooftop-cropped512x512-551cdb03v1_site_icon.png?fit=192%2C192&ssl=1" ], "apple-touch-icon": [ "https://i0.wp.com/boffosocko.com/wp-content/uploads/2015/04/LAAC-rooftop-cropped512x512-551cdb03v1_site_icon.png?fit=180%2C180&ssl=1" ], "micropub_media": [ "https://boffosocko.com/wp-json/micropub/1.0/media" ], "micropub": [ "https://boffosocko.com/wp-json/micropub/1.0/endpoint" ], "webmention": [ "https://boffosocko.com/wp-json/webmention/1.0/endpoint" ], "home": [ "https://boffosocko.com/" ], "noopener": [ "https://boffosocko.com/about/index/", "http://www.apsugen.com", "https://boffosocko.com/about/little-free-library-8424/", "http://stream.boffosocko.com", "http://boffosocko.com/twitter/", "https://docs.google.com/presentation/d/1DUq6MyTCa-E-vewr5g24SwLiu7IoNX72EK9BFJp5GaI/edit?usp=sharing", "http://cat.boffosocko.com", "https://twitter.com/search?q=%23ITBio&src=typd&f=realtime", "https://gregorlove.com/2017/12/my-project-for-todays-indiewebcamp/", "https://indieweb.org/read", "https://wordpress.org/plugins/indieweb-post-kinds/", "http://microformats.org/wiki/Main_Page", "http://boffosocko.com/tag/want-to-read/", "http://david.shanske.com", "http://boffosocko.com/2017/12/09/read-pages-381-461-of-origin-by-dan-brown/", "http://boffosocko.com/type/quote/", "http://boffosocko.com/2017/10/20/indieweb-the-book/", "http://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40174", "https://islandinthenet.com/manually-adding-microfomats-markup/", "https://aaronparecki.com/", "https://teacup.p3k.io/", "https://david.shanske.com/2017/12/13/update-read-posts-physical-books/" ], "author": [ "https://boffosocko.com/author/chrisaldrich/" ], "bookmark": [ "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/" ], "category": [ "https://boffosocko.com/category/indieweb/" ], "tag": [ "https://boffosocko.com/category/indieweb/", "https://boffosocko.com/tag/micropub/", "https://boffosocko.com/tag/quill/", "https://boffosocko.com/tag/read-posts/" ], "syndication": [ "https://www.facebook.com/chrisaldrich/posts/10101528970353005", "http://flip.it/1Ukfez", "https://www.linkedin.com/updates?discuss=&scope=6625072&stype=M&topic=6346203821269622784&type=U&a=1UuQ", "https://chrisaldrich.tumblr.com/post/168453957542", "https://twitter.com/ChrisAldrich/status/940438136559161344", "https://www.twitter.com/chrisaldrich/status/940438136559161344", "https://chrisaldrich.wordpress.com/?p=55676232", "https://plus.google.com/+ChrisAldrich1/posts/Gs5nraLcPyr", "https://twitter.com/khurtwilliams/status/940780250383966208", "https://news.indieweb.org/en/boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/", "https://medium.com/@chrisaldrich/threaded-replies-and-comments-with-webmentions-in-wordpress-cf6f6bbc375", "https://chrisaldrich.wordpress.com/?p=55676257", "https://twitter.com/ChrisAldrich/status/941787443879075840", "https://twitter.com/khurtwilliams/status/943858720060198912" ], "ugc": [ "https://gregorlove.com/", "http://boffosocko.com/author/chrisaldrich/", "https://wordpress.org/plugins/webmention/", "https://islandinthenet.com/manually-adding-microfomats-markup/", "http://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/", "https://indieweb.org/Webmention", "http://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40026", "https://islandinthenet.com/manually-adding-microfomats-markup/#comment-8568", "https://indieweb.org/", "https://twitter.com/ChrisAldrich/status/940874676695420929", "https://plus.google.com/+ChrisAldrich1/posts/P4AAtXvQoAU", "http://www.boffosocko.com", "https://indieweb.org/Instagram", "https://islandinthenet.com", "https://www.nextscripts.com/known-issues/", "https://islandinthenet.com/author/khurtwilliams/", "https://david.shanske.com", "https://github.com/dshanske/indieweb-post-kinds/issues/134", "https://www.w3.org/TR/webmention/", "https://wordpress.org/", "https://indieweb.org/discuss", "https://wordpress.org/plugins/semantic-linkbacks/", "https://wordpress.org/plugins/indieweb/", "https://indieweb.org/Getting_Started_on_WordPress", "http://microformats.org/wiki/Main_Page", "https://wordpress.org/themes/twentysixteen/", "https://wordpress.org/themes/sempress/", "https://github.com/pfefferle/ZenPress", "https://wordpress.org/themes/independent-publisher/", "https://github.com/pfefferle/wordpress-webmention-for-comments", "https://indieweb.org/fragmention", "https://github.com/pfefferle/wordpress-webmention-for-comments/issues", "https://aaronparecki.com/", "https://notiz.blog/", "https://david.shanske.com/", "https://islandinthenet.com/", "https://news.indieweb.org/en/boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/", "https://medium.com/@chrisaldrich/threaded-replies-and-comments-with-webmentions-in-wordpress-cf6f6bbc375", "https://chrisaldrich.wordpress.com/?p=55676257", "https://twitter.com/ChrisAldrich/status/941787443879075840", "https://boffosocko.com/author/chrisaldrich/" ], "external": [ "https://gregorlove.com/", "https://islandinthenet.com/manually-adding-microfomats-markup/", "http://www.boffosocko.com", "https://islandinthenet.com", "https://islandinthenet.com/author/khurtwilliams/", "https://david.shanske.com" ], "nofollow": [ "https://gregorlove.com/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-39988", "https://wordpress.org/plugins/webmention/", "https://islandinthenet.com/manually-adding-microfomats-markup/", "https://indieweb.org/Webmention", "https://islandinthenet.com/manually-adding-microfomats-markup/#comment-8568", "https://indieweb.org/", "https://twitter.com/ChrisAldrich/status/940874676695420929", "https://plus.google.com/+ChrisAldrich1/posts/P4AAtXvQoAU", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40027", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40028", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40013", "http://www.boffosocko.com", "https://indieweb.org/WWTD", "https://github.com/dshanske/indieweb-post-kinds/issues", "https://github.com/dshanske/syndication-links/issues", "https://indieweb.org/Instagram", "https://wordpress.org/plugins/dsgnwrks-instagram-importer/", "https://indieweb.org/Instagram#Exporting_your_data", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40026", "https://islandinthenet.com", "https://www.nextscripts.com/known-issues/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40143", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40179", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40182", "https://islandinthenet.com/author/khurtwilliams/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40181", "https://eddiehinkle.com/2017/12/12/2/article/", "https://aaronparecki.com/", "https://teacup.p3k.io/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40049", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40174", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40176", "https://david.shanske.com", "https://github.com/dshanske/indieweb-post-kinds/issues/134", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40152", "https://david.shanske.com/2017/12/13/update-read-posts-physical-books/", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40184", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40185", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40186", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40187", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40188", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40189", "https://www.w3.org/TR/webmention/", "https://wordpress.org/", "https://indieweb.org/discuss", "https://wordpress.org/plugins/semantic-linkbacks/", "https://wordpress.org/plugins/indieweb/", "https://indieweb.org/Getting_Started_on_WordPress", "http://microformats.org/wiki/Main_Page", "https://wordpress.org/themes/twentysixteen/", "https://wordpress.org/themes/sempress/", "https://github.com/pfefferle/ZenPress", "https://wordpress.org/themes/independent-publisher/", "https://github.com/pfefferle/wordpress-webmention-for-comments", "https://indieweb.org/fragmention", "https://github.com/pfefferle/wordpress-webmention-for-comments/issues", "https://notiz.blog/", "https://david.shanske.com/", "https://islandinthenet.com/", "https://news.indieweb.org/en/boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/", "https://medium.com/@chrisaldrich/threaded-replies-and-comments-with-webmentions-in-wordpress-cf6f6bbc375", "https://chrisaldrich.wordpress.com/?p=55676257", "https://twitter.com/ChrisAldrich/status/941787443879075840", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40213", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40199", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40536", "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#respond", "http://indieweb.org" ], "prev": [ "https://boffosocko.com/2017/12/11/checkin-arclight-cinemas-for-star-wars-the-last-jedi/" ], "next": [ "https://boffosocko.com/2017/12/12/modernist-breadcrumbs-episode-7-thermal-mass-heritage-radio-network/" ] }, "rel-urls": { "http://gmpg.org/xfn/11": { "rels": [ "profile" ] }, "https://boffosocko.com/xmlrpc.php": { "rels": [ "pingback" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/": { "text": "December 11, 2017 8:27 pmDecember 11, 2017", "title": "ActivityPub (JSON)", "type": "application/activity+json", "rels": [ "alternate", "bookmark", "canonical" ] }, "https://stats.wp.com": { "rels": [ "dns-prefetch" ] }, "https://fonts.googleapis.com": { "rels": [ "dns-prefetch" ] }, "https://use.fontawesome.com": { "rels": [ "dns-prefetch" ] }, "https://i0.wp.com": { "rels": [ "dns-prefetch" ] }, "https://c0.wp.com": { "rels": [ "dns-prefetch" ] }, "https://fonts.gstatic.com": { "rels": [ "preconnect" ] }, "https://boffosocko.com/feed/": { "title": "Chris Aldrich \u00bb Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/comments/feed/": { "title": "Chris Aldrich \u00bb Comments Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/article/feed/": { "title": "Chris Aldrich \u00bb Articles Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/note/feed/": { "title": "Chris Aldrich \u00bb Notes Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/reply/feed/": { "title": "Chris Aldrich \u00bb Replies Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/microblog.xml": { "title": "Chris Aldrich \u00bb Microblog", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/linkblog.xml": { "title": "Chris Aldrich \u00bb Linkblog", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/instagram.xml": { "title": "Chris Aldrich \u00bb Instagram", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/read.xml": { "title": "Chris Aldrich \u00bb What I'm Reading", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/checkin/feed/": { "title": "Chris Aldrich \u00bb Checkins", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/listen/feed/": { "title": "Chris Aldrich \u00bb What I'm Listening to", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/watch/feed/": { "title": "Chris Aldrich \u00bb What I'm Watching", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/photo/feed/": { "title": "Chris Aldrich \u00bb Photo Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/issue/feed/": { "title": "Chris Aldrich \u00bb Issues Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/rsvp/feed/": { "title": "Chris Aldrich \u00bb RSVPs", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/jam/feed/": { "title": "Chris Aldrich \u00bb Jams", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/annotation/feed/": { "title": "Chris Aldrich \u00bb Annotations and Highlights", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/favorite/feed/": { "title": "Chris Aldrich \u00bb Favorites ", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/like/feed/": { "title": "Chris Aldrich \u00bb Likes", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/bookmark/feed/": { "title": "Chris Aldrich \u00bb Bookmarks", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/follow/feed/": { "title": "Chris Aldrich \u00bb Follows", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/repost/feed/": { "title": "Chris Aldrich \u00bb Reposts", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/wish/feed/": { "title": "Chris Aldrich \u00bb Wishes", "type": "application/rss+xml", "rels": [ "alternate" ] }, "http://boffosocko.com/kind/eat,drink/feed/": { "title": "Chris Aldrich \u00bb Food Diary", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/category/science/information-theory/feed/": { "title": "Chris Aldrich \u00bb Information Theory Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/category/mathematics/feed/": { "title": "Chris Aldrich \u00bb Mathematics Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "http://stream.boffosocko.com/content/all?_t=rss": { "title": "Chris Aldrich \u00bb Known Social Stream", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/category/microcast/feed/": { "title": "Chris Aldrich \u00bb Microcast", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/category/podcast/feed/": { "title": "Chris Aldrich \u00bb An IndieWeb Podcast", "type": "application/rss+xml", "rels": [ "alternate" ] }, "http://boffosocko.com/blog/": { "title": "BoffoSocko Blog feed", "type": "text/html", "rels": [ "feed" ] }, "https://granary-demo.appspot.com/url?url=http://www.boffosocko.com/blog/&input=html&output=atom&hub=https://bridgy-fed.superfeedr.com/": { "type": "application/atom+xml", "rels": [ "alternate" ] }, "https://aperture.p3k.io/microsub/16": { "rels": [ "microsub" ] }, "https://micro.blog/c": { "rels": [ "me" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/feed/": { "title": "Chris Aldrich \u00bb An update to read posts for physical books Comments Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/feed/mf2/": { "type": "application/mf2+json", "rels": [ "alternate" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/feed/jf2/": { "type": "application/jf2+json", "rels": [ "alternate" ] }, "https://c0.wp.com/p/jetpack/12.7.2/modules/theme-tools/compat/twentyfifteen.css": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://c0.wp.com/c/6.2.9/wp-includes/css/dist/block-library/style.min.css": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/plugins/all-in-one-seo-pack/dist/Lite/assets/css/table-of-contents/global.e90f6d47.css?ver=4.9.4.1": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://c0.wp.com/c/6.2.9/wp-includes/css/dist/components/style.min.css": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://c0.wp.com/c/6.2.9/wp-includes/js/mediaelement/mediaelementplayer-legacy.min.css": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://c0.wp.com/c/6.2.9/wp-includes/js/mediaelement/wp-mediaelement.min.css": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://c0.wp.com/c/6.2.9/wp-includes/css/classic-themes.min.css": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/plugins/book-review/public/css/book-review-public.min.css?ver=2.3.9": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/plugins/webmention/assets/css/webmention.css?ver=5.6.2": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/plugins/wp-fragmention/assets/css/fragmention.css?ver=0.1.4": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/plugins/fragmentions/styles/fragmentions.css?ver=1.4.0": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/plugins/indieweb-post-kinds/css/kind.min.css?ver=3.0.9": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/plugins/indieweb/static/css/indieweb.css?ver=5.0.0": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://fonts.googleapis.com/css?family=Noto+Sans%3A400italic%2C700italic%2C400%2C700%7CNoto+Serif%3A400italic%2C700italic%2C400%2C700%7CInconsolata%3A400%2C700&subset=latin%2Clatin-ext": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://c0.wp.com/p/jetpack/12.7.2/_inc/genericons/genericons/genericons.css": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/themes/twentyfifteen-child/style.css?ver=6.2.9": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/themes/twentyfifteen/css/blocks.css?ver=20181230": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-content/plugins/syndication-links/css/syn-bw-medium.min.css?ver=4.5.3": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://use.fontawesome.com/releases/v5.15.4/css/all.css?ver=2.0.3": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://use.fontawesome.com/releases/v5.15.4/css/v4-shims.css?ver=2.0.3": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://c0.wp.com/p/jetpack/12.7.2/css/jetpack.css": { "media": "all", "type": "text/css", "rels": [ "stylesheet" ] }, "https://boffosocko.com/wp-json/": { "rels": [ "https://api.w.org/" ] }, "https://boffosocko.com/wp-json/wp/v2/posts/55702323": { "type": "application/json", "rels": [ "alternate" ] }, "https://boffosocko.com/xmlrpc.php?rsd": { "title": "RSD", "type": "application/rsd+xml", "rels": [ "EditURI" ] }, "https://boffosocko.com/wp-includes/wlwmanifest.xml": { "type": "application/wlwmanifest+xml", "rels": [ "wlwmanifest" ] }, "https://boffosocko.com/?p=55702323": { "rels": [ "shortlink" ] }, "https://boffosocko.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fboffosocko.com%2F2017%2F12%2F11%2Fan-update-to-read-posts-for-physical-books%2F": { "type": "application/json+oembed", "rels": [ "alternate" ] }, "https://boffosocko.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fboffosocko.com%2F2017%2F12%2F11%2Fan-update-to-read-posts-for-physical-books%2F&format=xml": { "type": "text/xml+oembed", "rels": [ "alternate" ] }, "https://boffosocko.com/category/indieweb/feed/rss/": { "title": "Chris Aldrich \u00bb IndieWeb Category Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/tag/micropub/feed/rss/": { "title": "Chris Aldrich \u00bb Micropub Tag Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/tag/quill/feed/rss/": { "title": "Chris Aldrich \u00bb Quill Tag Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/tag/read-posts/feed/rss/": { "title": "Chris Aldrich \u00bb read posts Tag Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/kind/article/feed/rss/": { "title": "Chris Aldrich \u00bb article Kind Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/author/chrisaldrich/feed/rss/": { "title": "Chris Aldrich \u00bb Posts by Chris Aldrich Feed", "type": "application/rss+xml", "rels": [ "alternate" ] }, "https://boffosocko.com/feed/json/": { "title": "Chris Aldrich \u00bb JSON Feed", "type": "application/feed+json", "rels": [ "alternate" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/feed/json/": { "title": "Chris Aldrich \u00bb An update to read posts for physical books Comments Feed", "type": "application/feed+json", "rels": [ "alternate" ] }, "https://i0.wp.com/boffosocko.com/wp-content/uploads/2015/04/LAAC-rooftop-cropped512x512-551cdb03v1_site_icon.png?fit=32%2C32&ssl=1": { "rels": [ "icon" ] }, "https://i0.wp.com/boffosocko.com/wp-content/uploads/2015/04/LAAC-rooftop-cropped512x512-551cdb03v1_site_icon.png?fit=192%2C192&ssl=1": { "rels": [ "icon" ] }, "https://i0.wp.com/boffosocko.com/wp-content/uploads/2015/04/LAAC-rooftop-cropped512x512-551cdb03v1_site_icon.png?fit=180%2C180&ssl=1": { "rels": [ "apple-touch-icon" ] }, "https://boffosocko.com/wp-json/micropub/1.0/media": { "rels": [ "micropub_media" ] }, "https://boffosocko.com/wp-json/micropub/1.0/endpoint": { "rels": [ "micropub" ] }, "https://boffosocko.com/wp-json/webmention/1.0/endpoint": { "rels": [ "webmention" ] }, "https://boffosocko.com/": { "text": "Chris Aldrich", "rels": [ "home" ] }, "https://boffosocko.com/about/index/": { "text": "Index", "rels": [ "noopener" ] }, "http://tw.boffosocko.com/": { "text": "TiddlyWikiResearch Wiki and Commonplace Book", "rels": [ "me" ] }, "https://wiki.chrisaldrich.net/Main_Page": { "text": "MediaWikiMy personal wiki", "rels": [ "me" ] }, "http://www.apsugen.com": { "text": "Apsugen", "rels": [ "noopener" ] }, "https://boffosocko.com/about/little-free-library-8424/": { "text": "Little Free Library #8424", "rels": [ "noopener" ] }, "http://stream.boffosocko.com": { "text": "Social Stream", "rels": [ "noopener" ] }, "http://boffosocko.com/twitter/": { "text": "Twitter Archive", "rels": [ "noopener" ] }, "https://docs.google.com/presentation/d/1DUq6MyTCa-E-vewr5g24SwLiu7IoNX72EK9BFJp5GaI/edit?usp=sharing": { "text": "IndieWeb + WordPress: Creating Your Dial Tone on the Internet", "rels": [ "noopener" ] }, "http://cat.boffosocko.com": { "text": "Category Theory", "rels": [ "noopener" ] }, "https://twitter.com/search?q=%23ITBio&src=typd&f=realtime": { "text": "#ITBio on Twitter", "rels": [ "noopener" ] }, "http://www.boffosocko.com/publishing": { "text": "Boffo Socko Publishing", "rels": [ "me" ] }, "mailto:chris@boffosocko.com": { "title": "email me", "text": "Email", "rels": [ "me" ] }, "http://boffosocko.com/feed/": { "title": "Click to subscribe to the RSS Feed at http://boffosocko.com/feed/", "text": "RSS", "rels": [ "me" ] }, "https://hypothes.is/users/chrisaldrich": { "title": "Hypothes.is annotations", "text": "Hypothesis", "rels": [ "me" ] }, "https://mastodon.social/@chrisaldrich": { "title": "Mastodon", "text": "Mastodon", "rels": [ "me" ] }, "https://foursquare.com/chrisaldrich": { "title": "Foursquare", "text": "Foursquare", "rels": [ "me" ] }, "https://github.com/chrisaldrich": { "title": "GitHub", "text": "GitHub", "rels": [ "me" ] }, "https://www.instagram.com/chrisaldrich/": { "title": "Instagram", "text": "Instagram", "rels": [ "me" ] }, "https://profiles.wordpress.org/chrisaldrich/": { "title": "WordPress", "text": "WordPress", "rels": [ "me" ] }, "http://www.linkedin.com/in/chrisaldrich": { "title": "LinkedIn", "text": "LinkedIn", "rels": [ "me" ] }, "https://www.flickr.com/people/chrisaldrich/": { "title": "Flickr", "text": "Flickr", "rels": [ "me" ] }, "https://open.spotify.com/user/chrisaldrich": { "title": "Spotify", "text": "Spotify", "rels": [ "me" ] }, "https://www.last.fm/user/snark35": { "title": "Last.fm scrobbles", "text": "Last.fm", "rels": [ "me" ] }, "https://www.youtube.com/user/christopherjaldrich/": { "title": "YouTube channel", "text": "YouTube", "rels": [ "me" ] }, "https://bsky.app/profile/chrisaldrich.bsky.social": { "text": "Bluesky", "rels": [ "me" ] }, "https://boffosocko.com/about/social-media-accounts-and-links/": { "title": "Look for other social media platforms here", "text": "Elsewhere", "rels": [ "me" ] }, "https://gregorlove.com/2017/12/my-project-for-todays-indiewebcamp/": { "text": "gRegor Morrill\u2019s IndieWebCamp Austin project", "rels": [ "noopener" ] }, "https://indieweb.org/read": { "text": "read posts", "rels": [ "noopener" ] }, "https://wordpress.org/plugins/indieweb-post-kinds/": { "text": "Post Kinds Plugin", "rels": [ "noopener" ] }, "http://microformats.org/wiki/Main_Page": { "text": "microformats ", "rels": [ "nofollow", "noopener", "ugc" ] }, "http://boffosocko.com/tag/want-to-read/": { "text": "want to read", "rels": [ "noopener" ] }, "http://david.shanske.com": { "text": "David Shanske", "rels": [ "noopener" ] }, "http://boffosocko.com/2017/12/09/read-pages-381-461-of-origin-by-dan-brown/": { "text": "recent read post", "rels": [ "noopener" ] }, "http://boffosocko.com/type/quote/": { "text": "quote posts", "rels": [ "noopener" ] }, "http://boffosocko.com/2017/10/20/indieweb-the-book/": { "text": "The Book", "rels": [ "noopener" ] }, "https://boffosocko.com/author/chrisaldrich/": { "text": "\n\t\t\t\tView all posts by Chris Aldrich\t\t\t", "rels": [ "author", "ugc" ] }, "https://boffosocko.com/category/indieweb/": { "text": "IndieWeb", "rels": [ "category", "tag" ] }, "https://boffosocko.com/tag/micropub/": { "text": "Micropub", "rels": [ "tag" ] }, "https://boffosocko.com/tag/quill/": { "text": "Quill", "rels": [ "tag" ] }, "https://boffosocko.com/tag/read-posts/": { "text": "read posts", "rels": [ "tag" ] }, "https://www.facebook.com/chrisaldrich/posts/10101528970353005": { "text": " Facebook", "rels": [ "syndication" ] }, "http://flip.it/1Ukfez": { "text": " Flipboard", "rels": [ "syndication" ] }, "https://www.linkedin.com/updates?discuss=&scope=6625072&stype=M&topic=6346203821269622784&type=U&a=1UuQ": { "text": " LinkedIn", "rels": [ "syndication" ] }, "https://chrisaldrich.tumblr.com/post/168453957542": { "text": " Tumblr", "rels": [ "syndication" ] }, "https://twitter.com/ChrisAldrich/status/940438136559161344": { "text": " X", "rels": [ "syndication" ] }, "https://www.twitter.com/chrisaldrich/status/940438136559161344": { "text": " X", "rels": [ "syndication" ] }, "https://chrisaldrich.wordpress.com/?p=55676232": { "text": " WordPress", "rels": [ "syndication" ] }, "https://plus.google.com/+ChrisAldrich1/posts/Gs5nraLcPyr": { "text": " googleplus", "rels": [ "syndication" ] }, "https://gregorlove.com/": { "text": "gRegor Morrill", "rels": [ "external", "nofollow", "ugc" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-39988": { "text": "Reply", "rels": [ "nofollow" ] }, "http://boffosocko.com/author/chrisaldrich/": { "text": "Chris Aldrich", "rels": [ "ugc" ] }, "https://wordpress.org/plugins/webmention/": { "text": "Webmentions plugin", "rels": [ "nofollow", "ugc" ] }, "https://islandinthenet.com/manually-adding-microfomats-markup/": { "text": "Khurt Williams used his website", "rels": [ "external", "nofollow", "noopener", "ugc" ] }, "http://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/": { "text": "one of my posts", "rels": [ "ugc" ] }, "https://indieweb.org/Webmention": { "text": "Webmention", "rels": [ "nofollow", "ugc" ] }, "http://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40026": { "text": "write my reply directly within the comments section of my original post", "rels": [ "ugc" ] }, "https://islandinthenet.com/manually-adding-microfomats-markup/#comment-8568": { "text": "Webmention his original back in return", "rels": [ "nofollow", "ugc" ] }, "https://indieweb.org/": { "text": "#IndieWeb", "rels": [ "nofollow", "ugc" ] }, "https://twitter.com/ChrisAldrich/status/940874676695420929": { "text": " ", "rels": [ "nofollow", "ugc" ] }, "https://plus.google.com/+ChrisAldrich1/posts/P4AAtXvQoAU": { "text": " ", "rels": [ "nofollow", "ugc" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40027": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40028": { "text": "Reply", "rels": [ "nofollow" ] }, "https://twitter.com/khurtwilliams/status/940780250383966208": { "text": " X", "rels": [ "syndication" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40013": { "text": "Reply", "rels": [ "nofollow" ] }, "http://www.boffosocko.com": { "text": "Chris Aldrich", "rels": [ "external", "nofollow", "ugc" ] }, "https://indieweb.org/WWTD": { "text": "WWTD", "rels": [ "nofollow" ] }, "https://github.com/dshanske/indieweb-post-kinds/issues": { "text": "GitHub issue queue", "rels": [ "nofollow" ] }, "https://github.com/dshanske/syndication-links/issues": { "text": "Syndication Links Plugin", "rels": [ "nofollow" ] }, "https://indieweb.org/Instagram": { "text": "https://indieweb.org/Instagram", "rels": [ "nofollow", "ugc" ] }, "https://wordpress.org/plugins/dsgnwrks-instagram-importer/": { "text": "DsgnWrks Instagram Importer", "rels": [ "nofollow" ] }, "https://indieweb.org/Instagram#Exporting_your_data": { "text": "Instagram export bookmarklet", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40026": { "text": "Reply", "rels": [ "nofollow" ] }, "https://islandinthenet.com": { "text": "Kh\u00fcrt Williams", "rels": [ "external", "nofollow", "ugc" ] }, "https://www.nextscripts.com/known-issues/": { "text": "https://www.nextscripts.com/known-issues/", "rels": [ "nofollow", "ugc" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40143": { "text": "Reply", "rels": [ "nofollow" ] }, "http://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40174": { "text": "comment on my site", "rels": [ "noopener" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40179": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40182": { "text": "Reply", "rels": [ "nofollow" ] }, "https://islandinthenet.com/author/khurtwilliams/": { "text": "Kh\u00fcrt Williams", "rels": [ "external", "nofollow", "ugc" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40181": { "text": "Reply", "rels": [ "nofollow" ] }, "https://eddiehinkle.com/2017/12/12/2/article/": { "text": "Owning my Reading and 100 Days of Reading Chapters", "rels": [ "nofollow" ] }, "https://aaronparecki.com/": { "text": "Aaron Parecki", "rels": [ "nofollow", "noopener", "ugc" ] }, "https://teacup.p3k.io/": { "text": "Teacup", "rels": [ "nofollow", "noopener" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40049": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40174": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40176": { "text": "Reply", "rels": [ "nofollow" ] }, "https://david.shanske.com": { "text": "David Shanske", "rels": [ "external", "nofollow", "ugc" ] }, "https://github.com/dshanske/indieweb-post-kinds/issues/134": { "text": "https://github.com/dshanske/indieweb-post-kinds/issues/134", "rels": [ "nofollow", "ugc" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40152": { "text": "Reply", "rels": [ "nofollow" ] }, "https://david.shanske.com/2017/12/13/update-read-posts-physical-books/": { "text": "Test", "rels": [ "nofollow", "noopener" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40184": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40185": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40186": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40187": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40188": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40189": { "text": "Reply", "rels": [ "nofollow" ] }, "https://www.w3.org/TR/webmention/": { "text": "W3C Webmention specification", "rels": [ "nofollow", "ugc" ] }, "https://wordpress.org/": { "text": "WordPress.org", "rels": [ "nofollow", "ugc" ] }, "https://indieweb.org/discuss": { "text": "chat", "rels": [ "nofollow", "ugc" ] }, "https://wordpress.org/plugins/semantic-linkbacks/": { "text": "Semantic Linkbacks", "rels": [ "nofollow", "ugc" ] }, "https://wordpress.org/plugins/indieweb/": { "text": "IndieWeb Plugin", "rels": [ "nofollow", "ugc" ] }, "https://indieweb.org/Getting_Started_on_WordPress": { "text": "IndieWeb wiki", "rels": [ "nofollow", "ugc" ] }, "https://wordpress.org/themes/twentysixteen/": { "text": "TwentySixteen theme", "rels": [ "nofollow", "ugc" ] }, "https://wordpress.org/themes/sempress/": { "text": "Sempress", "rels": [ "nofollow", "ugc" ] }, "https://github.com/pfefferle/ZenPress": { "text": "ZenPress", "rels": [ "nofollow", "ugc" ] }, "https://wordpress.org/themes/independent-publisher/": { "text": "Independent Publisher", "rels": [ "nofollow", "ugc" ] }, "https://github.com/pfefferle/wordpress-webmention-for-comments": { "text": "WordPress Webmention for Comments plugin", "rels": [ "nofollow", "ugc" ] }, "https://indieweb.org/fragmention": { "text": "fragmentions", "rels": [ "nofollow", "ugc" ] }, "https://github.com/pfefferle/wordpress-webmention-for-comments/issues": { "text": "please file the issue", "rels": [ "nofollow", "ugc" ] }, "https://notiz.blog/": { "text": "Matthias Pfefferle", "rels": [ "nofollow", "ugc" ] }, "https://david.shanske.com/": { "text": "David Shanske", "rels": [ "nofollow", "ugc" ] }, "https://islandinthenet.com/": { "text": "Kh\u00fcrt Williams", "rels": [ "nofollow", "ugc" ] }, "https://news.indieweb.org/en/boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/": { "text": "\u200b\u200b\u200b\u200b\u200b\u200b", "rels": [ "nofollow", "syndication", "ugc" ] }, "https://medium.com/@chrisaldrich/threaded-replies-and-comments-with-webmentions-in-wordpress-cf6f6bbc375": { "text": " ", "rels": [ "nofollow", "syndication", "ugc" ] }, "https://chrisaldrich.wordpress.com/?p=55676257": { "text": " ", "rels": [ "nofollow", "syndication", "ugc" ] }, "https://twitter.com/ChrisAldrich/status/941787443879075840": { "text": " ", "rels": [ "nofollow", "syndication", "ugc" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40213": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40199": { "text": "Reply", "rels": [ "nofollow" ] }, "https://twitter.com/khurtwilliams/status/943858720060198912": { "text": " X", "rels": [ "syndication" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40536": { "text": "Reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#respond": { "text": "Cancel reply", "rels": [ "nofollow" ] }, "https://boffosocko.com/2017/12/11/checkin-arclight-cinemas-for-star-wars-the-last-jedi/": { "text": "Previous Previous post: Checkin ArcLight Cinemas for Star Wars: The Last Jedi", "rels": [ "prev" ] }, "https://boffosocko.com/2017/12/12/modernist-breadcrumbs-episode-7-thermal-mass-heritage-radio-network/": { "text": "Next Next post: \ud83c\udfa7 Modernist BreadCrumbs | Episode 7: Thermal Mass | Heritage Radio Network", "rels": [ "next" ] }, "http://indieweb.org": { "text": "principles from ", "rels": [ "nofollow" ] } }, "debug": { "package": "https://packagist.org/packages/mf2/mf2", "source": "https://github.com/indieweb/php-mf2", "version": "v0.5.0", "note": [ "This output was generated from the php-mf2 library available at https://github.com/indieweb/php-mf2", "Please file any issues with the parser at https://github.com/indieweb/php-mf2/issues", "Using the Masterminds HTML5 parser" ] } }