date:20090514

On Wed, May 13, 2009 at 22:23, Coonay fla...@gmail.com wrote:

   is apiwiki.twitter.com  just a workplace for twitter.com api hosted
 by pbworks?


Yes.



  so it's the problem with pbwork.com,not with twitter.com?


Probably.


-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: replies blog post clarification...

When I changed my username from @poseurtech to @abraham all of the @replies
continued to point to my user_id. My assumption is you will still see the
tweet as the @reply seems to be tied to accounts not usernames.

On Wed, May 13, 2009 at 21:37, Zac Bowling zbowl...@gmail.com wrote:


 Riddle me this, what happens in this scenario:

 I'm following user A and user B
 1. User A sends an @reply to user B.
 2. User B changes his name.
 3. Tweet is going to user B's old name.

 Will I see the tweet?



 Zac Bowling




 On Wed, May 13, 2009 at 6:26 PM, Doug Williams d...@twitter.com wrote:
  Non-confirmed @replies will still be seen by all. Confirmed @replies, or
  those with in_reply_to_status_id set, will only be seen by mutual
 followers.
 
  Thanks,
  Doug
  --
 
  Doug Williams
  Twitter Platform Support
  http://twitter.com/dougw
 
 
 
 
  On Wed, May 13, 2009 at 3:25 PM, Steve Brunton sbrun...@gmail.com
 wrote:
 
  from @biz and his post :
 
  First, we're making a change such that any updates beginning with
  @username (that are not explicitly created by clicking on the reply
  icon) will be seen by everyone following that account.
 
  for us folks that fiddle with the API. Can we read this as Tweets that
  start with @username, but don't have the in_reply_to_status_id
  parameter set?
 
  -steve
 
 




-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, WI, United States

[twitter-dev] Re: New Public Streaming API Resource - Follow

2009-05-14 Thread Marco Kaiser

2009/5/13 John Kalucki jkalu...@gmail.com


 I'll attempt to answer these questions, but I can only do so with some
 speculation and humble ignorance.

 1) OAuth allows clients to authenticate with the Twitter REST API via
 third-party services. These services should not also need to interact
 with the Streaming API on a per client basis. Instead, the service
 should establish a single query that satisfies all clients' needs.
 This may not be practical in all cases, but I suspect we can
 approximate the desired behavior with the current set of primitives.


John,

in your original mail on this thread you wrote:

For example, a desktop client could simulate a user's /home timeline,
minus private updates and mentions, via the /follow resource.
Continuous polling would no longer be necessary or desired.

This doesn't match the scenario from above, where you refer to using the
streaming endpoints from a single query per service. So still the question
how a desktop client that is trying to do OAuth and not ask users for their
passwords can use the streaming API is open - or are you saying that those
clients just cannot use it? I think this would discourage many desktop
developers from even looking into integrating OAuth for their clients, which
as I assume can't be in twitter's interest.


 2) There are no immediate plans to support HTTPS, mainly because we're
 not really trying to keep the data private. Also, and I am probably
 totally wrong here, I don't think we use HTTPS on the main WWW site or
 on the REST API, so this doesn't make things much worse than they
 already are. A possible workaround would be for sensitive service to
 create an account just for streaming. Should the password be
 compromised, there's only a denial of service risk and no further
 risk.


Again, this doesn't help much in the context of desktop app use, as it would
have to use it's authenticated user's credentials. Clients just shouldn't
send a cleartext password over an unecrypted connection IMO.

Marco



 On May 13, 11:18 am, Marco Kaiser kaiser.ma...@gmail.com wrote:
  John,
 
  this looks pretty interesting!
 
  Two questions:
 
  1) you are requiring to send a username and password for Basic Auth - how
  does that map to apps / services using OAuth, as they won't have access
 to a
  user's passwords? (and related, how does this fit into your general
 roadmap
  to move everything to OAuth?)
 
  2) the docs only mention http as a protocol, not https. In combination
 with
  requiring passwords, only making http available seems quite unsecure. Any
  plans to also support https soon (or any other mechanism which gives
 better
  security?)
 
  Thanks,
  Marco
 
  2009/5/13 John Kalucki jkalu...@gmail.com
 
 
 
   Chad,
 
   Yes, I think this is called POSTDATA in browsers. I don't recall what
   the actual name of this part of the HTTP protocol is, but it's the
   body section after the headers.
 
   I corrected the file name error. Thanks.
 
   -John
 
   On May 12, 8:49 pm, Chad Etzel jazzyc...@gmail.com wrote:
Hi John,
 
/follow looks very interesting.  Since you're asking for feedback
 
I'm copying the follow parameter example documentation:
 
Example: Create a file called 'follow' that contains, exactly and
excluding the quotation marks: follow=12 13 15 16 20 87. Execute:
curl -d @followinghttp://stream.twitter.com/follow.json
-uAnyTwitterUser:Password.You will receive JSON updates from Jack
 Biz,
Crystal, Ev, Krissy, but not from Jeremy, as he's a private user.
 
I'm assuming that follow is just a POSTDATA variable in the normal
case (you're just using curl's file posting ability in the example)?
 
In the example, should the file be called following instead of
follow (since you are using -d @following in the curl line)?
 
Thanks,
-Chad
 
On Tue, May 12, 2009 at 11:24 PM, John Kalucki jkalu...@gmail.com
   wrote:
 
 Note: The Streaming API is currently under a limited alpha test,
 details below.
 
 The /follow Streaming API resource is now publicly available.
 This
 resource streams near-real-time public updates posted by an
 arbitrary
 set of users. Streaming by user_id may be interesting to a variety
 of
 developers who wish to provide a nearly instantaneous experience
 without the drawbacks of continuous polling, polling rate limits,
 auto-
 following and follow limits.
 
 For example, a desktop client could simulate a user's /home
 timeline,
 minus private updates and mentions, via the /follow resource.
 Continuous polling would no longer be necessary or desired. Upon
 receipt of a new streamed message, the REST API may be periodically
 polled to back-fill mentions, private statuses and other updates
 not
 available via the Streaming API.
 
 This stream may also be interesting to service developers that
 follow
 their subscribers solely to receive their replies or for data
 mining
 purposes.

[twitter-dev] Re: API Changes for May 11, 2009

2009-05-14 Thread rlamfink


Using the blocks/blocking API, the page parameter has no effect. I
always get the first page, no matter what page number is in the URL
parameter. Also I don't get just 20 users in the list as the
documentation says. I get more.

[twitter-dev] Rate Limits - statuses/friends vs statuses/followers

2009-05-14 Thread TweetClean


I have setup an IP whitelist account on my development machine.  In
order to work on throttling, I have a test machine that is using a
different IP and I am using a different twitter account.  I am
developing this application in Visual Basic.net from visual studio
2008.

When I perform a request for statuses/friends - I see the Remaining
Hits decrement by 1 for each call as it states in the API wiki

When I perform a request for the statuses/followers - I see no
Decrement of the Remaining Hits as stated in the API wiki.

The main reason I decided to build TweetClean was to provide a windows
desktop application that would allow users to compare their followers
to the people they follow.  The second reason was to allow users to
evaluate who they were following based upon how many days it had been
since those users last tweeted.  The application will be heavily
relying on proper throttling.  One of my beta testers has over 33,000
followers and the around the same number he is following.

I want to insure that I am throttling the application correctly.  Does
the API statuses/followers call actually decrement the Remaining API
hits by one and I am getting an invalid response from the account/
rate_limit_status call or has the API decrement been removed for the
statuses/followers API call.  I suppose the third condition that could
exist is that there is a bug and twitter does wish to have the API
Remaining Hits decremented for the statuses/follower API call and it
is just not decrementing correctly.

I appreciate any input on this subject.

Regards,

TweetClean
Robert A. Cristello

[twitter-dev] Re: oauth just to post status

2009-05-14 Thread surya sravanthi


hi,

I forgot to mention that I am using Twitter4j-2.0.3 version in jar.
?This does not contain twitter.setAccessToken(accessToken); in its
file. So, I am facing a problem in assigning stored(or say even for
the first time) accessToken to twiiter object...

Can you suggest me how to solve this problem

Surya Sravanthi

On Thu, May 14, 2009 at 11:28 AM, jmathai jmat...@gmail.com wrote:

 Create an application (http://twitter.com/oauth) and then post using
 your consumer key/secret.

 Blog posts if needed:
 http://www.jaisenmathai.com/blog/2009/03/31/how-to-quickly-integrate-with-twitters-oauth-api-using-php/
 http://www.jaisenmathai.com/blog/2009/04/30/letting-your-users-sign-in-with-twitter-with-oauth/

 On May 13, 8:03 pm, tayknight taykni...@gmail.com wrote:
 I meant to add, I want to use oauth for this so I get the 'via
 DummyOauthApp' line in the tweet.

 On May 13, 9:50 pm, tayknight taykni...@gmail.com wrote:

  Hi all. My app, once it gets going, is mainly going to post status
  updates as mentions to followers. For instance, the app, called
  DummyOauthApp will post a statuses/update like '@tayknight blah blah
  blah'.

  So, i don't need my app to authenticate itself  to oauth as tayknight,
  but as itself DummyOauthApp. Does this mean I need to generate an
  access token/secret pair for the app itself and continually reuse this
  pair to call statuses/update?

  Thanks.

[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged

2009-05-14 Thread John Kalucki


Damon,

Interesting use cases are starting to pop up!

For now, yes, the concurrent connection limit applies to all
resources. If you want streams for various sets of users, we'd ask
that you just set up one stream and multiplex all your requests over
the same connection. You'll have to do the demux on your end, but that
should be easy enough.

-John


On May 13, 11:40 pm, Damon P. Cortesi d.lifehac...@gmail.com
wrote:
 John,

 Do the concurrent connections apply to the birddog/shadow/follow feeds
 as well?

 I can see a use case where I might want to set up multiple connections
 to these services, i.e. I want to set up a stream for x,y and z users
 and another stream for p,q and r users.

 Is that a valid use of those streams?

 Thanks,

 dpc

 On May 9, 9:04 pm, John Kalucki jkalu...@gmail.com wrote:

  Note: The Streaming API is currently under a limited alpha test,
  details below.

  Multiple concurrent connections from the same account are discouraged
  on the Streaming API. Starting on or after the afternoon of Monday,
  May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce
  this policy. A later release will fully enforce this policy.
  Subsequent connections from the same account will cause previously
  established connections to be disconnected.

  In some cases, this might cause operational difficulties for
  developers who are using the restricted resources. For example, a
  developer's staging test might knock that developer's production /
  gardenhose feed offline. Non-production uses should connect to the /
  spritzer resource with a secondary account to avoid these conflicts.
  We may, on a case-by-case basis, grant exceptions to this policy as we
  work through the alpha test. We will attempt to balance ease-of-use,
  resource consumption and abuse prevention.

  -John Kalucki - Services, Twitter Inc.http://twitter.com/jkalucki

  Important Alpha Test Note:
  The Streaming API (akaHosebird) is currently under an alpha test. All
  developers using the Streaming API must tolerate possible unannounced
  and extended periods of unavailability, especially during off-hours,
  Pacific Time. New features, resources and policies are being deployed
  on very little, if any, notice. Any developer may experiment with the
  unrestricted resources and provide feedback via this list. Access to
  restricted resources is extremely limited and is only granted on a
  case-by-case basis after acceptance of an additional terms of service
  document. Documentation is 
  available:http://apiwiki.twitter.com/Streaming-API-Documentation.

[twitter-dev] Re: New Public Streaming API Resource - Follow

2009-05-14 Thread John Kalucki


Marco,

Once again, I beg patience with my ignorance of Twitter's larger
authentication plans.

For the time being, the primary use for Hosebird is delivering streams
to partners, data analyzers, and other developers looking to
experiment with statuses in a way that the purpose-built REST API
might not allow. For this case, basic auth is probably acceptable,
barely, as it is typically server to server. Desktop clients have much
greater exposure to man-in-the-middle snooping, so I fully appreciate
the concern about passwords.

It never occurred to me that OAuth might be a thing for the desktop.
In my experience, clients are mostly using basic auth, but it
certainly would be nice if that evolved. I think all I can say at this
point is, if streaming to the desktop becomes a Big Thing, we'll look
into adding a better authentication mechanism to the Streaming API.

-John


On May 14, 2:56 am, Marco Kaiser kaiser.ma...@gmail.com wrote:
 2009/5/13 John Kalucki jkalu...@gmail.com



  I'll attempt to answer these questions, but I can only do so with some
  speculation and humble ignorance.

  1) OAuth allows clients to authenticate with the Twitter REST API via
  third-party services. These services should not also need to interact
  with the Streaming API on a per client basis. Instead, the service
  should establish a single query that satisfies all clients' needs.
  This may not be practical in all cases, but I suspect we can
  approximate the desired behavior with the current set of primitives.

 John,

 in your original mail on this thread you wrote:

 For example, a desktop client could simulate a user's /home timeline,
 minus private updates and mentions, via the /follow resource.
 Continuous polling would no longer be necessary or desired.

 This doesn't match the scenario from above, where you refer to using the
 streaming endpoints from a single query per service. So still the question
 how a desktop client that is trying to do OAuth and not ask users for their
 passwords can use the streaming API is open - or are you saying that those
 clients just cannot use it? I think this would discourage many desktop
 developers from even looking into integrating OAuth for their clients, which
 as I assume can't be in twitter's interest.

  2) There are no immediate plans to support HTTPS, mainly because we're
  not really trying to keep the data private. Also, and I am probably
  totally wrong here, I don't think we use HTTPS on the main WWW site or
  on the REST API, so this doesn't make things much worse than they
  already are. A possible workaround would be for sensitive service to
  create an account just for streaming. Should the password be
  compromised, there's only a denial of service risk and no further
  risk.

 Again, this doesn't help much in the context of desktop app use, as it would
 have to use it's authenticated user's credentials. Clients just shouldn't
 send a cleartext password over an unecrypted connection IMO.

 Marco

  On May 13, 11:18 am, Marco Kaiser kaiser.ma...@gmail.com wrote:
   John,

   this looks pretty interesting!

   Two questions:

   1) you are requiring to send a username and password for Basic Auth - how
   does that map to apps / services using OAuth, as they won't have access
  to a
   user's passwords? (and related, how does this fit into your general
  roadmap
   to move everything to OAuth?)

   2) the docs only mention http as a protocol, not https. In combination
  with
   requiring passwords, only making http available seems quite unsecure. Any
   plans to also support https soon (or any other mechanism which gives
  better
   security?)

   Thanks,
   Marco

   2009/5/13 John Kalucki jkalu...@gmail.com

Chad,

Yes, I think this is called POSTDATA in browsers. I don't recall what
the actual name of this part of the HTTP protocol is, but it's the
body section after the headers.

I corrected the file name error. Thanks.

-John

On May 12, 8:49 pm, Chad Etzel jazzyc...@gmail.com wrote:
 Hi John,

 /follow looks very interesting.  Since you're asking for feedback

 I'm copying the follow parameter example documentation:

 Example: Create a file called 'follow' that contains, exactly and
 excluding the quotation marks: follow=12 13 15 16 20 87. Execute:
 curl -d @followinghttp://stream.twitter.com/follow.json
 -uAnyTwitterUser:Password.You will receive JSON updates from Jack
  Biz,
 Crystal, Ev, Krissy, but not from Jeremy, as he's a private user.

 I'm assuming that follow is just a POSTDATA variable in the normal
 case (you're just using curl's file posting ability in the example)?

 In the example, should the file be called following instead of
 follow (since you are using -d @following in the curl line)?

 Thanks,
 -Chad

 On Tue, May 12, 2009 at 11:24 PM, John Kalucki jkalu...@gmail.com
wrote:

  Note: The Streaming API is currently under a limited alpha test,

[twitter-dev] Re: New Public Streaming API Resource - Follow

2009-05-14 Thread Marco Kaiser

John,

I have all the patience you need ;-)

2009/5/14 John Kalucki jkalu...@gmail.com


 Marco,

 Once again, I beg patience with my ignorance of Twitter's larger
 authentication plans.

 For the time being, the primary use for Hosebird is delivering streams
 to partners, data analyzers, and other developers looking to
 experiment with statuses in a way that the purpose-built REST API
 might not allow. For this case, basic auth is probably acceptable,
 barely, as it is typically server to server. Desktop clients have much
 greater exposure to man-in-the-middle snooping, so I fully appreciate
 the concern about passwords.


Yes - and I agree with you that all the restricted Hosebird streams are
really targeting the server-side market. I was just following your thought
of making use of the public (lowest-tier) streams, and especially the
follow stream, in a desktop client. That's where my concerns come from.



 It never occurred to me that OAuth might be a thing for the desktop.
 In my experience, clients are mostly using basic auth, but it
 certainly would be nice if that evolved. I think all I can say at this
 point is, if streaming to the desktop becomes a Big Thing, we'll look
 into adding a better authentication mechanism to the Streaming API.


I'd love to share yoour opinion - I don't think OAuth is a model that works
well for any desktop application, and that storing a user's password on his
own computer isn't a big deal (we do this everyday with cached passwords in
browsers, mail clients, IM apps etc). But Twitter is clearly driving the
whole dev community towards OAuth (just look at the deprecation of new
source parameters and your encouragement to use OAuth instead), so I was
wondering how this new API fits into that.

Anyway, thanks for your answers, and I am well aware that this is an alpha
test and subject to change anyway.

Marco


 -John


 On May 14, 2:56 am, Marco Kaiser kaiser.ma...@gmail.com wrote:
  2009/5/13 John Kalucki jkalu...@gmail.com
 
 
 
   I'll attempt to answer these questions, but I can only do so with some
   speculation and humble ignorance.
 
   1) OAuth allows clients to authenticate with the Twitter REST API via
   third-party services. These services should not also need to interact
   with the Streaming API on a per client basis. Instead, the service
   should establish a single query that satisfies all clients' needs.
   This may not be practical in all cases, but I suspect we can
   approximate the desired behavior with the current set of primitives.
 
  John,
 
  in your original mail on this thread you wrote:
 
  For example, a desktop client could simulate a user's /home timeline,
  minus private updates and mentions, via the /follow resource.
  Continuous polling would no longer be necessary or desired.
 
  This doesn't match the scenario from above, where you refer to using the
  streaming endpoints from a single query per service. So still the
 question
  how a desktop client that is trying to do OAuth and not ask users for
 their
  passwords can use the streaming API is open - or are you saying that
 those
  clients just cannot use it? I think this would discourage many desktop
  developers from even looking into integrating OAuth for their clients,
 which
  as I assume can't be in twitter's interest.
 
   2) There are no immediate plans to support HTTPS, mainly because we're
   not really trying to keep the data private. Also, and I am probably
   totally wrong here, I don't think we use HTTPS on the main WWW site or
   on the REST API, so this doesn't make things much worse than they
   already are. A possible workaround would be for sensitive service to
   create an account just for streaming. Should the password be
   compromised, there's only a denial of service risk and no further
   risk.
 
  Again, this doesn't help much in the context of desktop app use, as it
 would
  have to use it's authenticated user's credentials. Clients just shouldn't
  send a cleartext password over an unecrypted connection IMO.
 
  Marco
 
   On May 13, 11:18 am, Marco Kaiser kaiser.ma...@gmail.com wrote:
John,
 
this looks pretty interesting!
 
Two questions:
 
1) you are requiring to send a username and password for Basic Auth -
 how
does that map to apps / services using OAuth, as they won't have
 access
   to a
user's passwords? (and related, how does this fit into your general
   roadmap
to move everything to OAuth?)
 
2) the docs only mention http as a protocol, not https. In
 combination
   with
requiring passwords, only making http available seems quite unsecure.
 Any
plans to also support https soon (or any other mechanism which gives
   better
security?)
 
Thanks,
Marco
 
2009/5/13 John Kalucki jkalu...@gmail.com
 
 Chad,
 
 Yes, I think this is called POSTDATA in browsers. I don't recall
 what
 the actual name of this part of the HTTP protocol is, but it's the
 body section after the

[twitter-dev] statuses/updates : unable to set source parameter

2009-05-14 Thread Nicolas Pene

Hi,
I'm working on a twitter client for Unix/Linux terminals (using Curl.)
I have a problem with it, I can't chang the source parameter when I'm
sending tweets.
Few days ago, I have register my application on the following url :
http://twitter.com/oauth_clients but the problem is the same.
Here is my command :
curl -u $twname:$twpwd -d status=\$mytweet\ \
http://twitter.com/statuses/update.xml?source=twitterfeed
Nb : this command works perfecly when I change the source name
sledgehammer by twitterfeed for example. Something goes wrong on my
registration, but I don't know what.
I realy don't know what to do, could you help me ?
Thanks,
@fenice
-- 
Think outside the box
Nicolas Pène - Don Fenice
http://godfather.fr
http://getbetter.fr

Twitter : fenice

[twitter-dev] Re: statuses/updates : unable to set source parameter

2009-05-14 Thread Chad Etzel


If you register an OAuth app, you must make an OAuth call in order for
the source to show up.  Registering/using new sources for Basic Auth
calls has been depricated, but older sources still work (which is why
twitterfeed works for you).

You'll need to make OAuth calls to see your source parameter.

-Chad

On Thu, May 14, 2009 at 9:25 AM, Nicolas Pene nicolas.p...@gmail.com wrote:
 Hi,
 I'm working on a twitter client for Unix/Linux terminals (using Curl.)
 I have a problem with it, I can't chang the source parameter when I'm
 sending tweets.
 Few days ago, I have register my application on the following url :
 http://twitter.com/oauth_clients but the problem is the same.
 Here is my command :
 curl -u $twname:$twpwd -d status=\$mytweet\
 \http://twitter.com/statuses/update.xml?source=twitterfeed
 Nb : this command works perfecly when I change the source name
 sledgehammer by twitterfeed for example. Something goes wrong on my
 registration, but I don't know what.
 I realy don't know what to do, could you help me ?
 Thanks,
 @fenice
 --
 Think outside the box
 Nicolas Pène - Don Fenice
 http://godfather.fr
 http://getbetter.fr

 Twitter : fenice

[twitter-dev] Data mining feed stuck with old results

2009-05-14 Thread Ianiv Schweber


Our data mining feed is stuck with items from about 20 hours ago:

created_atWed May 13 18:59:26 + 2009/created_at

Search and other timelines seem fine.

Thanks,

Ianiv Schweber
NowPublic.com

[twitter-dev] Re: Data mining feed stuck with old results

We've were notified of this late yesterday (there is a Google Code issue).
I've opened an internal ticket to have this taken care fixed.
In the mean time, you can take a look at the /spritzer Streaming API method
to receive push data :) Search the archives for information if this news.

Thanks,
Doug
--

Doug Williams
Twitter Platform Support
http://twitter.com/dougw


On Thu, May 14, 2009 at 8:41 AM, Ianiv Schweber ian...@gmail.com wrote:


 Our data mining feed is stuck with items from about 20 hours ago:

 created_atWed May 13 18:59:26 + 2009/created_at

 Search and other timelines seem fine.

 Thanks,

 Ianiv Schweber
 NowPublic.com

[twitter-dev] Re: Data mining feed stuck with old results

s/to have this taken care fixed/to have this fixed/;
Woops,
Doug
--

Doug Williams
Twitter Platform Support
http://twitter.com/dougw



On Thu, May 14, 2009 at 9:11 AM, Doug Williams d...@twitter.com wrote:

 We've were notified of this late yesterday (there is a Google Code issue).
 I've opened an internal ticket to have this taken care fixed.
 In the mean time, you can take a look at the /spritzer Streaming API method
 to receive push data :) Search the archives for information if this news.

 Thanks,
 Doug
 --

 Doug Williams
 Twitter Platform Support
 http://twitter.com/dougw


 On Thu, May 14, 2009 at 8:41 AM, Ianiv Schweber ian...@gmail.com wrote:


 Our data mining feed is stuck with items from about 20 hours ago:

 created_atWed May 13 18:59:26 + 2009/created_at

 Search and other timelines seem fine.

 Thanks,

 Ianiv Schweber
 NowPublic.com

[twitter-dev] Re: API Changes for May 11, 2009

Can you open an issue for this so we can track it? I'll take a look today.
Thanks,
Doug



On Thu, May 14, 2009 at 3:34 AM, rlamfink randylf...@comcast.net wrote:


 Using the blocks/blocking API, the page parameter has no effect. I
 always get the first page, no matter what page number is in the URL
 parameter. Also I don't get just 20 users in the list as the
 documentation says. I get more.

[twitter-dev] Re: Regex for @replies

2009-05-14 Thread Tim Rosenblatt


Hey Craig,

We found an addition to this. Your regex is great, but it doesn't
limit the length of screen names. Twitter doesn't allow signups
greater than 15 chars (but in tweets, it will actually link up to 20
chars).

So, @abcdefghijklmnopqrstuvwxyz will be linked out to
@abcdefghijklmnopqrst

\...@[\w\d_]{1,15}

This also works in Ruby.

-- Tim

On May 12, 2:01 pm, ericdoesdot...@gmail.com
ericdoesdot...@gmail.com wrote:
 Hi Everyone,

 In .NET, I use the regex: \...@[\w\d_]+

 This pattern exhibits the behavior described by Doug -- it finds the
 mentions @bob, @BOB, @bob and -...@bob, but not _...@bob and h...@bob.

 I sent the following tweet:

 `...@a ~...@a !...@a @@a #...@a $...@a %...@a ^...@a @a *...@a (@a )@a 
 _...@a +...@a -...@a =...@a [...@a
 {...@a ]...@a }...@a \...@a |@a ;@a :@a '@a @a ,@a @a @a @a /@a ?...@a 
 a...@a 1...@a

 Twitter and my pattern both did not match _...@a and a...@a and 1...@a.

 On May 12, 8:13 am, CaMason stasisme...@googlemail.com wrote:

  It looks like they're simply applying this regex as a test:

  (?![\w])@username(?![\w])

  Thus, if a character on either side is not (a-z, A-Z, 0-9, _) then it
  is a mention. any 'word' character (a-z, A-Z, 0-9, _) on either side
  of '@screenname' causes the mention to fail.

  (I hope I got the regex explanation correct!).

  -Craig

  On May 12, 12:33 pm, hjb ha...@heatonmoor.com wrote:

   @Doug,

   Is this behavour likely to remain? ( I noticed that @replies and -
   @replies are successful )

   That is to say, I'm sure @replies will work at some point via sms, but
   can we rely on the fact that _...@replies do not? Is this related to
   there being any chance of it being an email address?

   Thanks,

   Harry

   On May 11, 6:26 pm, Doug Williams d...@twitter.com wrote:

In my test posts @dougw and @DOUGW worked as mentions. t...@dougw and
_...@dougw were not included  as mentions.

Thanks,
Doug
--

Doug Williams
Twitter Platform Supporthttp://twitter.com/dougw

On Mon, May 11, 2009 at 10:16 AM, CaMason 
stasisme...@googlemail.comwrote:

 Thanks Doug, that's a great help.

 How about preceding?

 i.e. should t...@dougw, _...@dougw or @dougw create mentions? 
 The
 main concern here obviously is email addresses.

 And finally, are screen names case sensitive? :)

 Cheers

 On May 11, 6:07 pm, Doug Williams d...@twitter.com wrote:
  The classic definition of an @reply is any tweet that starts with 
  @user.
 If
  you perfrom a to:user (e.g. to:dougw) query at search.twitter.com 
  you
 will
  only get @replies. @replies were converted to mentions after we 
  realized
  people didn't just @reply. Mentions are any tweet that contain @user
 within
  the text of the tweet.

  So @replies are a subset of mentions.

  Any non-alphanumeric (where alphanumeric is a-z, 0-9, or _) can 
  terminate
  the username. For instance: hi @dougw, you look dapper today is a
 mention.

  Thanks,
  Doug
  --

  Doug Williams
  Twitter Platform Supporthttp://twitter.com/dougw

  On Mon, May 11, 2009 at 2:36 AM, stasisme...@googlemail.com 

  stasisme...@googlemail.com wrote:

   Hi guys,

   For an application I'm working on, we have a single table for 
   'tweets'
   and another for DMs. We're linking TwitterUsers to Tweets with a
   many:many, and a simple flag to specify if the tweet is a reply/
   mention.

   We first pull in messages from the user_timeline feed, then the
   mentions feed. As such, we'd like to check if any of the messages 
   in
   user_timeline feed is actually a reply.

   Could anybody clarify the exact rules that are used to determine
   whether a string is a reply/mention?

   i.e.
   preceded by start-of-string or non-word character...
   followed by space, comma, period or end of message...
   case insensitive...
   [not even sure if these are correct! :) ]

   Currently I'm using:

   /(?![^\W_])@%s(?![^\W_])/i

   with %s replaced by the user's screen name. Perhaps one of the 
   devs
   could share the exact rules (or even the regex), or propose a 
   nicer
   mechanism for detecting replies.

   (I did propose checking for replies before tweets, but these 
   update
   threads are run asynchronously).

   Cheers- Hide quoted text -

  - Show quoted text -

[twitter-dev] Re: twitter digest not available


That's awesome, AJ.

Though it hurts me in the opinion-of-humanity part of my brain to learn how
heavily represented American Idol is on that list.


--
Patrick Burrows
http://Categorical.ly (the Best Twitter Client Possible)
@Categorically

-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of AJ
Sent: Wednesday, May 13, 2009 6:36 PM
To: Twitter Development Talk
Subject: [twitter-dev] twitter digest not available


Hi, thanks to twitter's api and the api team, the data feed for data
mining is just wonderful. I have put together a real time system that
takes in the feed and does some NLP analysis on tweets using open
tools like Open Calais and openNLP.  The results are freely available
on http://web2express.org/.  Using this twiiter web app, you can
spot   daily hot topics and for each hot topic, quickly find the top
contributing twitter users. I hope this real time information will
help users to understand the popular topics at any given moment and
easily identify who to follow.

Please let me know if you have any comment.

-aj
AJ Chen, PhD
Co-Chair, Semantic Web SIG, sdforum.org
http://web2express.org
Palo Alto, CA

[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?

2009-05-14 Thread David Troyer

I would just like to put in my two cents that I think this has to be
addressed before basic auth is taken away. I am currently developing
a mobile app that would not be possible with oauth.

David Troyer

On Apr 20, 1:29 am, Doug Williams d...@twitter.com wrote:
Jeff,
We are still thinking internally about how we want to get around the browser
for OAuth token requests. Although, at this time we don't have a particular
implementation to share.

Doug Williams
Twitter API Supporthttp://twitter.com/dougw

On Sun, Apr 19, 2009 at 9:41 PM, Jeff Bishop jeff.bis...@gmail.com wrote:
Doug,

I think if the user could log in to Twitter from a link and then be
redirected to a place where the code could be shown to paste into the
desktop application then that would work fine. Heck, you could even put a
copy to clipboard button on that page so that the user could paste it in.
Is this something planned or does it already exist?

Jeff

- Original Message -
*From:* Doug Williams d...@twitter.com
*To:* twitter-development-talk@googlegroups.com
*Sent:* Sunday, April 19, 2009 9:22 PM
*Subject:* [twitter-dev] Re: oAUTH - can it be done without interaction
with a core browser?

The call tohttp://twitter.com/oauth/authorize(or the Sign in with
Twitter equivalenthttp://twitter.com/oauth/authenticate) requires a
browser to render the HTML necessary for the user prompt. This is a
limitation we recognize with the current beta release of the OAuth
implementation.

Doug Williams
Twitter API Support
http://twitter.com/dougw

On Sun, Apr 19, 2009 at 1:37 PM, Guan Yang g...@yang.dk wrote:

On Sun, Apr 19, 2009 at 14:37, Jeff Bishop jeff.bis...@gmail.com wrote:
1. Get all of the required items from the user outside of Twitter's
interface?
2. Authenticate (like with basic auth of some type using XML posts)?
3. Be able to post back to get the token information.

I'm not completely sure what you want, but you could do something like
this:

- Obtain a request token and secret.
- Start up a browser and send the user to
http://twitter.com/oauth/authorize
- Display a button that says something like click here when you're done
- When the user clicks that button, assume that you're authorized with
Twitter, and make a request to obtain the access token.
- If that's not the case, repeat the process.

The point is that you don't really need any information back through
the callback other than the fact that the user has completed the
authorization process. But that can be accomplished simply by having
the user click a button.

If you are able to register URI schemes in the operating system that
will launch your app, there is a different way of doing this. Suppose
you've registered mycoolapp:// with the operating system. Then you can
supply an oauth_callback parameter to
http://twitter.com/oauth/authorizethat looks something like this:

mycoolapp://twitter-authorize-complete

After successful authorization, Twitter will then redirect to something
like

mycoolapp://twitter-authorize-complete?oauth_token=xxxscreen_name=guanuser_id=1234other_params=values

That way your app will automatically be launched after authorization
and you can call access_token at that point.

Guan

[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?

David,
That is our intention, as mentioned in past discussion and documented on the
FAQ:

http://apiwiki.twitter.com/FAQ#WhenwillTwittersupportOAuthhttp://apiwiki.twitter.com/FAQ

Thanks,
Doug
--

Doug Williams
Twitter Platform Support
http://twitter.com/dougw

On Thu, May 14, 2009 at 10:21 AM, David Troyer dmtro...@gmail.com wrote:

I would just like to put in my two cents that I think this has to be
addressed before basic auth is taken away. I am currently developing
a mobile app that would not be possible with oauth.

David Troyer

On Apr 20, 1:29 am, Doug Williams d...@twitter.com wrote:
Jeff,
We are still thinking internally about how we want to get around the
browser
for OAuth token requests. Although, at this time we don't have a
particular
implementation to share.

Doug Williams
Twitter API Supporthttp://twitter.com/dougw

On Sun, Apr 19, 2009 at 9:41 PM, Jeff Bishop jeff.bis...@gmail.com
wrote:
Doug,

I think if the user could log in to Twitter from a link and then be
redirected to a place where the code could be shown to paste into the
desktop application then that would work fine. Heck, you could even
put a
copy to clipboard button on that page so that the user could paste it
in.
Is this something planned or does it already exist?

Jeff

The call
tohttp://twitter.com/oauth/authorize(orhttp://twitter.com/oauth/authorize%28orthe
Sign in with
Twitter equivalenthttp://twitter.com/oauth/authenticate) requires a
browser to render the HTML necessary for the user prompt. This is a
limitation we recognize with the current beta release of the OAuth
implementation.

Doug Williams
Twitter API Support
http://twitter.com/dougw

On Sun, Apr 19, 2009 at 1:37 PM, Guan Yang g...@yang.dk wrote:

On Sun, Apr 19, 2009 at 14:37, Jeff Bishop jeff.bis...@gmail.com
wrote:
1. Get all of the required items from the user outside of Twitter's
interface?
2. Authenticate (like with basic auth of some type using XML
posts)?
3. Be able to post back to get the token information.

I'm not completely sure what you want, but you could do something like
this:

- Obtain a request token and secret.
- Start up a browser and send the user to
http://twitter.com/oauth/authorize
- Display a button that says something like click here when you're
done
- When the user clicks that button, assume that you're authorized with
Twitter, and make a request to obtain the access token.
- If that's not the case, repeat the process.

mycoolapp://twitter-authorize-complete

After successful authorization, Twitter will then redirect to
something
like

mycoolapp://twitter-authorize-complete?oauth_token=xxxscreen_name=guanuser_id=1234other_params=values

That way your app will automatically be launched after authorization
and you can call access_token at that point.

Guan

[twitter-dev] Re: twitter digest not available

2009-05-14 Thread AJ Chen

Yes, the daily hot topics may surprise many people. I could not believe what
I saw when the system went online for the first time a few months ago. If
you are used to reading tech news or WSJ, you may get a shock. The daily
conversations on twitter, and probably other social networking sites, are
mostly about TV shows, movies, games, and other entertainment stuff. But, on
the other hand, this also makes sense. People are talking about their lives
on social networking sites, and life is not all about technology and stock
market, at least for most ordinary people.

Web2express Digest does not cut or selection of topics. It just shows
whatever comes out of the ongoing conversations from millions of people. I
think we can learn a lot from this information in addition to becoming more
effective in navigating through the twitter sphere.

-aj
-- 
AJ Chen, PhD
Co-Chair, Semantic Web SIG, sdforum.org
http://web2express.org
Palo Alto, CA

On Thu, May 14, 2009 at 10:03 AM, Patrick Burrows
pburr...@categorical.lywrote:


 That's awesome, AJ.

 Though it hurts me in the opinion-of-humanity part of my brain to learn how
 heavily represented American Idol is on that list.


 --
 Patrick Burrows
 http://Categorical.ly (the Best Twitter Client Possible)
 @Categorically

 -Original Message-
 From: twitter-development-talk@googlegroups.com
 [mailto:twitter-development-t...@googlegroups.com] On Behalf Of AJ
 Sent: Wednesday, May 13, 2009 6:36 PM
 To: Twitter Development Talk
 Subject: [twitter-dev] twitter digest not available


 Hi, thanks to twitter's api and the api team, the data feed for data
 mining is just wonderful. I have put together a real time system that
 takes in the feed and does some NLP analysis on tweets using open
 tools like Open Calais and openNLP.  The results are freely available
 on http://web2express.org/.  Using this twiiter web app, you can
 spot   daily hot topics and for each hot topic, quickly find the top
 contributing twitter users. I hope this real time information will
 help users to understand the popular topics at any given moment and
 easily identify who to follow.

 Please let me know if you have any comment.

 -aj
 AJ Chen, PhD
 Co-Chair, Semantic Web SIG, sdforum.org
 http://web2express.org
 Palo Alto, CA

[twitter-dev] Re: Can Somebody Help Me Setup My Twitter API?

2009-05-14 Thread Nick Arnett

On Thu, May 14, 2009 at 10:53 AM, J... celebur...@gmail.com wrote:


 Hello Twitter API Group,

 I am a novice programmer who would like to experiment with the Twitter
 API, however I have spent the last week attempting to setup the API


What language are you using?

Nick

[twitter-dev] Re: statuses/updates : unable to set source parameter

2009-05-14 Thread Don Fenice


thank you for the answer.
I tried to use OAuth, but I haven't found any application or example
for curl (the command line version of curl)

On 14 mai, 17:15, Chad Etzel jazzyc...@gmail.com wrote:
 If you register an OAuth app, you must make an OAuth call in order for
 the source to show up.  Registering/using new sources for Basic Auth
 calls has been depricated, but older sources still work (which is why
 twitterfeed works for you).

 You'll need to make OAuth calls to see your source parameter.

 -Chad



 On Thu, May 14, 2009 at 9:25 AM, Nicolas Pene nicolas.p...@gmail.com wrote:
  Hi,
  I'm working on a twitter client for Unix/Linux terminals (using Curl.)
  I have a problem with it, I can't chang the source parameter when I'm
  sending tweets.
  Few days ago, I have register my application on the following url :
 http://twitter.com/oauth_clientsbut the problem is the same.
  Here is my command :
  curl -u $twname:$twpwd -d status=\$mytweet\
  \http://twitter.com/statuses/update.xml?source=twitterfeed
  Nb : this command works perfecly when I change the source name
  sledgehammer by twitterfeed for example. Something goes wrong on my
  registration, but I don't know what.
  I realy don't know what to do, could you help me ?
  Thanks,
  @fenice
  --
  Think outside the box
  Nicolas Pène - DonFenice
 http://godfather.fr
 http://getbetter.fr

  Twitter :fenice

[twitter-dev] Re: Can Somebody Help Me Setup My Twitter API?


If you just have general questions, I'm sure you could simply ask this list
for free. 

For instance: as long as you have a twitter account, there is nothing else
you need to access the API.

Have you tried using some of the curl command line statements that are on
documented on most (all?) Twitter API call wiki pages? Curl is a command
line utility. If you are using Windows you will have to download a copy of
it (it is free).


--
Patrick Burrows
http://Categorical.ly (the Best Twitter Client Possible)
@Categorically


-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of J...
Sent: Thursday, May 14, 2009 1:53 PM
To: Twitter Development Talk
Subject: [twitter-dev] Can Somebody Help Me Setup My Twitter API?


Hello Twitter API Group,

I am a novice programmer who would like to experiment with the Twitter
API, however I have spent the last week attempting to setup the API
correctly on my own account and seem to be getting confused or having
questions.  If there is a freelancer or somebody who has experience in
setting up I would like to hire them to help me out.  I have the book
Twitter API: Up and Running but seem to be having trouble with some
of the info in the book as well.  Please contact me ASAP and we can
talk further.  I would be excited to get going on this as soon as
possible but am also eager to learn about the API as well.

[twitter-dev] Re: twitter digest not available

It would be interesting to try and automatically categorize the information
as well. I had intended to add Bayesian categorization functionality to
Categorical.ly, eventually. But that would be more categorization of an
individual user's tweets based on categories they set up. 

 

It would be interesting to do something similar for the digest you've
created. I'm not sure how you would train it, initially. 

 

--

Patrick Burrows

http://Categorical.ly (the Best Twitter Client Possible)

@Categorically

 

From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of AJ Chen
Sent: Thursday, May 14, 2009 1:49 PM
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: twitter digest not available

 

Yes, the daily hot topics may surprise many people. I could not believe what
I saw when the system went online for the first time a few months ago. If
you are used to reading tech news or WSJ, you may get a shock. The daily
conversations on twitter, and probably other social networking sites, are
mostly about TV shows, movies, games, and other entertainment stuff. But, on
the other hand, this also makes sense. People are talking about their lives
on social networking sites, and life is not all about technology and stock
market, at least for most ordinary people. 

Web2express Digest does not cut or selection of topics. It just shows
whatever comes out of the ongoing conversations from millions of people. I
think we can learn a lot from this information in addition to becoming more
effective in navigating through the twitter sphere.

-aj 
-- 
AJ Chen, PhD
Co-Chair, Semantic Web SIG, sdforum.org
http://web2express.org
Palo Alto, CA

On Thu, May 14, 2009 at 10:03 AM, Patrick Burrows pburr...@categorical.ly
wrote:


That's awesome, AJ.

Though it hurts me in the opinion-of-humanity part of my brain to learn how
heavily represented American Idol is on that list.


--
Patrick Burrows
http://Categorical.ly (the Best Twitter Client Possible)
@Categorically


-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of AJ
Sent: Wednesday, May 13, 2009 6:36 PM
To: Twitter Development Talk
Subject: [twitter-dev] twitter digest not available


Hi, thanks to twitter's api and the api team, the data feed for data
mining is just wonderful. I have put together a real time system that
takes in the feed and does some NLP analysis on tweets using open
tools like Open Calais and openNLP.  The results are freely available
on http://web2express.org/.  Using this twiiter web app, you can
spot   daily hot topics and for each hot topic, quickly find the top
contributing twitter users. I hope this real time information will
help users to understand the popular topics at any given moment and
easily identify who to follow.

Please let me know if you have any comment.

-aj
AJ Chen, PhD
Co-Chair, Semantic Web SIG, sdforum.org
http://web2express.org
Palo Alto, CA

[twitter-dev] How do you store Twitter profiles in your database?

2009-05-14 Thread Arik Fraimovich


I came to the point in my application development, that I need to
start caching profiles. I guess that many of you already doing such
caching and can share some tips from your experience.

Basically what I thought about is to store the cached profiles in a DB
table. What I wasn't sure about is the schema of the table. Thought of
two options:
1. store the user_id, screenname and created_at/updated_at fields (to
know where to get newer copy) and to store the rest of the fields as
JSON in a blob/text field.
Pros: no need to update structure whenever the API updates.
Cons: can't do interesting aggregations on the profiles.
2. create the table schema to be same as the fields the Twitter API
returns (+ created_at/updated_at).
Pros: can do interesting aggregations, can set indexes on key fields
(although I will usually retrieve by user_id/screename)
Cons: will have to update the schema each time the API updates, need
to create a lot of fields in the DB :)

Any other cons/pros I need to consider? Any other suggestions?

Thanks !
Arik (@arikfr)

[twitter-dev] Unscheduled downtime

Please see the status blog:
http://status.twitter.com/post/107824532/unplanned-downtime
Thanks,
Doug
--

Doug Williams
Twitter Platform Support
http://twitter.com/dougw

[twitter-dev] Re: How do you store Twitter profiles in your database?


I think number 2 is the only good option here (and it is what I do.)

The problem with storing serialized data (such as JSON) in a database is
that if the schema changes, now you need to know what the original schema
version was of the data in the database in order to deserialize it. The
schema could change without you knowing and break things in a way that is
undetectable for weeks or months. 

With a defined schema, you get an error immediately and can fix it
immediately. 


--
Patrick Burrows
http://Categorical.ly (the Best Twitter Client Possible)
@Categorically


-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Arik
Fraimovich
Sent: Thursday, May 14, 2009 3:36 PM
To: Twitter Development Talk
Subject: [twitter-dev] How do you store Twitter profiles in your database?


I came to the point in my application development, that I need to
start caching profiles. I guess that many of you already doing such
caching and can share some tips from your experience.

Basically what I thought about is to store the cached profiles in a DB
table. What I wasn't sure about is the schema of the table. Thought of
two options:
1. store the user_id, screenname and created_at/updated_at fields (to
know where to get newer copy) and to store the rest of the fields as
JSON in a blob/text field.
Pros: no need to update structure whenever the API updates.
Cons: can't do interesting aggregations on the profiles.
2. create the table schema to be same as the fields the Twitter API
returns (+ created_at/updated_at).
Pros: can do interesting aggregations, can set indexes on key fields
(although I will usually retrieve by user_id/screename)
Cons: will have to update the schema each time the API updates, need
to create a lot of fields in the DB :)

Any other cons/pros I need to consider? Any other suggestions?

Thanks !
Arik (@arikfr)

[twitter-dev] verify_credentials how do i extract values from array in php?

2009-05-14 Thread TonyHawley


Hi, i want to be able to print specific values from the
verify_credentials.xml after a user has successful login.

The problem im having i haven't a clue how to print individual values
from the returned user array.

Im using this code to get user info, but i cant echo single parts of
the array

$user_info = $to-OAuthRequest('https://twitter.com/account/
verify_credentials.xml', array(), 'GET');

I want to extract the username and display picture i tried things like

echo $user_info[name]
echo $user_info[1]

But no joy, can anyone point me in the right direction?

Thanks in advance for any help.

[twitter-dev] Re: Bad Celebrity Search Results

2009-05-14 Thread rob


I just tried this with the API, and it seems to work for Diddy:

feed://twitter.com/statuses/user_timeline.atom?screen_name=iamdiddy

And Shaq:

feed://twitter.com/statuses/user_timeline.atom?screen_name=THE_REAL_SHAQ




On May 13, 10:18 pm, Brendan O'Connor breno...@gmail.com wrote:
 i wanted to get all of shaq's tweets with the search api and i couldn't :)

 going through random ones on twitterholic ..
 from:aplusk barely works
 from:scobleizer works
 from:adventuregirl works
 from:timoreilly works

 haven't tried the standard API for these.

 bleah
 Brendan



 On Wed, May 13, 2009 at 6:57 PM, explicious avail4...@gmail.com wrote:

  Hi Brendan,

  found out how? references? or merely observed per the link? It's
  curious because it might be throwing off my calculated 'coolness
  vector' - I noticed the coolness vector of a tweet containing a celebs
  name seemed lower than anticipiated - however it wasn't the point of
  the experiment, mind you - I just found the downplay sorta odd and mad-
  ening. :-)

  Thanks
  Waitman

  On May 13, 6:44 pm, Brendan O'Connor breno...@gmail.com wrote:
   i just found out some high-volume users aren't indexed at all.  for
  example:

[twitter-dev] Re: verify_credentials how do i extract values from array in php?

 echo $user_info['name']

On Thu, May 14, 2009 at 16:03, TonyHawley parabe...@gmail.com wrote:


 Hi, i want to be able to print specific values from the
 verify_credentials.xml after a user has successful login.

 The problem im having i haven't a clue how to print individual values
 from the returned user array.

 Im using this code to get user info, but i cant echo single parts of
 the array

 $user_info = $to-OAuthRequest('https://twitter.com/account/
 verify_credentials.xmlhttps://twitter.com/account/%0Averify_credentials.xml',
 array(), 'GET');

 I want to extract the username and display picture i tried things like

 echo $user_info[name]
 echo $user_info[1]

 But no joy, can anyone point me in the right direction?

 Thanks in advance for any help.






-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: statuses/updates : unable to set source parameter

Twitter may approve a source parameter for a command line application. Email
a...@twitter.com and explain why OAuth won't work for you.

On Thu, May 14, 2009 at 13:28, Don Fenice nicolas.p...@gmail.com wrote:


 thank you for the answer.
 I tried to use OAuth, but I haven't found any application or example
 for curl (the command line version of curl)

 On 14 mai, 17:15, Chad Etzel jazzyc...@gmail.com wrote:
  If you register an OAuth app, you must make an OAuth call in order for
  the source to show up.  Registering/using new sources for Basic Auth
  calls has been depricated, but older sources still work (which is why
  twitterfeed works for you).
 
  You'll need to make OAuth calls to see your source parameter.
 
  -Chad
 
 
 
  On Thu, May 14, 2009 at 9:25 AM, Nicolas Pene nicolas.p...@gmail.com
 wrote:
   Hi,
   I'm working on a twitter client for Unix/Linux terminals (using Curl.)
   I have a problem with it, I can't chang the source parameter when I'm
   sending tweets.
   Few days ago, I have register my application on the following url :
  http://twitter.com/oauth_clientsbut the problem is the same.
   Here is my command :
   curl -u $twname:$twpwd -d status=\$mytweet\
   \http://twitter.com/statuses/update.xml?source=twitterfeed
   Nb : this command works perfecly when I change the source name
   sledgehammer by twitterfeed for example. Something goes wrong on my
   registration, but I don't know what.
   I realy don't know what to do, could you help me ?
   Thanks,
   @fenice
   --
   Think outside the box
   Nicolas Pène - DonFenice
  http://godfather.fr
  http://getbetter.fr
 
   Twitter :fenice




-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from San Francisco, CA, United States

[twitter-dev] Re: verify_credentials how do i extract values from array in php?

2009-05-14 Thread TonyHawley


Thanks for your reply, i tried that and its returns a left arrow 
no username? i tried with other parameters aswell location,
screen_name etc, still no joy?

I am actaully using your library Abraham, but totally baffled, ive
been on this for almost 2 days now, what do you think im doing wrong?

Thanks again for your time

On 14 May, 23:21, Abraham Williams 4bra...@gmail.com wrote:
  echo $user_info['name']



 On Thu, May 14, 2009 at 16:03, TonyHawley parabe...@gmail.com wrote:

  Hi, i want to be able to print specific values from the
  verify_credentials.xml after a user has successful login.

  The problem im having i haven't a clue how to print individual values
  from the returned user array.

  Im using this code to get user info, but i cant echo single parts of
  the array

  $user_info = $to-OAuthRequest('https://twitter.com/account/
  verify_credentials.xmlhttps://twitter.com/account/%0Averify_credentials.xml',
  array(), 'GET');

  I want to extract the username and display picture i tried things like

  echo $user_info[name]
  echo $user_info[1]

  But no joy, can anyone point me in the right direction?

  Thanks in advance for any help.

 --
 Abraham Williams |http://the.hackerconundrum.com
 Hacker |http://abrah.am|http://twitter.com/abraham
 Web608 | Community Evangelist |http://web608.org
 This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: verify_credentials how do i extract values from array in php?