Store Webmention Responses in Post Meta

[dshanske]

Use case for Bridgy....

"A POST to http://brid.gy/publish/webmention will return 200 OK on success with a JSON response containing at least a url field that points to the silo object that it operated on. For Twitter favorites and Facebook likes and event RSVPs, this is the tweet, post, or event. If a new object was created, e.g. a Facebook post or comment or Twitter tweet, @-reply, or retweet, there will also be an id field with the silo id of that object."

The json response can be extracted and the entire array attached to the post using the add_post_meta function in Wordpress.

This data can then be used by the theme or another plugin to add rel-syndication links.

[pfefferle]

The idea is good, but I am not sure if this should be part of the core plugin, because it is very brid.gy specific. The spec doesn't specify the response at all, so I think it would be cool to code a bird.gy plugin that hooks into the "send_webmention" action (if added a filter today bf62f8f#diff-a206f8eddc4eec457824d08af6ecd005R319)

what do you think @snarfed?

[dshanske]

This was the debate I was trying to figure out. Should the response be
loaded by the webmentions plugin and then retrieved by a Bridgy plugin or
aware theme or both be in a Bridgy plugin. That's why I filed it as an
issue. Sending data in the response is Bridgy specific, but doesn't have to
be.
On May 5, 2014 2:40 PM, "Matthias Pfefferle" notifications@github.com
wrote:

The idea is good, but I am not sure if this should be part of the core
plugin, because it is very brid.gy specific. The spec doesn't specify the
response at all, so I think it would be cool to code a bird.gy plugin
that hooks into the "send_webmention" action (if added a filter today
bf62f8f#diff-a206f8eddc4eec457824d08af6ecd005R319bf62f8f#diff-a206f8eddc4eec457824d08af6ecd005R319
)

what do you think @snarfed https://github.com/snarfed?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23#issuecomment-42222007
.

[snarfed]

actually, the webmention spec strongly encourages a response body: The response body SHOULD include a URL that can be used to monitor the status of the request. lots of other existing implementations send one, including this plugin, p3k, webmention.io, and i think idno, so this probably isn't specific to bridgy.

[dshanske]

Either way, the filter addition allows for that and is probably better than
dumping it to mets as it allows for custom handling.
On May 5, 2014 3:09 PM, "Ryan Barrett" notifications@github.com wrote:

actually, the webmention spec strongly encourages a response bodyhttps://github.com/converspace/webmention/blob/master/README.md#sender-notifies-receiver:
The response body SHOULD include a URL that can be used to monitor the
status of the request. lots of other existing implementations send one,
including this plugin, p3k, webmention.io, and i think idno, so this
probably isn't specific to bridgy.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23#issuecomment-42225626
.

[snarfed]

👍 filter (or hook) makes sense to me too.

[pfefferle]

Thanks for pointing me to the response body part. I will also change the response of the plugin to return a more useful information, like the url of the comment.