allow updating a published post

[snarfed]

we already store the source URL and silo post/comment id in the Publish entity. just need to look it up on a publish attempt and translate to the silo API call for updating or deleting instead of creating.

cc @kartikprabhu

[karadaisy]

Note: Facebook's API docs make it look like you can edit/update a post via the API, but when I actually tried to do it, it gave me an error with a message along the lines of "this type of post cannot be edited"

[snarfed]

:sadface: i had a similar experience with instagram's like api. sigh.

[tantek]

For reference: http://indiewebcamp.com/CRUD

And presumably such "deletes" could include "unliking" a post e.g. on FB (including POSSE copies there).

Could be used for for deleting POSSE "retweets" (unretweeting?) as well, by the author deleting the original, sending a webmention to Bridgy publish, then responding to Bridgy's request to the original permalink with a 410.

[karadaisy]

Hey, I learned from a question to @scripting that it is possible to edit posts on Facebook using the graph API! You simply POST to the /{post-id} edge. I'm not sure if this is a new undocumented feature or if I was doing something wrong in April when I first tried it.

See here for proof: https://www.facebook.com/kyle.mahan/posts/10101004398903469

[snarfed]

👏 🍎

[tantek]

I definitely want this (Bridgy Publish POSSE CRUD) for updating a POSSEd photo post to add person-tags to it, but that may also require implementing #459

Encountered: http://indiewebcamp.com/irc/2015-09-01/line/1441139228600

[snarfed]

starting to look at this again.

silo support:

• Facebook: yes, update and delete posts. docs. only posts that we created, though.
• Twitter: yes, delete tweets and favorites.
• Instagram: yes, delete likes.
• Flickr: yes. replacing/updating/deleting photos, updating/deleting comments, and deleting likes.

[snarfed]

there's also using u-syndication to detect and update a POSSE post that we didn't originally create. that only works for update, though, since deletes return 410, and Flickr is the only silo that supports updating things (photos, comments) that we didn't create with our own app.

(technically a delete 410 could also return an HTML body that includes the original u-syndication(s) we could use...but in practice, i doubt many implementations do that, if any.)