Re: [twitter-dev] Search crossdomain.xml accidentally deleted again?

[Raffi Krikorian]

>
> My flash application is currently getting security errors from
> search.twitter.com. It would appear the crossdomain.xml file no longer
> exists.


i still see it

[ra...@tw-mbp13-raffi Desktop]$ wget
http://search.twitter.com/crossdomain.xml
--2010-02-27 20:29:27--  http://search.twitter.com/crossdomain.xml
Resolving search.twitter.com... 168.143.162.59
Connecting to search.twitter.com|168.143.162.59|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 206 [application/xml]
Saving to: `crossdomain.xml'

100%[=>] 206
--.-K/s   in 0s

2010-02-27 20:29:27 (16.4 MB/s) - `crossdomain.xml' saved [206/206]

And while we're at it... has the Twitter team thought more about
> loosening the restrictions in their crossdomain.xml files so that
> Flash developers can actually access the api without using a php or
> similar proxy?


yup.  we have a few thing we want to make sure we do first, and then the
plan is to loosen restrictions on api.twitter.com.

-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

[twitter-dev] Search crossdomain.xml accidentally deleted again?

[Orian Marx (@orian)]

My flash application is currently getting security errors from
search.twitter.com. It would appear the crossdomain.xml file no longer
exists. This problem has happened before:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/d3230be66c27c88e/

And while we're at it... has the Twitter team thought more about
loosening the restrictions in their crossdomain.xml files so that
Flash developers can actually access the api without using a php or
similar proxy? I brought this issue up in October:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e35a708400b529b3/