!gnusocial - I'm playing with #AtomPub a bit again, and am having a little trouble with this: in the JSON representation of a post, the local conversation ID is always easily found in the "statusnet_conversation_id" property; however, in the Atom representation, that information is sometimes absent. The <status_net> element only ever contains a "notice_id" property and no conversation ID; the <ostatus:conversation> element /sometimes/ has an "href" attribute with a URL containing the conversation ID, but not always. It would be really helpful if the local conversation ID was always present in Atom posts.