hmm - its possible there was a S3 hiccup ("bucket" sounds like a S3 related
term).

On Sun, Feb 28, 2010 at 8:29 AM, Orian Marx (@orian) <or...@orianmarx.com>wrote:

> I see it now too, but when I posted yesterday I was getting some error
> referring to "Bucket does not exist" or something like that.
>
> On Feb 27, 11:30 pm, Raffi Krikorian <ra...@twitter.com> wrote:
> > > 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]$ wgethttp://
> 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 Teamhttp://twitter.com/raffi
>



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

Reply via email to