<?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 Thursday, 10-May-12 16:32:57 UTC</title>
 <author_name>Bit Shift (bitshift)</author_name>
 <author_url>http://rainbowdash.net/bitshift</author_url>
 <url>http://rainbowdash.net/notice/1358671</url>
 <html>@&lt;span class=&quot;vcard&quot;&gt;&lt;a href=&quot;http://rainbowdash.net/user/798&quot; class=&quot;url&quot; title=&quot;Officer Wiggy Bingo&quot;&gt;&lt;span class=&quot;fn nickname&quot;&gt;redenchilada&lt;/span&gt;&lt;/a&gt;&lt;/span&gt; Eh, it's understandable as far as the twitter-compatible API goes; Twitter has no public APIs for such things. If it's still not possible via the AtomPub API (which IdentiCurse is migrating to in the long term), then yes. And it's still a POS in other ways (most of which Cerulean has complained about in detail here). :P</html>
</oembed>
