Other post properties appear in e-content and are parsed by other sites, plugins incorrectly.

[chrisaldrich]

When replying to another WordPress site (and other platforms as well) the webmention sends the additional meta-data from Post Kinds' Post Properties in the webmention.

When this metadata appears on the originating site, it gives the necessary detail and context for the reply which follows it.

However, when the webmention appears as a comment on the receiving site(s), the additional metadata is extraneous. The receiving site places the reply into its comment stream (which already provides the context that the webmention is a reply!) Additionally, because the reply icon/svg isn't sent/displayed it removes a bit of the added context and makes replies even odder looking.

If there's a way to remove the metadata from the sent webmention on replies, this may be the best solution. In other post types, this may not be the case, for if you remove this data (for a bookmark as an example), then the URL wouldn't be included and there would be no webmention at all.

Example:

Original reply post: http://boffosocko.com/2016/08/26/reply-to-scott-kingery-about-wallabag-and-reading/ Receiving endpoint: http://techlifeweb.com/14892-2/#comment-120995 Additional receiving endpoint: http://boffosocko.com/2016/08/22/a-new-reading-post-type-for-bookmarking-and-reading-workflow/#comment-31841

Additional information/thoughts/considerations: Recall though that on POSSE copies of the original, because the metadata from Post Kinds isn't "technically" part of the_body (right?), many POSSE methods (except manual methods) won't pick up any of these data. In some cases, what is in Post Kinds' Post Properties may be ALL of the data which was meant to be POSSEd (example: bookmarks, likes, favorites, read, etc.)

Ideally, having things set up to support the largest flow of POSSE methods (Jepack, SNAP, et al.) in a simple manner would be best.

[dshanske]

I had the idea of putting in a series of compatability settings, but there is a problem because of what you mentioned. All of this is dynamically entere into ther content. Now, because the content is wrapped in e-content, that means the in-reply-to is inside the e-content, which is what becomes the comment. Omn my site, I fixed this by making an amendment to the theme. That fixed the parsing issue. Basically, I moved e-content inside the+_content using a filter set at priority -1.