<?xml version="1.0" encoding="UTF-8"?>
<oembed>
 <version>1.0</version>
 <type>link</type>
 <provider_name>Rainbow Dash Network</provider_name>
 <provider_url>http://rainbowdash.net/</provider_url>
 <title>Bit Shift (bitshift)'s status on Monday, 21-May-12 19:09:56 UTC</title>
 <author_name>Bit Shift (bitshift)</author_name>
 <author_url>http://rainbowdash.net/bitshift</author_url>
 <url>http://rainbowdash.net/notice/1423279</url>
 <html>@&lt;span class=&quot;vcard&quot;&gt;&lt;a href=&quot;http://rainbowdash.net/user/2043&quot; class=&quot;url&quot; title=&quot;Chris Bell&quot;&gt;&lt;span class=&quot;fn nickname&quot;&gt;mrdragon&lt;/span&gt;&lt;/a&gt;&lt;/span&gt; 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.</html>
</oembed>
