Does anyone know what's going on with Twitter's crossdomain policy
file? I read -- over a year and a half ago -- that they were
temporarily blocking broad access because of security holes. The
crossdomain file still reads:
http://www.w3.org/2001/XMLSchema-
instance" xsi:noNamespaceSchemaLocation="http://www.adobe.com/xml/
schemas/PolicyFile.xsd">
...which means Twitter is disallowing access from anything other than
the twitter.com domain, meaning no access to any web-based apps
without a server-side proxy workaround. Wasn't this supposed to be
temporary? And why even have a web-based API if they're still, a year
and a half later, actively disallowing connections to it?
