i want to connect my AIR application with twitter API,
i never used any API before,
i used
http://twitter.com/direct_messages/new.format";
result="
resultHandlerSendMessage(event);"
fault="faultHandlerSendMessage(event);"
method="POST"
resultFormat="e4x" >
{u
Hey Stephen,
I have a similar app, http://friendorfollow.com. I process my data in
a similar manner as you and I've also noticed some inaccuracies. So
far I've chalked it up to lag in the API data. Would be nice if the
data was a bit more reliable.
Dusty
On Oct 10, 7:03 pm, Steven Bristol <[EMA
You need to send a request that uses HTTP Basic authentication. I'm
sure you can find examples of doing so in many Flex references.
--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron
On Mon, Oct 13, 2008 at 2:24 AM, abhishek <[EMAIL PROTECTED]> wrote:
>
> i want to
I too have been having some issues with connecting to anything protected by
HTTP Basic Authentication in twitter. What I have found is kind of a
bummer:
1 - The 'Authorized' http header was removed from a version of Flash Player
(I believe 9.0105 ?), but then it was added back.
2 - Now the Author
Hi Stephen,
I am relatively new to the API, having only just started looking at it
yesterday, but I believe that the friends and followers lists are limited to
100 of the most recent updates. Depending upon how many followers or friends
there are, you can append '?page=2' to the URL being called.
AIR is not bound by the same cross-site request restrictions that the
Flash Player plugin is, so the situation is a little different.
crossdomain.xml was open wider, but security issues necessitated the
lockdown (check the archives). I doubt that will be changing soon. A
server-based proxy is you
abhishek wrote:
> url="http://twitter.com/direct_messages/new.format";
You need to replace 'format' with your desired result format, either
'xml' or 'json'.
-Matt
We have an open issue for that. Please star it to receive updates
about its progress:
http://code.google.com/p/twitter-api/issues/detail?id=5
On Thu, Oct 9, 2008 at 10:21 PM, DustyReagan <[EMAIL PROTECTED]> wrote:
>
> Hi Twitter, Alex, all,
>
> Would it be possible to get a user's following_c
It's not really the convention of REST APIs to provide WADL/WSDL, but
it's something we'll consider for the next major release of the API.
On Thu, Oct 9, 2008 at 8:14 PM, jim.renkel <[EMAIL PROTECTED]> wrote:
>
> Lukas,
>
> Thank you for the pointer to and the effort put into creating the WADL
>
I suppose I wouldn't hate it if you guys did it, but its of no
interest to me, and the API has been very popular without it (perhaps
because it's simple enough to not require such conventions).
--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron
On Mon, Oct 13, 2008
On Oct 13, 9:46 am, "Ross Tweedie" <[EMAIL PROTECTED]> wrote:
> Hi Stephen,
>
> I am relatively new to the API, having only just started looking at it
> yesterday, but I believe that the friends and followers lists are limited to
> 100 of the most recent updates. Depending upon how many follower
SoapUI's recently released, in-beta, RESTful harness looks for WADL ... and
that's not the only fairly mainstream place/service/app that seems to be
talking WADL these days. It's growing.
--Andy Badera
On Mon, Oct 13, 2008 at 1:52 PM, Alex Payne <[EMAIL PROTECTED]> wrote:
>
> It's not really th
We only honor "since" dates from the last 24 hours. That said,
nothing has changed with that method to my knowledge.
On Fri, Oct 10, 2008 at 12:31 AM, Enlai <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> Anyone know why this isn't working?
>
> http://twitter.com/direct_messages.xml?since=Tue%2C+27+M
I'm sitting down with @mzsanford this week to spec out what we're
calling the "API Service" internally, the next version of the Twitter
API. We're going to have a number of questions that we want your
feedback on, and this is the first.
Currently, the URL to which you POST to update a user's sta
If we really get to pick from a clean slate, I'd say:
POST http://api.twitter.com/1/users/bob/statuses/?format=xml
POST http://api.twitter.com/1/users/bob/statuses/?format=atom
POST http://api.twitter.com/1/users/bob/statuses/?format=json
But the current way of posting to the global status
I prefer the latter - especially as this has more context (to me) and is
alot more friendly.
On Tue, Oct 14, 2008 at 1:11 PM, Alex Payne <[EMAIL PROTECTED]> wrote:
>
> POST http://api.twitter.com/1/statuses.xml
>
> ... or:
>
> POST http://api.twitter.com/1/users/bob/statuses.xml
>
> The differe
On Mon, Oct 13, 2008 at 5:22 PM, DeWitt Clinton <[EMAIL PROTECTED]> wrote:
>
> But the current way of posting to the global status pool isn't entirely
> non-RESTful, it's just a little less discoverable. Because I'd also expect
> these two calls to be equivalent:
>
> GET http://api.twitter.com
I've pushed out TTYtter 0.9.0 tonight, which is a large update to the TTYtter
pure Perl command line client and platform. This version not only corrects
several bugs, but also adds API rate limit polling and autothrottling, URL
shortening, readline terminal support (for cursor key editing, TAB com
Oh nice! Starred.
Thanks!
On Oct 13, 12:40 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> We have an open issue for that. Please star it to receive updates
> about its progress:
>
> http://code.google.com/p/twitter-api/issues/detail?id=5
>
>
>
> On Thu, Oct 9, 2008 at 10:21 PM, DustyReagan <[EM
19 matches
Mail list logo
