Take a look at Twitter's crossdomain.xml (http://twitter.com/
crossdomain.xml). It was changed earlier this year so that requests
coming from pages on other domains are denied. Your code could run
fine inside an AIR app, otherwise you will need to use server proxy.
Alternatively, use the search
I fixed the link up. Sorry 'bout that!
On Tue, Oct 28, 2008 at 2:45 AM, Pims [EMAIL PROTECTED] wrote:
Hey Alex,
We submitted our little app to have a custom from app_name when we
post links through the API.
It used to work fine for a long time, but somehow, the link got
stripped and it's
We're noticing high network latency and timeouts on twitter.com today,
which some of you are probably noticing in your apps. The problem
doesn't appear to be within our cluster, and we're working with our
service provider to sort it out. We'll be tracking the issue on
I'm tracking this issue here, for the record:
http://code.google.com/p/twitter-api/issues/detail?id=135
On Mon, Oct 27, 2008 at 9:17 PM, Alex Payne [EMAIL PROTECTED] wrote:
You entirely right Chris. The onus is on us. I'll get this fixed up
tomorrow. Sorry to anyone who lost time on this
The favorites/create API (at least under JSON) often returns JSON
indicating that the method failed, and that the favorite was NOT
created, even when it successfully favorited the tweet. Here is an
example:
http://twitter.com/favorites/create/979618853.json
returns:
{created_at:Tue Oct 28
