{"version":"1.0","provider_name":"Rainbow Dash Network","provider_url":"http:\/\/rainbowdash.net\/","type":"link","title":"Bit Shift (bitshift)'s status on Monday, 21-May-12 19:09:56 UTC","author_name":"Bit Shift (bitshift)","author_url":"http:\/\/rainbowdash.net\/bitshift","url":"http:\/\/rainbowdash.net\/notice\/1423279","html":"@<span class=\"vcard\"><a href=\"http:\/\/rainbowdash.net\/user\/2043\" class=\"url\" title=\"Chris Bell\"><span class=\"fn nickname\">mrdragon<\/span><\/a><\/span> As in, are there any issues? Not that I know of. There _is_ one major improvement, namely that conversation IDs are sent in the Twitter-compatible API, which allows for clients to get the full context view, like the one in the site, rather than having to follow a chain back (i.e., notice X is a reply to notice Y, so fetch notice Y, that's a reply to notice Z, so fetch notice Z, and so on), which only gives one thin strand of the full conversation."}