If my app deletes a post it made to a user's wall, will all likes and shares made by other people also be deleted? <p>Lets say I have a FB app I've created, and for whatever reason the server code for the app is responsible for posting stories to the app user's wall (using a token).</p> <p>Now let's say we want to take down that post at a later date - easy, right? Because the app created the post, it owns it, and using the ID it received originally it can take that post down. (I presume the ID I get back is actually an "object id" referring to my content, rather than specifically to the post on the user's wall - correct?)</p> <p>Here's the thing though. What if one or more friends of the user shared that story to their own wall - what if this happened a number of times, spreading through the friend relationship tree further and further. Does my app still have the power to remove all of these posts, because it created the original post?</p> <p>Additionally, what if the original user deleted the post themselves from their wall, but not until it had been shared by his/her friends? Would this have the same effect (delete everywhere), or would it only be that one specific post being removed? Would my app get an error when it tried to delete the post itself if the post had already been deleted by the user? </p> <p>The reason I ask is because, if my app deleted the original post that it made to the user's wall, I would want <em>all</em> of the shared posts or likes to also be deleted, no matter where they were down the friend chain. I don't want to delete my original post and assume all is well, only to discover that because it was shared several times down the chain that it is still visible somewhere. </p> <p>In case it's relevant, the "post" my app will make would require a custom image and a specific return URL - I tried the <code>/user_id/links</code> graph API and it didnt work (there's a bug with it). So I'd be most likely using <code>/user_id/feed</code> to make the post.</p>