Re: /statuses/user_timeline.format missing in action?
You entirely right Chris. The onus is on us. I'll get this fixed up tomorrow. Sorry to anyone who lost time on this bug! On Mon, Oct 27, 2008 at 7:10 PM, Chris Thompson <[EMAIL PROTECTED]> wrote: > I am the developer of Net::Twitter. > > Or, at least, I was before I handed it off because I grew tired of trying to > keep up with the foibles of the API. But, since the new guy hasn't released > anything, my name is still on the most recent version. So I get emails from > people, and questions on irc.perl.org about this. > > The problem in this case lies squarely on Twitter's side. > > Alex says: > >>Are you quite sure that you're making the request authenticated? It >>will return a 404 if it can't authenticate you, because that URL >>doesn't specify a user ID to retrieve a timeline for and thus assumes >>that you want the timeline for the requesting user. > > This is not how HTTP Auth works. > > The correct handshake for a URL that needs Auth is: > > 1) I request, with no WWW-Authenticate: header > 2) Server responds with a 401: Unauthorized and a WWW-Authenticate header > containing the realm > 3) I re-request with the WWW-Authenticate header containing user/pass > 4) Server decides that auth header is good, responds with a 200, or decides > it's bad and goes back to #2 > > Net::Twitter uses perl's libwww (LWP) which, in turn, implements the HTTP > protocol to spec. It doesn't send the WWW-Authenticate header until it sees > a 401. This is a specific part of HTTP as defined in RFC2617. > > If you think about it in terms of a browser like firefox, the browser CAN'T > send an auth header until it is told it needs one, and it puts up an auth > popup with the Realm listed that it got from the 401. > > LWP is doing the right thing, Twitter simply isn't asking for the auth. > > If you use curl or wget from the command line to hit the user_timeline url, > it works. The reason for this is, you specify user and pass on the command > line and both curl or wget just jam the WWW-Authenticate header in there > whether it ever gets asked for it or not, violating RFC. > > Same with Matt Sanford's perl using authorization_basic. This is not part of > LWP::UserAgent, but part of HTTP::Headers and what it does is force the > WWW-Authorize header into the request, always-on, just like curl and wget, > and yet again violating the RFC. > > LWP is only "being finicky" if by finicky you mean "Implementing RFC2617 as > written". > > I hate to be a pest on this, but the credentials code in Net::Twitter hasn't > changed at all since Net::Twitter 1.0.0 way back in March of 2007. You guys > are doing the right thing everywhere except user_timeline. If you had it > throw the 401 first, you'd get the auth. 404's just flat wrong here. > > -- > > Chris Thompson > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: /statuses/user_timeline.format missing in action?
I'm experiencing a similar issue with my Dashboard Twitter client using XMLHttpRequest. I'm using JSON as my format and receive a "Not Found" response when requesting the authenticating user's timeline. I pass the user credentials as part of the URL. ie: http://username:[EMAIL PROTECTED]/statuses/user_timeline.json?count=1 Any ideas why this would be happening? I see I'm not the only one. Thanks, Frank On Oct 27, 10:10 pm, "Chris Thompson" <[EMAIL PROTECTED]> wrote: > I am the developer of Net::Twitter. > > Or, at least, I was before I handed it off because I grew tired of trying to > keep up with the foibles of the API. But, since the new guy hasn't released > anything, my name is still on the most recent version. So I get emails from > people, and questions on irc.perl.org about this. > > The problem in this case lies squarely on Twitter's side. > > Alex says: > > >Are you quite sure that you're making the request authenticated? It > >will return a 404 if it can't authenticate you, because that URL > >doesn't specify a user ID to retrieve a timeline for and thus assumes > >that you want the timeline for the requesting user. > > This is not how HTTP Auth works. > > The correct handshake for a URL that needs Auth is: > > 1) I request, with no WWW-Authenticate: header > 2) Server responds with a 401: Unauthorized and a WWW-Authenticate header > containing the realm > 3) I re-request with the WWW-Authenticate header containing user/pass > 4) Server decides that auth header is good, responds with a 200, or decides > it's bad and goes back to #2 > > Net::Twitter uses perl's libwww (LWP) which, in turn, implements the HTTP > protocol to spec. It doesn't send the WWW-Authenticate header until it sees > a 401. This is a specific part of HTTP as defined in RFC2617. > > If you think about it in terms of a browser like firefox, the browser CAN'T > send an auth header until it is told it needs one, and it puts up an auth > popup with the Realm listed that it got from the 401. > > LWP is doing the right thing, Twitter simply isn't asking for the auth. > > If you use curl or wget from the command line to hit the user_timeline url, > it works. The reason for this is, you specify user and pass on the command > line and both curl or wget just jam the WWW-Authenticate header in there > whether it ever gets asked for it or not, violating RFC. > > Same with Matt Sanford's perl using authorization_basic. This is not part of > LWP::UserAgent, but part of HTTP::Headers and what it does is force the > WWW-Authorize header into the request, always-on, just like curl and wget, > and yet again violating the RFC. > > LWP is only "being finicky" if by finicky you mean "Implementing RFC2617 as > written". > > I hate to be a pest on this, but the credentials code in Net::Twitter hasn't > changed at all since Net::Twitter 1.0.0 way back in March of 2007. You guys > are doing the right thing everywhere except user_timeline. If you had it > throw the 401 first, you'd get the auth. 404's just flat wrong here. > > -- > > Chris Thompson
Re: /statuses/user_timeline.format missing in action?
I am the developer of Net::Twitter. Or, at least, I was before I handed it off because I grew tired of trying to keep up with the foibles of the API. But, since the new guy hasn't released anything, my name is still on the most recent version. So I get emails from people, and questions on irc.perl.org about this. The problem in this case lies squarely on Twitter's side. Alex says: >Are you quite sure that you're making the request authenticated? It >will return a 404 if it can't authenticate you, because that URL >doesn't specify a user ID to retrieve a timeline for and thus assumes >that you want the timeline for the requesting user. This is not how HTTP Auth works. The correct handshake for a URL that needs Auth is: 1) I request, with no WWW-Authenticate: header 2) Server responds with a 401: Unauthorized and a WWW-Authenticate header containing the realm 3) I re-request with the WWW-Authenticate header containing user/pass 4) Server decides that auth header is good, responds with a 200, or decides it's bad and goes back to #2 Net::Twitter uses perl's libwww (LWP) which, in turn, implements the HTTP protocol to spec. It doesn't send the WWW-Authenticate header until it sees a 401. This is a specific part of HTTP as defined in RFC2617. If you think about it in terms of a browser like firefox, the browser CAN'T send an auth header until it is told it needs one, and it puts up an auth popup with the Realm listed that it got from the 401. LWP is doing the right thing, Twitter simply isn't asking for the auth. If you use curl or wget from the command line to hit the user_timeline url, it works. The reason for this is, you specify user and pass on the command line and both curl or wget just jam the WWW-Authenticate header in there whether it ever gets asked for it or not, violating RFC. Same with Matt Sanford's perl using authorization_basic. This is not part of LWP::UserAgent, but part of HTTP::Headers and what it does is force the WWW-Authorize header into the request, always-on, just like curl and wget, and yet again violating the RFC. LWP is only "being finicky" if by finicky you mean "Implementing RFC2617 as written". I hate to be a pest on this, but the credentials code in Net::Twitter hasn't changed at all since Net::Twitter 1.0.0 way back in March of 2007. You guys are doing the right thing everywhere except user_timeline. If you had it throw the 401 first, you'd get the auth. 404's just flat wrong here. -- Chris Thompson
Re: Search API 400 Error
using, for example, http://search.twitter.com/search.json?q=term seems to be totally random if it returns 400 or success... although one potential weird thing is I wrote a recursive function that would keep trying until it returns a success, and it kept returning 400. But if I just hit it normally, then it has a better chance of success. thanks, w On Oct 27, 8:47 am, Matt <[EMAIL PROTECTED]> wrote: > Hi there, > > It doesn't sound like the search API rate limiting, as that returns > a different response code (503) along with an error message. What URL > are you using when you get the 400? > > Thanks; > — Matt Sanford > > On Oct 26, 11:29 am, wcrtr <[EMAIL PROTECTED]> wrote: > > > > > > > Just doing some simple requests to the search API, using json as a > > response format without any callback function, just a straight > > request. I'm not sure what the exact rate limiting procedures are for > > the search API (since the wiki says it doesn't rate limit under most > > circumstances...), but it seems pretty arbitrary that sometimes the > > request will come back with results no problem, and other times it > > will throw the 400 error. Any ideas?
Re: Does direct_messages (Twitter API) support RFC 1123/RFC 822 date time format
Your date does not appear to be properly CGI-encoded:
>> Date.parse(CGI.unescape("Sun%2C+26+Oct+22%3:55%3:48+000+2008"))
=> Mon, 26 Oct 0022
That's what Ruby in our development environment thinks your date is.
Those "%3"s might be the culprit.
On Mon, Oct 27, 2008 at 2:01 PM, Kris <[EMAIL PROTECTED]> wrote:
>
> I am aware of the example in the documentation.
> Thanks for pointing it out and I apologize for not mentioning before
> that I had tried the format listed in the documentation.
>
> For example:
> $this->twitterHost .= "direct_messages.xml?since=Sun%2C+26+Oct
> +22%3:55%3:48+000+2008";
> results in error number 502 (server busy) and "Twitter is over
> capacity" message.
> Not sure why the API does not throw a format error?
>
> I saw a post (http://groups.google.com/group/twitter-development-talk/
> browse_thread/thread/e97f02c8b8012fb5) which mentions that the API
> conforms to RFC1123 but that does not work either.
>
> Any thoughts?
>
> Thanks
>
> On Oct 27, 4:35 pm, "Damon Clinkscales" <[EMAIL PROTECTED]> wrote:
>> On Mon, Oct 27, 2008 at 1:48 PM, Kris <[EMAIL PROTECTED]> wrote:
>>
>> > The API documentation does not clearly list the date format for
>> > obtaining direct_messages sent to a user (within the specified date/
>> > time window).
>> > I am using RFC 1123/822 format but do not get any messages sent with
>> > in the specified date/time window:
>>
>> > For Example:
>>
>> > direct_messages.xml?since=".urlencode("Sun, 26 Oct 2008 22:00:00 EST")
>>
>> > (does not return any messages or errors.)
>>
>> > What is the correct date/time format? Has anyone used this
>> > successfully?
>>
>> > Thanks
>>
>> Personally, I use since_id.
>>
>> But here's the
>> documentation:http://apiwiki.twitter.com/REST+API+Documentation#DirectMessageMethods
>>
>> which contains this example:
>>
>> # since. Optional. Narrows the resulting list of direct messages to
>> just those sent after the specified HTTP-formatted date, up to 24
>> hours old. The same behavior is available by setting the
>> If-Modified-Since parameter in your HTTP request.
>>
>> Ex:http://twitter.com/direct_messages/sent.xml?since=Tue%2C+27+Mar+2007+...
>>
>> -damon
>>
>> --http://twitter.com/damon- Hide quoted text -
>>
>> - Show quoted text -
>
--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x
Re: Does direct_messages (Twitter API) support RFC 1123/RFC 822 date time format
I am aware of the example in the documentation.
Thanks for pointing it out and I apologize for not mentioning before
that I had tried the format listed in the documentation.
For example:
$this->twitterHost .= "direct_messages.xml?since=Sun%2C+26+Oct
+22%3:55%3:48+000+2008";
results in error number 502 (server busy) and "Twitter is over
capacity" message.
Not sure why the API does not throw a format error?
I saw a post (http://groups.google.com/group/twitter-development-talk/
browse_thread/thread/e97f02c8b8012fb5) which mentions that the API
conforms to RFC1123 but that does not work either.
Any thoughts?
Thanks
On Oct 27, 4:35 pm, "Damon Clinkscales" <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 27, 2008 at 1:48 PM, Kris <[EMAIL PROTECTED]> wrote:
>
> > The API documentation does not clearly list the date format for
> > obtaining direct_messages sent to a user (within the specified date/
> > time window).
> > I am using RFC 1123/822 format but do not get any messages sent with
> > in the specified date/time window:
>
> > For Example:
>
> > direct_messages.xml?since=".urlencode("Sun, 26 Oct 2008 22:00:00 EST")
>
> > (does not return any messages or errors.)
>
> > What is the correct date/time format? Has anyone used this
> > successfully?
>
> > Thanks
>
> Personally, I use since_id.
>
> But here's the
> documentation:http://apiwiki.twitter.com/REST+API+Documentation#DirectMessageMethods
>
> which contains this example:
>
> # since. Optional. Narrows the resulting list of direct messages to
> just those sent after the specified HTTP-formatted date, up to 24
> hours old. The same behavior is available by setting the
> If-Modified-Since parameter in your HTTP request.
>
> Ex:http://twitter.com/direct_messages/sent.xml?since=Tue%2C+27+Mar+2007+...
>
> -damon
>
> --http://twitter.com/damon- Hide quoted text -
>
> - Show quoted text -
Re: /statuses/user_timeline.format missing in action?
Thanks Matt
I think when you said "The LWP library is finicky about
authentication", you nailed it. There's more than one way to tell LWP
how to authenticate, and calling 'basic_authorization' on the request
object seems to make Twitter happy, whereas calling 'credentials' on
the user agent object apparently doesn't. Net::Twitter uses
'credentials' rather than 'basic_authorization'. I'm not sure I want
to do the necessary LWP spelunking to figure out what the difference
is between the two approaches as far as the consumer is concerned.
Curiously, the 'credentials' technique appears to have worked in the
past, still works for 'friends_timeline' on Twitter, and works for
both 'friends_timeline' and 'user_timeline' on the Laconica
implementation of the Twitter API. Go figure.
One thing I notice: if you send the wrong credentials to
'user_timeline', Twitter gives back a 404 Not Found code (rather than
401 Not Authorized). If you send the wrong credentials to
'friends_timeline', Twitter gives back a 401 Not Authorized. This
apparent inconsistency may be a deliberate choice on your part,
though.
I'm going to switch our application code over to using raw LWP rather
than Net::Twitter for the small number of calls we need, and that will
probably take care of it.
Thanks to you and Alex for your help,
Angus
On Oct 22, 5:33 pm, Matt Sanford <[EMAIL PROTECTED]> wrote:
> Hi Angus,
>
> Back in the day I was known to write some Perl so I took a crack at
> user_timeline. The following works fine for me:
>
> use LWP::UserAgent;
> use HTTP::Request;
>
> my $ua = LWP::UserAgent->new;
> my $req=HTTP::Request->new(GET => "http://twitter.com/statuses/
> user_timeline.json");
> $req->authorization_basic('username here', 'password here');
> print $ua->request($req)->as_string
>
> Or, the exact command I used:
>
> perl -MLWP::UserAgent -e '$ua = LWP::UserAgent->new;
> $req=HTTP::Request->new(GET => "http://twitter.com/statuses/
> user_timeline.json"); $req->authorization_basic($ARGV[0],$ARGV[1]);
> print $ua->request($req)->as_string' USERNAME PASSWORD
>
> Where USERNAME and PASSWORD are your user information. The LWP
> library is finicky about authentication.
>
> — Matt
>
> On Oct 22, 1:34 pm, angusmci <[EMAIL PROTECTED]> wrote:
>
> > Thanks for your answer.
>
> > I decided to bypass the Net::Twitter library altogether, and just talk
> > to Twitter directly using LWP (Perl's web programming library).
>
> > I sent two requests to Twitter, one for "http://twitter.com/statuses/
> > user_timeline.json", and one for "http://twitter.com/statuses/
> > friends_timeline.json". In each case, I sent Twitter valid credentials
> > (i.e. the username and password that I use to log in to Twitter). I
> > set the LWP user agent up in exactly the same way each case.
>
> > The request for 'user_timeline' returned 404 Not Found; the request
> > for 'friends_timeline' returned a list of updates from people I'm
> > following.
>
> > If the authentication credentials I'm sending weren't valid, then the
> > request for 'friends_timeline' should return a 401 error. The fact
> > that it didn't suggests that the test script is authenticating it
> > successfully at least in some cases.
>
> > I'm sorry to keep bothering you with this, but it really looks as if
> > some parts - but only some parts - of the Twitter API have a
> > mysterious prejudice against Perl ('curl' works fine). I'll try with
> > Ruby and Python test scripts and see if that makes any difference.
>
> > Angus
>
> > On Oct 21, 2:20 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
>
> > > > Are there any headers or arguments that are mandatory for
> > > > 'user_timeline' that are not required for other, similar API
> > > > functions?
>
> > > No, none. If you want the user timeline for the authenticating user,
> > > you need to provide authentication. If you want the user timeline for
> > > another user, you must specify it as part of the URL. That's all
> > > there is to it.
>
> > > > Thanks, Angus
>
> > > > On Oct 20, 9:10 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> > > >> Are you quite sure that you're making the request authenticated? It
> > > >> will return a 404 if it can't authenticate you, because that URL
> > > >> doesn't specify a user ID to retrieve a timeline for and thus assumes
> > > >> that you want the timeline for the requesting user.
>
> > > >> On Mon, Oct 20, 2008 at 11:48 AM, angusmci <[EMAIL PROTECTED]> wrote:
>
> > > >> > I don't have a way currently to monitor what's actually going out
> > > >> > over
> > > >> > the wire, but I've scattered Data::Dumper calls through the
> > > >> > Net::Twitter code to inspect the data structures used by the libwww
> > > >> > user agent. According to that, Net::Twitter is requesting:
>
> > > >> > http://twitter.com/statuses/user_timeline.json?count=1&;
>
> > > >> > and it's sending the headers:
>
> > > >> > 'user-agent' => 'Net::Twitter/1.17 (PERL)',
> > > >> > 'x-twitter-client-version:' => '1.17',
> > > >> > 'x-twi
Re: whitelisting
I'll be approving requests made this weekend today. On Mon, Oct 27, 2008 at 1:49 PM, Yu-Shan Fung <[EMAIL PROTECTED]> wrote: > Hi all, > Does anyone know how long it takes to get an IP whitelisted? I submitted a > request yesterday. Not being able to make more than 70 requests an hour > makes development and testing impossible... > Thanks! > Yu-Shan > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
whitelisting
Hi all, Does anyone know how long it takes to get an IP whitelisted? I submitted a request yesterday. Not being able to make more than 70 requests an hour makes development and testing impossible... Thanks! Yu-Shan
Re: Does direct_messages (Twitter API) support RFC 1123/RFC 822 date time format
On Mon, Oct 27, 2008 at 1:48 PM, Kris <[EMAIL PROTECTED]> wrote:
>
> The API documentation does not clearly list the date format for
> obtaining direct_messages sent to a user (within the specified date/
> time window).
> I am using RFC 1123/822 format but do not get any messages sent with
> in the specified date/time window:
>
> For Example:
>
> direct_messages.xml?since=".urlencode("Sun, 26 Oct 2008 22:00:00 EST")
>
> (does not return any messages or errors.)
>
> What is the correct date/time format? Has anyone used this
> successfully?
>
> Thanks
Personally, I use since_id.
But here's the documentation:
http://apiwiki.twitter.com/REST+API+Documentation#DirectMessageMethods
which contains this example:
# since. Optional. Narrows the resulting list of direct messages to
just those sent after the specified HTTP-formatted date, up to 24
hours old. The same behavior is available by setting the
If-Modified-Since parameter in your HTTP request.
Ex:
http://twitter.com/direct_messages/sent.xml?since=Tue%2C+27+Mar+2007+22%3A55%3A48+GMT
-damon
--
http://twitter.com/damon
Re: Search API 400 Error
Hello again, I searched our logs for 'term', 'brown' and 'curl' and couldn't find any references to your searches where there was an error returned. We do have a load balancer that will return 400 if it receives an in valid HTTP request. The most common causes are very long URLs or unescaped spaces in the URL itself. Can you please run curl with a -v and send along the output of the problem request? If nothing else this will give me a full trace to work from. Thanks — Matt Sanford On Oct 27, 9:48 am, wcrtr <[EMAIL PROTECTED]> wrote: > using, for example, > > http://search.twitter.com/search.json?q=term > > seems to be totally random if it returns 400 or success... although > one potential weird thing is I wrote a recursive function that would > keep trying until it returns a success, and it kept returning 400. > But if I just hit it normally, then it has a better chance of success. > > thanks, > w > > On Oct 27, 8:47 am, Matt <[EMAIL PROTECTED]> wrote: > > > Hi there, > > > It doesn't sound like the search API rate limiting, as that returns > > a different response code (503) along with an error message. What URL > > are you using when you get the 400? > > > Thanks; > > — Matt Sanford > > > On Oct 26, 11:29 am, wcrtr <[EMAIL PROTECTED]> wrote: > > > > Just doing some simple requests to the search API, using json as a > > > response format without any callback function, just a straight > > > request. I'm not sure what the exact rate limiting procedures are for > > > the search API (since the wiki says it doesn't rate limit under most > > > circumstances...), but it seems pretty arbitrary that sometimes the > > > request will come back with results no problem, and other times it > > > will throw the 400 error. Any ideas?
Does direct_messages (Twitter API) support RFC 1123/RFC 822 date time format
The API documentation does not clearly list the date format for
obtaining direct_messages sent to a user (within the specified date/
time window).
I am using RFC 1123/822 format but do not get any messages sent with
in the specified date/time window:
For Example:
direct_messages.xml?since=".urlencode("Sun, 26 Oct 2008 22:00:00 EST")
(does not return any messages or errors.)
What is the correct date/time format? Has anyone used this
successfully?
Thanks
Re: Search API 400 Error
using the standard search api url... http://search.twitter.com/search.json?q=brown couple things: • only seem to get the 400 when I make the query using curl, and the 400 shows up randomly (it seems), whereas often times the search request works without problems • I tried using a little function that would make the request, check for the 400 error, and if it showed up, then try and make the request again after a 5 second delay. When using this function, if the 400 error showed up, the subsequent requests would _all_ be 400 errors, vs. the ~ 50% success rate when making the call normally. thanks, w On Oct 27, 8:47 am, Matt <[EMAIL PROTECTED]> wrote: > Hi there, > > It doesn't sound like the search API rate limiting, as that returns > a different response code (503) along with an error message. What URL > are you using when you get the 400? > > Thanks; > — Matt Sanford > > On Oct 26, 11:29 am, wcrtr <[EMAIL PROTECTED]> wrote: > > > Just doing some simple requests to the search API, using json as a > > response format without any callback function, just a straight > > request. I'm not sure what the exact rate limiting procedures are for > > the search API (since the wiki says it doesn't rate limit under most > > circumstances...), but it seems pretty arbitrary that sometimes the > > request will come back with results no problem, and other times it > > will throw the 400 error. Any ideas?
Re: Notification Methods
Twitter has two levels of preferences when it comes to following someone's updates. If you follow a user (in the nomenclature of the API, befriend them), you'll see their updates on the web and in API clients. If you turn notifications on for them with the method that you mentioned, you'll get their updates to your mobile device if you've set one up. On Mon, Oct 27, 2008 at 12:47 AM, Clifton <[EMAIL PROTECTED]> wrote: > > Sorry if this is a duplicate message... > > I'm new to this and and could use some input. Can anyone help me > understand this: > > > Notification Methods > > follow > > Enables notifications for updates from the specified user to the > authenticating user. Returns the specified user when successful. > > URL:http://twitter.com/notifications/follow/id.format > > Formats: xml, json > > Method(s): POST > > Parameters: > >* id. Required. The ID or screen name of the user to follow. > Ex: > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Search API 400 Error
Hi there, It doesn't sound like the search API rate limiting, as that returns a different response code (503) along with an error message. What URL are you using when you get the 400? Thanks; — Matt Sanford On Oct 26, 11:29 am, wcrtr <[EMAIL PROTECTED]> wrote: > Just doing some simple requests to the search API, using json as a > response format without any callback function, just a straight > request. I'm not sure what the exact rate limiting procedures are for > the search API (since the wiki says it doesn't rate limit under most > circumstances...), but it seems pretty arbitrary that sometimes the > request will come back with results no problem, and other times it > will throw the 400 error. Any ideas?
Re: Question: Notify user of event?
> Yeah Cameron, I was afraid of that. :( dang it. > I'm confused about what this does. Can anyone help me understand it? > My n00bness does not comprehend it: > Notification Methods > > follow > > Enables notifications for updates from the specified user to the > authenticating user. Returns the specified user when successful. > URL:http://twitter.com/notifications/follow/id.format AFAIK this is only for enabling mobile notifications for a user you already follow (e.g., getting tweets over SMS). -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- Male Macintosh geeks are so predictable. All we think about is X. --
Re: Question: Notify user of event?
Yeah, you're right. On Oct 26, 11:15 pm, Cameron Kaiser <[EMAIL PROTECTED]> wrote: > > Is it possible to send a notification to a twitter user? Direct > > message or email or anything? > > You can always send a direct message to a user you have a following > relationship with, but if you mean an arbitrary user, I'm not aware of > any such method (and it would be ripe for abuse if one existed). > > -- > personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* [EMAIL PROTECTED] > -- Got Mole problems? Call Avogadro at 6.02 x 10^23. > --
Re: Question: Notify user of event?
Yeah Cameron, I was afraid of that. :( dang it. I'm confused about what this does. Can anyone help me understand it? My n00bness does not comprehend it: Notification Methods follow Enables notifications for updates from the specified user to the authenticating user. Returns the specified user when successful. URL:http://twitter.com/notifications/follow/id.format Formats: xml, json Method(s): POST Parameters: * id. Required. The ID or screen name of the user to follow. Ex: On Oct 26, 11:15 pm, Cameron Kaiser <[EMAIL PROTECTED]> wrote: > > Is it possible to send a notification to a twitter user? Direct > > message or email or anything? > > You can always send a direct message to a user you have a following > relationship with, but if you mean an arbitrary user, I'm not aware of > any such method (and it would be ripe for abuse if one existed). > > -- > personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* [EMAIL PROTECTED] > -- Got Mole problems? Call Avogadro at 6.02 x 10^23. > --
Notification Methods
Sorry if this is a duplicate message... I'm new to this and and could use some input. Can anyone help me understand this: Notification Methods follow Enables notifications for updates from the specified user to the authenticating user. Returns the specified user when successful. URL:http://twitter.com/notifications/follow/id.format Formats: xml, json Method(s): POST Parameters: * id. Required. The ID or screen name of the user to follow. Ex:
Re: Twitter AS3 API - Connection Problem
Hi,
Flash player has a security model due to which your flash movie can't
connect to any site other than from which it is loaded. For this, you will
have to make few configurations on the site to which flash movie wants to
connect. flash player security topics will help you.
- shahid
On Sun, Oct 26, 2008 at 8:06 PM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> Hi guys,
>
> import twitter.api.Twitter;
> import twitter.api.events.TwitterEvent
>
> var twitter:Twitter = new Twitter();
> twitter.loadUserTimeline("flasherblog");
> twitter.addEventListener("onUserTimelineResult",return_);
>
> function return_(e:TwitterEvent) {
>twit_txt.text = e.data[0].text
> }
>
> This my simple Action Script 3.0 code. When I test my movie I can see
> my last status. But when I try to test this in host I can't see
> anything?
>
> How can I solve this?
> http://www.flasherblog.com/deneme/twitter.html
>
> Thanks.
>
