date:20100830

Hi Omri,

Twitter does not have a tweet count API at this time. The best way to
count tweets is by consuming the streaming API and tracking what's
interesting to you. It won't give you any historical perspective prior to
from your beginning point.

http://dev.twitter.com/pages/streaming_api

Topsy also provides an API: http://labs.topsy.com/widgets/otter-api/

Taylor

On Mon, Aug 30, 2010 at 12:58 AM, omri omridek...@gmail.com wrote:

 hi, my name is omri, and I saw the sites :
 rowfeeder, booshaka and viralheat.
 this sites extract the data from twitter (and facebook) and offer it
 to users, i wanted to know is there a way in your API to extract this
 data? how do this sites reach this data?
 to be more concrete, is there a solution in your api to realize how
 many posts there are that include the search word X?

 thanks.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] can email be accepted when using OAuth?

Hi Joe,

Email can be accepted, as long as it is properly encoded. A URL encoded POST
body by definition means that you'll already have to escape characters like
the @ symbol for your POST body -- then for your signature base string,
it'll have to be encoded again.

Most Twitter users sign in with their screen name and password. Do you have
a use case where users are predominantly using their email address?

Taylor

On Mon, Aug 30, 2010 at 1:10 AM, joe joe.chan...@gmail.com wrote:

 Hi guys,

 I have a question about getting access token.
 Can I use email address as the username? When x_auth_username =
 x...@xxx.com, always a error msg returned: Failed to validate oauth
 signature and token. But if user input username, there is no problem
 at all.
 So can anybody tell whether email address is accepted? Thanks a lot.

 Joe

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Need help getting previously registered application set up for OAuth at dev.twitter.com

Hi Jon,

Please send an email to our API support team at a...@twitter.com with as much
information as possible, from the email address associated with the Twitter
account you ultimately want to own the application (probably best to have
the account belong to the business rather than an employee). You may want to
setup an OAuth application with a different name so that you can get started
on implementation while you wait for the naming rights to be figured out.

Taylor

On Sun, Aug 29, 2010 at 11:53 AM, Jon Galloway jongallo...@gmail.comwrote:

 Alex set Witty up as an application for us a long time ago, but it's
 not associated with our Twitter accounts so we can't set up OAuth.
 Alan Le (@a7an) originally worked with Alex on this. I've taken over
 development (@jongalloway).

 We're obviously in a rush to get OAuth set up before basic auth is
 shut off. How can we get help with this?

 - Jon

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Twitter api request for a user's timeline w/ count=40 is returning ~20 records, why?

With the timeline methods, the count you provide is optimistic in that
you'll get up to those number of results if they are available.

In most cases, the results you aren't seeing would be retweets, which aren't
returned in user_timeline without an include_rts=true parameter.

Taylor

On Sat, Aug 28, 2010 at 6:09 PM, Erik Vold erikvv...@gmail.com wrote:

 why does
 http://twitter.com/statuses/user_timeline.xml?screen_name=erikvoldpage=0count=40
 return ~15 results? should it not return 40 results?

 http://dev.twitter.com/doc/get/statuses/user_timeline

 Erik

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Help with Oauth update status

There is no secure method to accomplish this purely in Javascript, as you
would have to hard code your consumer key  consumer secret as well as an
oauth_token and oauth_token_secret for the Twitter account you want to use
for all operations. With these pieces of information, anyone would be able
to tweet on behalf of your application and account.

In a case like this, you'd want to implement most of this logic server-side,
where you can keep the hard-coded credentials securely. You could
potentially use Javascript to speak to your own servers to hustle the
process along.

We offer a feature on dev.twitter.com that allows you to easily obtain an
access token for the user who owns the application, which would at least
help you in that you'd not have to implement the negotiation steps of OAuth.

Taylor

On Sun, Aug 29, 2010 at 11:13 AM, Matthew Cornell
matthewcorn...@gmail.comwrote:

 I'd like to see this too.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Change in error response objects

2010-08-30 Thread Mike Francisco



Raffi Krikorian wrote:
 it is designed so that we can send multiple error codes back, but in
 practice, right now, we only send one.

 On Sun, Aug 29, 2010 at 4:25 PM, Dewald Pretorius dpr...@gmail.com wrote:

  Raffi,
 
  Will the new error construct always be:
 
  [errors][code]
  [errors][message]
 
  Or can it be sometimes:
 
  [errors][0][code]
  [errors][0][message]
  [errors][1][code]
  [errors][1][message]
 
  --
  Twitter developer documentation and resources: http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk?hl=en
 



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

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Change in error response objects

2010-08-30 Thread Marc Mims

* Raffi Krikorian ra...@twitter.com [100830 05:48]:
 what endpoints are you still seeing this error format under?  the change
 should have been reverted in the case that you were mentioning.

Like Cameron, I'm seeing it on users/show.  Here's an example:
GET http://api.twitter.com/1/users/show/178618878.json

{errors:[{code:63,message:User has been suspended}]}

-Marc

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: HTML errors on /signup, /account/new, /account/create

2010-08-30 Thread RF

Thanks Matt.  Here's a related observation.  If the wrong code is
entered for the Captcha, the email field is reliably emptied out.
Then when the correct Captcha code is entered, the field remains blank
and requires re-entry of the email address. This is a very repeatable
way to reproduce the issue.

On Aug 25, 4:37 pm, Matt Harris thematthar...@twitter.com wrote:
 Hey,

 Thanks for highlighting this to us. I've let the web team know about
 so they can address it.
 Best,
 Matt





 On Wed, Aug 25, 2010 at 12:27 PM, RF rfrank...@airportview.net wrote:
  The account setup pages have several HTML errors exposed by the W3C
  Markup Validation Service. The worst is on line 169.  A reference to
  the non-existent ID user_password causes the next field, email, to
  forget the email address submitted. This error bumps the attempt
  counter, thus giving the user only 3 actual attempts to setup an
  account.

  The following link invokes the validator and lists the errors for /
  account/new:

 http://validator.w3.org/check?uri=https%3A%2F%2Ftwitter.com%2Faccount...

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list
  Change your membership to this 
  group:http://groups.google.com/group/twitter-development-talk?hl=en

 --

 Matt Harris
 Developer Advocate, Twitterhttp://twitter.com/themattharris- Hide quoted text 
 -

 - Show quoted text -

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] PHP Search Example

2010-08-30 Thread lu5ceh

I using

$SearchHashTag = $connection-get(search, array('q' = '#linux'));

To search tweets and returns:

stdClass Object ( [statuses] = Array ( [0] = 45070895939 [1] =
45070904709 [2] = 45070915901 [3] = 45070939637 [4] = 45070939741
[5] = 45071173851 [6] = 45071383871 [7] = 45071675705 [8] =
45071733003 [9] = 45071893347 [10] = 45071895895 [11] = 45071907613
[12] = 45071909151 [13] = 45072271867 [14] = 45072442737 [15] =
45072456829 ) [created_in] = 0.010282 )

how to return Tweets with #linux hashtag?!

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Open Source CMS Module and Consumer Secret

2010-08-30 Thread Michael Babcock

I think the issue is really that it is not a very elegant solution and
is outside the realm of a standard non-technical persons experience.
The whole idea of having the end-user register a pre-built app as
their own is cumbersome. That said it is the only real solution to the
dilemma. It is the solution that I have chosen for my own apps.


On Aug 18, 4:22 am, Ken k...@cimas.ch wrote:
 I am new to this thread having seen it over the past few weeks and
 wondered what all the fuss was about.

 The solution by MindcrimeNL above seems optimal, why is it a
 workaround?

 Do developers not really want their users to register their own
 Twitter app? It's not exactly hard to do. You just need to tell them
 what to put for the callback URL...

 For opensource systems targeted at non-technical users, don't you
 provide a 'control panel' where the admin user can edit their
 preferences such as webmaster's email etc?  Just like inserting your
 Google maps API key, Adsense id, Amazon associates id, etc.

 For applications with a more technical installation, you'd just have
 them edit a config file.

 On Aug 18, 11:34 am, MindcrimeNL hostmas...@gab-ev.de wrote:



  Still no 
  solution:http://groups.google.com/group/twitter-development-talk/msg/58b4b54d4...
  After that initial message, it is apparently still not available...

  I've released my module by explaining in the readme how webmasters can
  add their own application and obtain the consumer public and secret
  key for their application and giving them an option to enter them in
  the module.
  I'm not really happy about this workaround... It just sucks...

  On Aug 1, 2:19 am, Michael Babcock mjet...@gmail.com wrote:

   Sorry for the confusion. I mean web application developers. There are
   quit a number ofopen-sourceweb apps for twitter. Besides standalone
   apps, there are also, add-ons for all the various CMS solutions out
   there, written in PHP, Perl, etc.

   On Jul 27, 2:02 pm, M. Edward (Ed) Borasky zn...@borasky-

   research.net wrote:
There are plenty ofopensource*library* developers, and plenty of  
applications that useopensourcelibraries, but not all that many  
   opensourcefull applications. The only ones I can think of at the  
moment are Gwibber (Gnome), Choqok (KDE), mine (Social Media Analytics  
Research Toolkit), Spaz, get2gnow, and ttytter. IMHO Choqok and  
Gwibber are lame - I use CoTweet or Twitter.com on my desktop and  
mobile.twitter.com, Twitter, Twidroid, Seesmic, Touiteur and Peep on  
my HTC Verizon Droid Incredible.

The Twitter piece of Social Media Analytics Research Toolkit is at the  
moment read only, and as I noted earlier the main reason I even looked  
at oAuth was to get the 1500 (read) API calls per hour. Given the  
small number of users I have at the moment, it wouldn't be all that  
difficult to upgrade them to oAuth and 350 calls per hour one at a  
time by hand - all that would be required is to license that piece of  
code separately. ;-)
--
M. Edward (Ed) 
Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul 
Erdos

Quoting Michael Babcock mjet...@gmail.com:

 Correct me if I am wrong, but doesn't Twitter risk loosing a large
 percentage of their third partyopen-sourcedevelopers, by not having
 a solid solution for the required OAuth security changes in time for
 the deadline?

 I can only guess, but, I would think that theopen-sourcesegment
 would count for quite a large number of independent developers, all
 eager to build for and promote the Twitter vision.

 Michael

 On Jul 27, 8:59 am, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
 Hi Folks,

 There are a few hold ups to rolling this out more widely, the most 
 pressing
 being that we are currently unable to serve SSL content on
 dev.twitter.com-- there are also better solutions than this
 rudimentary one that we simply
 can't implement yet. We're also concerned with releasing (and 
 supporting) a
 solution widely that we'll soon want to deprecate.

 Taylor

 On Tue, Jul 27, 2010 at 8:53 AM, Cameron Kaiser 
 spec...@floodgap.comwrote:

   I have the same question. I need to add Twitter OAuth to my 
   widely
   distributed PHP basedopen-sourceCMS add-on. All the documentation
   says never ever distribute your consumer secret, which I 
   understand
   why this would be a bad idea. Yet all of the 
   documentation/examples I
   have found require that the consumer secret be hard-coded into 
   the
  source.

   The closes thing I have found, that doesn't require the consumer
   secret embedded in thesource, is a description of how it might 
   work,

 http://groups.google.com/group/twitter-development-talk/browse_thread...
   But, I cannot

Re: [twitter-dev] number of search results


Viralheat also has an API.

--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos


Quoting Taylor Singletary taylorsinglet...@twitter.com:


Hi Omri,

Twitter does not have a tweet count API at this time. The best way to
count tweets is by consuming the streaming API and tracking what's
interesting to you. It won't give you any historical perspective prior to
from your beginning point.

http://dev.twitter.com/pages/streaming_api

Topsy also provides an API: http://labs.topsy.com/widgets/otter-api/

Taylor

On Mon, Aug 30, 2010 at 12:58 AM, omri omridek...@gmail.com wrote:


hi, my name is omri, and I saw the sites :
rowfeeder, booshaka and viralheat.
this sites extract the data from twitter (and facebook) and offer it
to users, i wanted to know is there a way in your API to extract this
data? how do this sites reach this data?
to be more concrete, is there a solution in your api to realize how
many posts there are that include the search word X?

thanks.

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en



--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:   
http://groups.google.com/group/twitter-development-talk?hl=en






--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Open Source CMS Module and Consumer Secret


On Aug 18, 4:22 am, Ken k...@cimas.ch wrote:

I am new to this thread having seen it over the past few weeks and
wondered what all the fuss was about.

The solution by MindcrimeNL above seems optimal, why is it a
workaround?

Do developers not really want their users to register their own
Twitter app? It's not exactly hard to do. You just need to tell them
what to put for the callback URL...

For opensource systems targeted at non-technical users, don't you
provide a 'control panel' where the admin user can edit their
preferences such as webmaster's email etc?  Just like inserting your
Google maps API key, Adsense id, Amazon associates id, etc.

For applications with a more technical installation, you'd just have
them edit a config file.



Quoting Michael Babcock mjet...@gmail.com:


I think the issue is really that it is not a very elegant solution and
is outside the realm of a standard non-technical persons experience.
The whole idea of having the end-user register a pre-built app as
their own is cumbersome. That said it is the only real solution to the
dilemma. It is the solution that I have chosen for my own apps.


It depends on the end user and application. If the application  
provides a compelling solution to a real problem that they have, the  
inconvenience of oAuth registration won't matter. If it doesn't, the  
*application* won't matter. ;-)


I suspect that Twitter's human infrastructure, if not its technical  
one, would rebel at a mass-market application where each of hundreds  
or thousands of users had his/her own consumer key and secret in  
addition to a Twitter account. I think it's far better  
developer/business practice to design *proprietary* applications that  
are secure and register them with Twitter using xAuth.


--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Inverse oAuthpocalypse??

Now that oAuthpocalypse is approaching a successful finish, what's the  
plan for Inverse oAuthpocalypse? That is, we were promised that the  
API call rate would rise to 1500 GETs per hour on oAuth. It is  
currently at 350, and dropped to 175 at one point during the World Cup  
Loadapalooza. So is there a plan to gradually get up to the 1500, will  
we see a jump to 1500, or are we stuck at 350 for the foreseeable  
future?


As a developer and former capacity planner, my preference would be for  
a very gradual increase - say increases of 50 an hour per week until  
something breaks, then hold there as dictated by infrastructure growth  
priorities.


--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos





--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: User_Timeline - include_rts not working

2010-08-30 Thread timmerk

I'm having the same issue - you can see an example here:

http://twitter.com/statuses/user_timeline.json?screen_name=NuWaveGOVcount=4include_rts=true

As you can see, there are no retweets included in the JSON.

Thanks!

On Aug 25, 2:30 pm, Matt Harris thematthar...@twitter.com wrote:
Hey Hen,

Are you still finding retweets are not showing up for you?

Matt

On Sat, Aug 21, 2010 at 7:19 AM, henasraf doku...@gmail.com wrote:
Matt,
Any user I show in my app would not show retweets, even if they surely
exist. You can see for yourself athttp://wosaic.net/twitguin(still
early stages, don't mind it being a bit lame), see any user such as
myself athttp://wosaic.net/twitguin/user/henasraf; you may go
through pages and see that no retweets ever show; they should be color
coded in orange. You can compare tohttp://twitter.com/henasrafto see
retweets that should show.

Thanks,
Hen

On Aug 19, 11:34 pm, Matt Harris thematthar...@twitter.com wrote:
Hey,

Retweets should be included if they exist in the users timeline when you
request them. For example if you request 20 Tweets of the timeline and one
of those last 20 was a retweet - it will be included. If one of the last 20
Tweets wasn't a retweet it won't be included, even if include_rts is true.

Does this explain what is happening in your app?
If not could you give an example of a username which shows this problem.

Best,
Matt

On Thu, Aug 19, 2010 at 1:24 PM, henasraf doku...@gmail.com wrote:
Hey all, I'm using user_timeline to fetch the timeline of a user in my
app. Problem is, it doesn't include native Retweets, even though I've
set include_rts to true. The docs clearly say it should work, but it
doesn't. What could be the problem? Thanks in advance :)

Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris

Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris- Hide quoted text
-

- Show quoted text -

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: User_Timeline - include_rts not working

Hi Timmerk,

Make sure you're using api.twitter.com as the host for all of your API
requests. The proper API is not at twitter.com -- it's at api.twitter.com.
Include_rts will not work against twitter.com (and one day you'll find all
of your requests rejected.)

Also, please note that proper API routes include a version component. The
call you're making should be:
http://api.twitter.com/1/statuses/user_timeline.json?screen_name=NuWaveGOVcount=4include_rts=true

Taylor

On Mon, Aug 30, 2010 at 10:43 AM, timmerk timm...@gmail.com wrote:

 I'm having the same issue - you can see an example here:


 http://twitter.com/statuses/user_timeline.json?screen_name=NuWaveGOVcount=4include_rts=true

 As you can see, there are no retweets included in the JSON.

 Thanks!

 On Aug 25, 2:30 pm, Matt Harris thematthar...@twitter.com wrote:
  Hey Hen,
 
  Are you still finding retweets are not showing up for you?
 
  Matt
 
 
 
 
 
  On Sat, Aug 21, 2010 at 7:19 AM, henasraf doku...@gmail.com wrote:
   Matt,
   Any user I show in my app would not show retweets, even if they surely
   exist. You can see for yourself athttp://wosaic.net/twitguin(still
   early stages, don't mind it being a bit lame), see any user such as
   myself athttp://wosaic.net/twitguin/user/henasraf; you may go
   through pages and see that no retweets ever show; they should be color
   coded in orange. You can compare tohttp://twitter.com/henasrafto see
   retweets that should show.
 
   Thanks,
   Hen
 
   On Aug 19, 11:34 pm, Matt Harris thematthar...@twitter.com wrote:
   Hey,
 
   Retweets should be included if they exist in the users timeline when
 you
   request them. For example if you request 20 Tweets of the timeline and
 one
   of those last 20 was a retweet - it will be included. If one of the
 last 20
   Tweets wasn't a retweet it won't be included, even if include_rts is
 true.
 
   Does this explain what is happening in your app?
   If not could you give an example of a username which shows this
 problem.
 
   Best,
   Matt
 
   On Thu, Aug 19, 2010 at 1:24 PM, henasraf doku...@gmail.com wrote:
Hey all, I'm using user_timeline to fetch the timeline of a user in
 my
app. Problem is, it doesn't include native Retweets, even though
 I've
set include_rts to true. The docs clearly say it should work, but it
doesn't. What could be the problem? Thanks in advance :)
 
   --
 
   Matt Harris
   Developer Advocate, Twitterhttp://twitter.com/themattharris
 
  --
 
  Matt Harris
  Developer Advocate, Twitterhttp://twitter.com/themattharris- Hide quoted
 text -
 
  - Show quoted text -

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Inverse oAuthpocalypse??

Hey Ed,

We're still aiming for raising OAuth limits but don't have a time table yet.
Given our experiences with rate limits, World Cup, and our desire for system
stability, I can imagine us staggering the roll out similar to your
suggestions. We'll reinvestigate raising limits after the company-wide
efforts to stabilize the platform are realized.

Taylor

On Mon, Aug 30, 2010 at 10:40 AM, M. Edward (Ed) Borasky 
zn...@borasky-research.net wrote:

 Now that oAuthpocalypse is approaching a successful finish, what's the plan
 for Inverse oAuthpocalypse? That is, we were promised that the API call
 rate would rise to 1500 GETs per hour on oAuth. It is currently at 350, and
 dropped to 175 at one point during the World Cup Loadapalooza. So is there a
 plan to gradually get up to the 1500, will we see a jump to 1500, or are we
 stuck at 350 for the foreseeable future?

 As a developer and former capacity planner, my preference would be for a
 very gradual increase - say increases of 50 an hour per week until something
 breaks, then hold there as dictated by infrastructure growth priorities.

 --
 M. Edward (Ed) Borasky
 http://borasky-research.net http://twitter.com/znmeb

 A mathematician is a device for turning coffee into theorems. - Paul
 Erdos





 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: User_Timeline - include_rts not working

2010-08-30 Thread timmerk

Thanks Taylor! That worked.

On Aug 30, 1:50 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 Hi Timmerk,

 Make sure you're using api.twitter.com as the host for all of your API
 requests. The proper API is not at twitter.com -- it's at api.twitter.com.
 Include_rts will not work against twitter.com (and one day you'll find all
 of your requests rejected.)

 Also, please note that proper API routes include a version component. The
 call you're making should 
 be:http://api.twitter.com/1/statuses/user_timeline.json?screen_name=NuWa...

 Taylor



 On Mon, Aug 30, 2010 at 10:43 AM, timmerk timm...@gmail.com wrote:
  I'm having the same issue - you can see an example here:

 http://twitter.com/statuses/user_timeline.json?screen_name=NuWaveGOV;...

  As you can see, there are no retweets included in the JSON.

  Thanks!

  On Aug 25, 2:30 pm, Matt Harris thematthar...@twitter.com wrote:
   Hey Hen,

   Are you still finding retweets are not showing up for you?

   Matt

   On Sat, Aug 21, 2010 at 7:19 AM, henasraf doku...@gmail.com wrote:
Matt,
Any user I show in my app would not show retweets, even if they surely
exist. You can see for yourself athttp://wosaic.net/twitguin(still
early stages, don't mind it being a bit lame), see any user such as
myself athttp://wosaic.net/twitguin/user/henasraf;you may go
through pages and see that no retweets ever show; they should be color
coded in orange. You can compare tohttp://twitter.com/henasraftosee
retweets that should show.

Thanks,
Hen

On Aug 19, 11:34 pm, Matt Harris thematthar...@twitter.com wrote:
Hey,

Retweets should be included if they exist in the users timeline when
  you
request them. For example if you request 20 Tweets of the timeline and
  one
of those last 20 was a retweet - it will be included. If one of the
  last 20
Tweets wasn't a retweet it won't be included, even if include_rts is
  true.

Does this explain what is happening in your app?
If not could you give an example of a username which shows this
  problem.

Best,
Matt

On Thu, Aug 19, 2010 at 1:24 PM, henasraf doku...@gmail.com wrote:
 Hey all, I'm using user_timeline to fetch the timeline of a user in
  my
 app. Problem is, it doesn't include native Retweets, even though
  I've
 set include_rts to true. The docs clearly say it should work, but it
 doesn't. What could be the problem? Thanks in advance :)

--

Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris

   --

   Matt Harris
   Developer Advocate, Twitterhttp://twitter.com/themattharris-Hide quoted
  text -

   - Show quoted text -

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en- Hide quoted 
 text -

 - Show quoted text -

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

2010-08-30 Thread Jesse Stay

Freakin' awesome. Nice job guys!

Jesse

On Mon, Aug 30, 2010 at 12:52 PM, Mark McBride mmcbr...@twitter.com wrote:

 Site Streams, a new feature on the Streaming API, is now available for
 beta testing. Site Streams allows services, such as web sites or
 mobile push services, to receive real-time updates for a large number
 of users without any of the hassles of managing REST API rate limits.
 The initial version delivers events created by, or directed to, users
 that have shared their OAuth token with your application.

 Via Site Streams, the following events are streamed immediately and
 without rate limits: Direct Messages, Mentions, Follows, Favorites,
 Tweets, Retweets, Profile changes, and List changes. A subsequent
 version is planned that will optionally deliver each user's home
 timeline.

 For additional information on Site Streams and details on how to apply
 for access, see the Site Streams Beta documentation at
 http://bit.ly/sitestreams_doc.

---Mark

 http://twitter.com/mccv

 --
 Twitter API documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Change your membership to this group:
 http://groups.google.com/group/twitter-api-announce?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

2010-08-30 Thread Tom van der Woerdt

My initial thought was that this was for applications like TweetDeck
where users have multiple accounts, but the docs say that Desktop
clients should keep using the normal User Streams. Will there be an
update for the User Streams to support having multiple accounts, are the
docs wrong, or do you really want us to open (in some cases) 10 connections?

Tom


On 8/30/10 8:57 PM, Jesse Stay wrote:
 Freakin' awesome. Nice job guys!
 
 Jesse
 
 On Mon, Aug 30, 2010 at 12:52 PM, Mark McBride mmcbr...@twitter.com
 mailto:mmcbr...@twitter.com wrote:
 
 Site Streams, a new feature on the Streaming API, is now available for
 beta testing. Site Streams allows services, such as web sites or
 mobile push services, to receive real-time updates for a large number
 of users without any of the hassles of managing REST API rate limits.
 The initial version delivers events created by, or directed to, users
 that have shared their OAuth token with your application.
 
 Via Site Streams, the following events are streamed immediately and
 without rate limits: Direct Messages, Mentions, Follows, Favorites,
 Tweets, Retweets, Profile changes, and List changes. A subsequent
 version is planned that will optionally deliver each user's home
 timeline.
 
 For additional information on Site Streams and details on how to apply
 for access, see the Site Streams Beta documentation at
 http://bit.ly/sitestreams_doc.
 
---Mark
 
 http://twitter.com/mccv
 
 --
 Twitter API documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Change your membership to this group:
 http://groups.google.com/group/twitter-api-announce?hl=en
 
 
 -- 
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Desktop clients that support multiple accounts should continue to open
multiple connections on User Streams.

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



On Mon, Aug 30, 2010 at 12:00 PM, Tom van der Woerdt i...@tvdw.eu wrote:

 My initial thought was that this was for applications like TweetDeck
 where users have multiple accounts, but the docs say that Desktop
 clients should keep using the normal User Streams. Will there be an
 update for the User Streams to support having multiple accounts, are the
 docs wrong, or do you really want us to open (in some cases) 10
 connections?

 Tom


 On 8/30/10 8:57 PM, Jesse Stay wrote:
  Freakin' awesome. Nice job guys!
 
  Jesse
 
  On Mon, Aug 30, 2010 at 12:52 PM, Mark McBride mmcbr...@twitter.com
  mailto:mmcbr...@twitter.com wrote:
 
  Site Streams, a new feature on the Streaming API, is now available
 for
  beta testing. Site Streams allows services, such as web sites or
  mobile push services, to receive real-time updates for a large number
  of users without any of the hassles of managing REST API rate limits.
  The initial version delivers events created by, or directed to, users
  that have shared their OAuth token with your application.
 
  Via Site Streams, the following events are streamed immediately and
  without rate limits: Direct Messages, Mentions, Follows, Favorites,
  Tweets, Retweets, Profile changes, and List changes. A subsequent
  version is planned that will optionally deliver each user's home
  timeline.
 
  For additional information on Site Streams and details on how to
 apply
  for access, see the Site Streams Beta documentation at
  http://bit.ly/sitestreams_doc.
 
 ---Mark
 
  http://twitter.com/mccv
 
  --
  Twitter API documentation and resources: http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Change your membership to this group:
  http://groups.google.com/group/twitter-api-announce?hl=en
 
 
  --
  Twitter developer documentation and resources:
 http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk?hl=en

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Site streams and privacy

2010-08-30 Thread jmathai

I haven't kept up on the streaming API but read about the new Site
Steam and it raised some privacy concerns.  Specifically the fact that
direct messages would be streamed from anyone that added your
application.  I understand this was always possible but the stream API
makes it fairly trivial to collect all that data.

It's also a privacy concern because of user intent.  When someone adds
an application my guess is that they're not intending on saying yes,
gain access to my direct messages much less sign up to receive all
my direct messages via a stream.

Anyways, the stream API is awesome...but it's important to understand
how users interact with applications and what their intentions are
when they add (regardless of what they are in fact signing up for).  I
also realize all of this was previously possible but by making it
easier it increases the chances that apps are accessing this data.

Just thought I'd bring it up for discussion :)

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Site streams and privacy

Site Streams do not change anything in the Twitter privacy model. OAuth'ed
applications have always been able to pull your direct messages via the REST
API.

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



On Mon, Aug 30, 2010 at 12:05 PM, jmathai jmat...@gmail.com wrote:

 I haven't kept up on the streaming API but read about the new Site
 Steam and it raised some privacy concerns.  Specifically the fact that
 direct messages would be streamed from anyone that added your
 application.  I understand this was always possible but the stream API
 makes it fairly trivial to collect all that data.

 It's also a privacy concern because of user intent.  When someone adds
 an application my guess is that they're not intending on saying yes,
 gain access to my direct messages much less sign up to receive all
 my direct messages via a stream.

 Anyways, the stream API is awesome...but it's important to understand
 how users interact with applications and what their intentions are
 when they add (regardless of what they are in fact signing up for).  I
 also realize all of this was previously possible but by making it
 easier it increases the chances that apps are accessing this data.

 Just thought I'd bring it up for discussion :)

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] OAuth rate limit of 150

2010-08-30 Thread Roger Ertesvåg

The OAuth rate limit for one of my accounts is stuck at 150. From what
I'm reading, and seeing from other accounts I have, it is my
understanding that it should be 350. What can I do to fix this?


Regards
Roger Ertesvag

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

This is super news.

However, if you're going to force web services to use Site Streams
when it is in production (sites must only use the REST API for data
that is not available through User Streams), then please add the
ability to subscribe only to certain elements. For example, we need
the ability to subscribe to only Follows, or to only Tweets and
Retweets, etc.

You make note that each stream may consume significant bandwidth (
1MB).

If a web service does not make use of the user's Follows, or of the
user's Tweets, then it makes no sense to consume that bandwidth with
the dead-weight of the elements that are not used by the service.

I understand that Site Streams is in beta now. I'm putting in this
request for when it is in production and we are forced to use it.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Site streams and privacy

2010-08-30 Thread jmathai

John,

I know it doesn't introduce anything new (per my original post).

I had a hard time coming up with an example but here's the best I
could do.

When I authorize application FOO to access my account I am giving them
permission to poll for my direct messages. [Agreed]
I am also giving them permission to listen to a stream which contains
my direct messages. [Agreed]
I am also giving Twitter permission to mail them a CD every month with
all my direct messages. [Agreed]

My point is...it's not about a violation of the existing terms.  But
there is a line - which I'm sure you'd draw before mailing out CDs -
which I think the Site Stream is approaching.

I'm not opposed to the Site stream - in fact I hope to use it.  But I
also don't have much personal information on Twitter (it's generally
public - incl. DMs).  But it could be for others.

I'm sure you guys thought about it more than I have but it's worth
bringing up.

On Aug 30, 12:07 pm, John Kalucki j...@twitter.com wrote:
 Site Streams do not change anything in the Twitter privacy model. OAuth'ed
 applications have always been able to pull your direct messages via the REST
 API.

 -John Kaluckihttp://twitter.com/jkalucki
 Twitter, Inc.

 On Mon, Aug 30, 2010 at 12:05 PM, jmathai jmat...@gmail.com wrote:
  I haven't kept up on the streaming API but read about the new Site
  Steam and it raised some privacy concerns.  Specifically the fact that
  direct messages would be streamed from anyone that added your
  application.  I understand this was always possible but the stream API
  makes it fairly trivial to collect all that data.

  It's also a privacy concern because of user intent.  When someone adds
  an application my guess is that they're not intending on saying yes,
  gain access to my direct messages much less sign up to receive all
  my direct messages via a stream.

  Anyways, the stream API is awesome...but it's important to understand
  how users interact with applications and what their intentions are
  when they add (regardless of what they are in fact signing up for).  I
  also realize all of this was previously possible but by making it
  easier it increases the chances that apps are accessing this data.

  Just thought I'd bring it up for discussion :)

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en



-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

We're not forcing people over to Site Streams. If, on the other hand, if you
start to consume Site Streams, we want you to stop regular polling on the
REST API.

If your service is modest, any excess delivery will be modest. Excessive
options add complexity and slow development for what may be little
practical efficiency gain. Bandwidth and CPU are nearly free at 1mbit/sec.
It's all a balance.

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


On Mon, Aug 30, 2010 at 12:15 PM, Dewald Pretorius dpr...@gmail.com wrote:

 This is super news.

 However, if you're going to force web services to use Site Streams
 when it is in production (sites must only use the REST API for data
 that is not available through User Streams), then please add the
 ability to subscribe only to certain elements. For example, we need
 the ability to subscribe to only Follows, or to only Tweets and
 Retweets, etc.

 You make note that each stream may consume significant bandwidth (
 1MB).

 If a web service does not make use of the user's Follows, or of the
 user's Tweets, then it makes no sense to consume that bandwidth with
 the dead-weight of the elements that are not used by the service.

 I understand that Site Streams is in beta now. I'm putting in this
 request for when it is in production and we are forced to use it.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Tweet Button - Need Success, Status Text Callbacks

2010-08-30 Thread Jeremy B

We are also looking for a similar functionality.  Is there anything in
the tweet button API which will easily do this?
thanks,
/jeremy

On Aug 13, 1:05 pm, Adam Stiles a...@stilesoft.com wrote:
 Facebook's JS SDK allows us to do something like theTweetButton...
 pre-populate the status message, use our Application Id, etc. We'd
 love to use thetweetbutton like this too but its missing some
 functionality that we need. The FB JS SDK gives us a javascriptcallbackthat 
 let's us know that a status update was posted
 successfully *and* it gives us the text that was posted. It'd be great
 if we could get the same kind of functionality from thetweetbutton.

 Adam

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Request of xAuth access

2010-08-30 Thread João Paulo Sabino de Moraes

If you're attaching some file at your email, it won't reach
a...@twitter. every kind of image or file has to be sent as url.

jp

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Site streams and privacy


Quoting jmathai jmat...@gmail.com:


I haven't kept up on the streaming API but read about the new Site
Steam and it raised some privacy concerns.  Specifically the fact that
direct messages would be streamed from anyone that added your
application.  I understand this was always possible but the stream API
makes it fairly trivial to collect all that data.

It's also a privacy concern because of user intent.  When someone adds
an application my guess is that they're not intending on saying yes,
gain access to my direct messages much less sign up to receive all
my direct messages via a stream.


That's part of an application developer's responsibility - to make it  
clear what your application *does* on behalf of a user and how users  
can detect when it does something it *shouldn't* do. And yes, very few  
applications fully document that during the oAuth dialog, but it  
*does* need to be done somewhere.


My assumption was, from the nature of the API as announced, that  
Twitter had developed this technology at the prompting of some  
existing partners. It doesn't seem generally applicable to new use  
cases by small shops such as myself. ;-)

--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos



--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Site streams and privacy

2010-08-30 Thread jmathai

On Aug 30, 12:59 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
 That's part of an application developer's responsibility - to make it  
 clear what your application *does* on behalf of a user and how users  
 can detect when it does something it *shouldn't* do. And yes, very few  
 applications fully document that during the oAuth dialog, but it  
 *does* need to be done somewhere.

That's more my point and I'm not arguing that the Stream API shouldn't
exist.  I want to use it myself.  I just don't believe users are
really agreeing to this regardless if it's in the fine print or not.
There's a fine line and it's being approached - that's all.

I think it's a bigger issue with OAuth as a whole.  Users don't really
know what they're handing over since it's not their username and
password.  They continue under a false pretense that their information
is still secure (citation needed).  I don't think more words on the
OAuth flow pages addresses this and the only way to solve this is to
educate users (not an easy task).  I hope in time users have a true
understanding of what it means to allow this app because right now I
don't believe they do.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta


Quoting Dewald Pretorius dpr...@gmail.com:


Here's another issue that probably needs to be considered.

It applies mostly to DMs, because people will tend to use DMs for
sensitive information, and would expect a certain level of privacy.

Right now, an OAuth authorized site can query a user's DMs and do with
that info what it likes. It could present privacy issues, but at least
you have an audit trail of the DM request by the authorized site in
your logs/system.

You lose that audit trail with Site Streams. The DMs are
indiscriminately distributed out to all OAuth authorized sites that
subscribe to the user's stream.

It may not seem like a big deal, because it's status quo minus the
audit trail. Until you're hit with a multi-million dollar class-action
lawsuit for indiscriminately distributing potentially sensitive
information. Then it is a big deal. It's not only the lawsuit, it's a
privacy PR disaster as well.


Ayup - *Twitter* loses an audit trail - they can track sends / TCP  
acknowledgements but have no idea what the receiver is doing with the  
packets. The consuming site must maintain an audit trail, though, right?


Something like this happened at Facebook when they changed their  
developer TOS. Here's the wording they used:


?You must give users control over their data by posting a privacy  
policy that explains what data you collect, and how you will use,  
store, and/or transfer their data. You may cache data you receive from  
the Facebook API in order to improve your application?s user  
experience, but you should try to keep the data up to date. You will  
delete all data you receive from us concerning a user if the user asks  
you to do so, and will provide a mechanism for users to make such a  
request.?


I'm assuming Twitter will want to do something similar, and I'd think  
it would also include honoring the delete messages that come down  
the streams. That could be *very* interesting if the service was doing  
indexing. ;-)

--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Thanks. I've clarified the language.

-John



On Mon, Aug 30, 2010 at 12:42 PM, Dewald Pretorius dpr...@gmail.com wrote:

 John,

 Perhaps you should then rephrase the following at
 http://bit.ly/sitestream_doc

 One Site Streams graduates to production, sites must only use the
 REST API for data that is not available through User Streams or as a
 fall-back data source.

 It's in the first paragraph of Important Items.

 Here's another issue that probably needs to be considered.

 It applies mostly to DMs, because people will tend to use DMs for
 sensitive information, and would expect a certain level of privacy.

 Right now, an OAuth authorized site can query a user's DMs and do with
 that info what it likes. It could present privacy issues, but at least
 you have an audit trail of the DM request by the authorized site in
 your logs/system.

 You lose that audit trail with Site Streams. The DMs are
 indiscriminately distributed out to all OAuth authorized sites that
 subscribe to the user's stream.

 It may not seem like a big deal, because it's status quo minus the
 audit trail. Until you're hit with a multi-million dollar class-action
 lawsuit for indiscriminately distributing potentially sensitive
 information. Then it is a big deal. It's not only the lawsuit, it's a
 privacy PR disaster as well.

 On Aug 30, 4:25 pm, John Kalucki j...@twitter.com wrote:
  We're not forcing people over to Site Streams. If, on the other hand, if
 you
  start to consume Site Streams, we want you to stop regular polling on the
  REST API.
 
  If your service is modest, any excess delivery will be modest. Excessive
  options add complexity and slow development for what may be little
  practical efficiency gain. Bandwidth and CPU are nearly free at
 1mbit/sec.
  It's all a balance.
 
  -John Kaluckihttp://twitter.com/jkalucki
  Twitter, Inc.
 
 
 
  On Mon, Aug 30, 2010 at 12:15 PM, Dewald Pretorius dpr...@gmail.com
 wrote:
   This is super news.
 
   However, if you're going to force web services to use Site Streams
   when it is in production (sites must only use the REST API for data
   that is not available through User Streams), then please add the
   ability to subscribe only to certain elements. For example, we need
   the ability to subscribe to only Follows, or to only Tweets and
   Retweets, etc.
 
   You make note that each stream may consume significant bandwidth (
   1MB).
 
   If a web service does not make use of the user's Follows, or of the
   user's Tweets, then it makes no sense to consume that bandwidth with
   the dead-weight of the elements that are not used by the service.
 
   I understand that Site Streams is in beta now. I'm putting in this
   request for when it is in production and we are forced to use it.
 
   --
   Twitter developer documentation and resources:
 http://dev.twitter.com/doc
   API updates via Twitter:http://twitter.com/twitterapi
   Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
   Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk?hl=en

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

John,

Is that page cached, because the third sentence of the first bullet
under Important Items still says *exactly* the same?

On Aug 30, 5:15 pm, John Kalucki j...@twitter.com wrote:
 Thanks. I've clarified the language.

 -John



 On Mon, Aug 30, 2010 at 12:42 PM, Dewald Pretorius dpr...@gmail.com wrote:
  John,

  Perhaps you should then rephrase the following at
 http://bit.ly/sitestream_doc

  One Site Streams graduates to production, sites must only use the
  REST API for data that is not available through User Streams or as a
  fall-back data source.

  It's in the first paragraph of Important Items.

  Here's another issue that probably needs to be considered.

  It applies mostly to DMs, because people will tend to use DMs for
  sensitive information, and would expect a certain level of privacy.

  Right now, an OAuth authorized site can query a user's DMs and do with
  that info what it likes. It could present privacy issues, but at least
  you have an audit trail of the DM request by the authorized site in
  your logs/system.

  You lose that audit trail with Site Streams. The DMs are
  indiscriminately distributed out to all OAuth authorized sites that
  subscribe to the user's stream.

  It may not seem like a big deal, because it's status quo minus the
  audit trail. Until you're hit with a multi-million dollar class-action
  lawsuit for indiscriminately distributing potentially sensitive
  information. Then it is a big deal. It's not only the lawsuit, it's a
  privacy PR disaster as well.

  On Aug 30, 4:25 pm, John Kalucki j...@twitter.com wrote:
   We're not forcing people over to Site Streams. If, on the other hand, if
  you
   start to consume Site Streams, we want you to stop regular polling on the
   REST API.

   If your service is modest, any excess delivery will be modest. Excessive
   options add complexity and slow development for what may be little
   practical efficiency gain. Bandwidth and CPU are nearly free at
  1mbit/sec.
   It's all a balance.

   -John Kaluckihttp://twitter.com/jkalucki
   Twitter, Inc.

   On Mon, Aug 30, 2010 at 12:15 PM, Dewald Pretorius dpr...@gmail.com
  wrote:
This is super news.

However, if you're going to force web services to use Site Streams
when it is in production (sites must only use the REST API for data
that is not available through User Streams), then please add the
ability to subscribe only to certain elements. For example, we need
the ability to subscribe to only Follows, or to only Tweets and
Retweets, etc.

You make note that each stream may consume significant bandwidth (
1MB).

If a web service does not make use of the user's Follows, or of the
user's Tweets, then it makes no sense to consume that bandwidth with
the dead-weight of the elements that are not used by the service.

I understand that Site Streams is in beta now. I'm putting in this
request for when it is in production and we are forced to use it.

--
Twitter developer documentation and resources:
 http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
   http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
   http://groups.google.com/group/twitter-development-talk?hl=en

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

It's cached. It'll update via a process that is mysterious to me.


On Mon, Aug 30, 2010 at 1:21 PM, Dewald Pretorius dpr...@gmail.com wrote:

 John,

 Is that page cached, because the third sentence of the first bullet
 under Important Items still says *exactly* the same?

 On Aug 30, 5:15 pm, John Kalucki j...@twitter.com wrote:
  Thanks. I've clarified the language.
 
  -John
 
 
 
  On Mon, Aug 30, 2010 at 12:42 PM, Dewald Pretorius dpr...@gmail.com
 wrote:
   John,
 
   Perhaps you should then rephrase the following at
  http://bit.ly/sitestream_doc
 
   One Site Streams graduates to production, sites must only use the
   REST API for data that is not available through User Streams or as a
   fall-back data source.
 
   It's in the first paragraph of Important Items.
 
   Here's another issue that probably needs to be considered.
 
   It applies mostly to DMs, because people will tend to use DMs for
   sensitive information, and would expect a certain level of privacy.
 
   Right now, an OAuth authorized site can query a user's DMs and do with
   that info what it likes. It could present privacy issues, but at least
   you have an audit trail of the DM request by the authorized site in
   your logs/system.
 
   You lose that audit trail with Site Streams. The DMs are
   indiscriminately distributed out to all OAuth authorized sites that
   subscribe to the user's stream.
 
   It may not seem like a big deal, because it's status quo minus the
   audit trail. Until you're hit with a multi-million dollar class-action
   lawsuit for indiscriminately distributing potentially sensitive
   information. Then it is a big deal. It's not only the lawsuit, it's a
   privacy PR disaster as well.
 
   On Aug 30, 4:25 pm, John Kalucki j...@twitter.com wrote:
We're not forcing people over to Site Streams. If, on the other hand,
 if
   you
start to consume Site Streams, we want you to stop regular polling on
 the
REST API.
 
If your service is modest, any excess delivery will be modest.
 Excessive
options add complexity and slow development for what may be little
practical efficiency gain. Bandwidth and CPU are nearly free at
   1mbit/sec.
It's all a balance.
 
-John Kaluckihttp://twitter.com/jkalucki
Twitter, Inc.
 
On Mon, Aug 30, 2010 at 12:15 PM, Dewald Pretorius dpr...@gmail.com
 
   wrote:
 This is super news.
 
 However, if you're going to force web services to use Site Streams
 when it is in production (sites must only use the REST API for
 data
 that is not available through User Streams), then please add the
 ability to subscribe only to certain elements. For example, we need
 the ability to subscribe to only Follows, or to only Tweets and
 Retweets, etc.
 
 You make note that each stream may consume significant bandwidth (
 1MB).
 
 If a web service does not make use of the user's Follows, or of the
 user's Tweets, then it makes no sense to consume that bandwidth
 with
 the dead-weight of the elements that are not used by the service.
 
 I understand that Site Streams is in beta now. I'm putting in this
 request for when it is in production and we are forced to use it.
 
 --
 Twitter developer documentation and resources:
  http://dev.twitter.com/doc
 API updates via Twitter:http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
 
   --
   Twitter developer documentation and resources:
 http://dev.twitter.com/doc
   API updates via Twitter:http://twitter.com/twitterapi
   Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
   Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk?hl=en

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Site streams and privacy


Quoting jmathai jmat...@gmail.com:


On Aug 30, 12:59 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:

That's part of an application developer's responsibility - to make it  
clear what your application *does* on behalf of a user and how users  
can detect when it does something it *shouldn't* do. And yes, very few  
applications fully document that during the oAuth dialog, but it  
*does* need to be done somewhere.


That's more my point and I'm not arguing that the Stream API shouldn't
exist.  I want to use it myself.  I just don't believe users are
really agreeing to this regardless if it's in the fine print or not.
There's a fine line and it's being approached - that's all.

I think it's a bigger issue with OAuth as a whole.  Users don't really
know what they're handing over since it's not their username and
password.  They continue under a false pretense that their information
is still secure (citation needed).  I don't think more words on the
OAuth flow pages addresses this and the only way to solve this is to
educate users (not an easy task).  I hope in time users have a true
understanding of what it means to allow this app because right now I
don't believe they do.


Ayup - and it's only going to get worse as Twitter grows towards its  
500M user goal. For better or worse, Facebook's size and complexity is  
blazing these trails and, assuming good will of the power elite,  
something approaching best practices will emerge.


Twitter is currently both smaller and less complex than Facebook. My  
futurist lens is very cloudy on how Twitter and its user base will  
co-evolve, but I have to assume that a future 500M-user Twitter will  
be different from today's 500M-user Facebook. And I am even less  
certain how much bigger Facebook can get. ;-)


--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Ed,

Developer responsibilities and developer agreements mean absolutely
nothing to that person who wants to abuse users' DMs.

In fact, they will probably trick users to authorize their app with a
neat feature, and then in the background collect received and sent
DMs.

Twitter will not have the foggiest idea of which service it could be,
because they will have no record of API requests, or pattern of
requests, for received and sent DMs.


On Aug 30, 5:15 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
 Quoting Dewald Pretorius dpr...@gmail.com:





  Here's another issue that probably needs to be considered.

  It applies mostly to DMs, because people will tend to use DMs for
  sensitive information, and would expect a certain level of privacy.

  Right now, an OAuth authorized site can query a user's DMs and do with
  that info what it likes. It could present privacy issues, but at least
  you have an audit trail of the DM request by the authorized site in
  your logs/system.

  You lose that audit trail with Site Streams. The DMs are
  indiscriminately distributed out to all OAuth authorized sites that
  subscribe to the user's stream.

  It may not seem like a big deal, because it's status quo minus the
  audit trail. Until you're hit with a multi-million dollar class-action
  lawsuit for indiscriminately distributing potentially sensitive
  information. Then it is a big deal. It's not only the lawsuit, it's a
  privacy PR disaster as well.

 Ayup - *Twitter* loses an audit trail - they can track sends / TCP  
 acknowledgements but have no idea what the receiver is doing with the  
 packets. The consuming site must maintain an audit trail, though, right?

 Something like this happened at Facebook when they changed their  
 developer TOS. Here's the wording they used:

 ?You must give users control over their data by posting a privacy  
 policy that explains what data you collect, and how you will use,  
 store, and/or transfer their data. You may cache data you receive from  
 the Facebook API in order to improve your application?s user  
 experience, but you should try to keep the data up to date. You will  
 delete all data you receive from us concerning a user if the user asks  
 you to do so, and will provide a mechanism for users to make such a  
 request.?

 I'm assuming Twitter will want to do something similar, and I'd think  
 it would also include honoring the delete messages that come down  
 the streams. That could be *very* interesting if the service was doing  
 indexing. ;-)
 --
 M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb

 A mathematician is a device for turning coffee into theorems. - Paul Erdos

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Try getting access to Site Streams without a signed agreement between  
your organization and Twitter prohibiting such shenanigans. ;-)


--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos


Quoting Dewald Pretorius dpr...@gmail.com:


Ed,

Developer responsibilities and developer agreements mean absolutely
nothing to that person who wants to abuse users' DMs.

In fact, they will probably trick users to authorize their app with a
neat feature, and then in the background collect received and sent
DMs.

Twitter will not have the foggiest idea of which service it could be,
because they will have no record of API requests, or pattern of
requests, for received and sent DMs.


On Aug 30, 5:15 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:

Quoting Dewald Pretorius dpr...@gmail.com:





 Here's another issue that probably needs to be considered.

 It applies mostly to DMs, because people will tend to use DMs for
 sensitive information, and would expect a certain level of privacy.

 Right now, an OAuth authorized site can query a user's DMs and do with
 that info what it likes. It could present privacy issues, but at least
 you have an audit trail of the DM request by the authorized site in
 your logs/system.

 You lose that audit trail with Site Streams. The DMs are
 indiscriminately distributed out to all OAuth authorized sites that
 subscribe to the user's stream.

 It may not seem like a big deal, because it's status quo minus the
 audit trail. Until you're hit with a multi-million dollar class-action
 lawsuit for indiscriminately distributing potentially sensitive
 information. Then it is a big deal. It's not only the lawsuit, it's a
 privacy PR disaster as well.

Ayup - *Twitter* loses an audit trail - they can track sends / TCP  
acknowledgements but have no idea what the receiver is doing with the  
packets. The consuming site must maintain an audit trail, though, right?

Something like this happened at Facebook when they changed their  
developer TOS. Here's the wording they used:

?You must give users control over their data by posting a privacy  
policy that explains what data you collect, and how you will use,  
store, and/or transfer their data. You may cache data you receive from  
the Facebook API in order to improve your application?s user  
experience, but you should try to keep the data up to date. You will  
delete all data you receive from us concerning a user if the user asks  
you to do so, and will provide a mechanism for users to make such a  
request.?

I'm assuming Twitter will want to do something similar, and I'd think  
it would also include honoring the delete messages that come down  
the streams. That could be *very* interesting if the service was doing  
indexing. ;-)
--
M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:   
http://groups.google.com/group/twitter-development-talk?hl=en






--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

I think you're missing my point. A signed agreement does not prevent
anything for the evil-minded. At best it establishes the parameters
for damage control by Twitter (revoking access, banning, etc.), except
in this case Twitter won't have the forensics to determine who did the
damage.

On Aug 30, 5:44 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
 Try getting access to Site Streams without a signed agreement between  
 your organization and Twitter prohibiting such shenanigans. ;-)

 --
 M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb

 A mathematician is a device for turning coffee into theorems. - Paul Erdos

 Quoting Dewald Pretorius dpr...@gmail.com:



  Ed,

  Developer responsibilities and developer agreements mean absolutely
  nothing to that person who wants to abuse users' DMs.

  In fact, they will probably trick users to authorize their app with a
  neat feature, and then in the background collect received and sent
  DMs.

  Twitter will not have the foggiest idea of which service it could be,
  because they will have no record of API requests, or pattern of
  requests, for received and sent DMs.

  On Aug 30, 5:15 pm, M. Edward (Ed) Borasky zn...@borasky-
  research.net wrote:
  Quoting Dewald Pretorius dpr...@gmail.com:

   Here's another issue that probably needs to be considered.

   It applies mostly to DMs, because people will tend to use DMs for
   sensitive information, and would expect a certain level of privacy.

   Right now, an OAuth authorized site can query a user's DMs and do with
   that info what it likes. It could present privacy issues, but at least
   you have an audit trail of the DM request by the authorized site in
   your logs/system.

   You lose that audit trail with Site Streams. The DMs are
   indiscriminately distributed out to all OAuth authorized sites that
   subscribe to the user's stream.

   It may not seem like a big deal, because it's status quo minus the
   audit trail. Until you're hit with a multi-million dollar class-action
   lawsuit for indiscriminately distributing potentially sensitive
   information. Then it is a big deal. It's not only the lawsuit, it's a
   privacy PR disaster as well.

  Ayup - *Twitter* loses an audit trail - they can track sends / TCP  
  acknowledgements but have no idea what the receiver is doing with the  
  packets. The consuming site must maintain an audit trail, though, right?

  Something like this happened at Facebook when they changed their  
  developer TOS. Here's the wording they used:

  ?You must give users control over their data by posting a privacy  
  policy that explains what data you collect, and how you will use,  
  store, and/or transfer their data. You may cache data you receive from  
  the Facebook API in order to improve your application?s user  
  experience, but you should try to keep the data up to date. You will  
  delete all data you receive from us concerning a user if the user asks  
  you to do so, and will provide a mechanism for users to make such a  
  request.?

  I'm assuming Twitter will want to do something similar, and I'd think  
  it would also include honoring the delete messages that come down  
  the streams. That could be *very* interesting if the service was doing  
  indexing. ;-)
  --
  M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb

  A mathematician is a device for turning coffee into theorems. - Paul 
  Erdos

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:  
 http://groups.google.com/group/twitter-development-talk?hl=en

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Is there way to post multiple tweets in one API update call?

2010-08-30 Thread K

Hey guys,
I am writing an app that tweets a message typed into a field. My
client is asking if it is possible to split message into multiple
tweets if message is longer than 140 characters. I am writing to see
if there is way to send multiple tweets in one API? If not, I will
need to send multiple update API calls within short duration. Is
there any complication with this? I was wondering if I can possibly
hit API limit this way... :(.
Thank you for your help!
K

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] My cursors problem

2010-08-30 Thread Rick

My topic subject might be spam-attractive but I didn't had any
insperation for a nicer one.

I am playing around for 6 weeks with my cursor problem in PHP. I use
the twitteroauth library and I am unable to solve my issue. I hope
somebody can help me solving my cursor problem.

My current code with error_reporting(E_ALL); returns a couple of
errors. But it seems to not give me any satisfied result I want to (It
only returns the last 100 followers).

?php

// Above the cursor definition I include stuff like twitterOAuth.php
and I have the access tokens etc. I leaved them out of this code for
easyness

$cursor = -1;

$followers = $oauth-get('statuses/followers', array('cursor' =
$cursor));
$totaal = count($followers);

while($totaal  1) {
  for($x=0; $x$totaal; $x++) {
// Here I removed the code so you can see the overall code. Inside
this while I get information on who made his last status. I check them
trought $followers[$x]-status-created_at) and $followers[$x]-
protected) and then I process this information.
  }

 $cursor = $followers-next_cursor;
 $followers = $oauth-get('statuses/followers', array('cursor' =
$cursor));
 $totaal = count($followers);

 $cursor++;
}

?

Thats the code. I removed some of the informatiob so you can easy see
my bone code. What am I doing wrong? Should I process $totaal
different? With this code I only get the last 100 followers and not
anything else.

Thank you for helping me before the basis xAuth ends.

Regards

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] xAuth not Working (Help)

2010-08-30 Thread João Paulo Sabino de Moraes

Hi Everyone,

I´ve got an application account that has already an xAuth access. But I
still got 401 Error saying : Failed to validate oauth signature and token;

I thinks I´m not missing any parameter, the code is in as3 but you can see
the parameteres and more below the encoded signstring .

request = ACCESS;
var vars:String = ;
var urlRequest:URLRequest = new URLRequest(
https://api.twitter.com/oauth/access_token;);
var params : URLVariables = new URLVariables();
params.oauth_consumer_key = consumerKey;
vars += oauth_consumer_key=+consumerKey;
params.oauth_consumer_secret = consumerSecret;
vars += oauth_consumer_secret=+consumerSecret;
 var temp = nonce;
params.oauth_nonce = temp;
vars += oauth_nonce=+temp;
params.oauth_signature_method = HMAC-SHA1;
vars += oauth_signature_method=HMAC-SHA1;
 var temp = time;
params.oauth_timestamp = temp;
vars += oauth_timestamp=+temp;
 params.oauth_version = 1.0;
vars += oauth_version=1.0;
 params.x_auth_mode = client_auth;
vars += x_auth_mode=client_auth;
 params.x_auth_password = password;
vars += x_auth_password=+password;
 params.x_auth_username = user;
vars += x_auth_username=+user;
 var signString:String = POST + encodeURIComponent(
https://api.twitter.com/oauth/access_token;) +  +
encodeURIComponent(vars);
var hmac:HMAC =  Crypto.getHMAC(sha1);
var key:ByteArray = Hex.toArray(
Hex.fromString(encodeURIComponent(consumerSecret) +  +
encodeURIComponent(oauthTokenSecret)));
var data:ByteArray = Hex.toArray( Hex.fromString( signString ) );
var sha:String = Base64.encodeByteArray( hmac.compute( key, data ) );
trace(signString);
params.oauth_signature = encodeURIComponent(sha);



oauth_consumer_key=31NPH6FNUQi5HsWHzSbjQoauth_consumer_secret=jSwOaW3RDS9DnVmKvgHiNrx7sW0QYj9w9lMBL8P6bIoauth_nonce=94252oauth_signature_method=HMAC-SHA1oauth_timestamp=1283202704oauth_version=1.0x_auth_mode=client_authx_auth_password=passWordTestx_auth_username=usernameTest

Ecoded SignString:

POSThttps%3A%2F%2Fapi.twitter.com
%2Foauth%2Faccess_tokenoauth_consumer_key%3D31NPH6FNUQi5HsWHzSbjQ%26oauth_consumer_secret%3DjSwOaW3RDS9DnVmKvgHiNrx7sW0QYj9w9lMBL8P6bI%26oauth_nonce%3D94252%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1283202704%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3DpassWordTest%26x_auth_username%3DusernameTest


thanks



-- 
João Paulo S. de Moraes
+55 81 3432 3804
+55 81 9189 3814 (mobile)

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] xAuth not Working (Help)

Hi João,

Can you share the code you use to actually execute the request? I'd like to
make sure that all the OAuth-related parameters are being sent in the HTTP
header, the x_auth_* parameters should be in the POST body. You shouldn't
have any x_auth parameters in your authorization header, and you shouldn't
have any oauth_* parameters in your POST body.

On first glance, your signature base string appears correct. Have you also
verified that the timestamp on the machine executing the requests is in sync
with our clock?

Thanks,
Taylor



2010/8/30 João Paulo Sabino de Moraes jona...@gmail.com

 Hi Everyone,

 I´ve got an application account that has already an xAuth access. But I
 still got 401 Error saying : Failed to validate oauth signature and token;

 I thinks I´m not missing any parameter, the code is in as3 but you can see
 the parameteres and more below the encoded signstring .

 request = ACCESS;
 var vars:String = ;
 var urlRequest:URLRequest = new URLRequest(
 https://api.twitter.com/oauth/access_token;);
  var params : URLVariables = new URLVariables();
 params.oauth_consumer_key = consumerKey;
  vars += oauth_consumer_key=+consumerKey;
 params.oauth_consumer_secret = consumerSecret;
  vars += oauth_consumer_secret=+consumerSecret;
  var temp = nonce;
 params.oauth_nonce = temp;
 vars += oauth_nonce=+temp;
  params.oauth_signature_method = HMAC-SHA1;
 vars += oauth_signature_method=HMAC-SHA1;
  var temp = time;
 params.oauth_timestamp = temp;
 vars += oauth_timestamp=+temp;
  params.oauth_version = 1.0;
 vars += oauth_version=1.0;
  params.x_auth_mode = client_auth;
 vars += x_auth_mode=client_auth;
  params.x_auth_password = password;
 vars += x_auth_password=+password;
  params.x_auth_username = user;
  vars += x_auth_username=+user;
  var signString:String = POST + encodeURIComponent(
 https://api.twitter.com/oauth/access_token;) +  +
 encodeURIComponent(vars);
  var hmac:HMAC =  Crypto.getHMAC(sha1);
 var key:ByteArray = Hex.toArray(
 Hex.fromString(encodeURIComponent(consumerSecret) +  +
 encodeURIComponent(oauthTokenSecret)));
  var data:ByteArray = Hex.toArray( Hex.fromString( signString ) );
 var sha:String = Base64.encodeByteArray( hmac.compute( key, data ) );
  trace(signString);
 params.oauth_signature = encodeURIComponent(sha);




 oauth_consumer_key=31NPH6FNUQi5HsWHzSbjQoauth_consumer_secret=jSwOaW3RDS9DnVmKvgHiNrx7sW0QYj9w9lMBL8P6bIoauth_nonce=94252oauth_signature_method=HMAC-SHA1oauth_timestamp=1283202704oauth_version=1.0x_auth_mode=client_authx_auth_password=passWordTestx_auth_username=usernameTest

 Ecoded SignString:

 POSThttps%3A%2F%2Fapi.twitter.com
 %2Foauth%2Faccess_tokenoauth_consumer_key%3D31NPH6FNUQi5HsWHzSbjQ%26oauth_consumer_secret%3DjSwOaW3RDS9DnVmKvgHiNrx7sW0QYj9w9lMBL8P6bI%26oauth_nonce%3D94252%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1283202704%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3DpassWordTest%26x_auth_username%3DusernameTest


 thanks



 --
 João Paulo S. de Moraes
 +55 81 3432 3804
 +55 81 9189 3814 (mobile)

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] xAuth not Working (Help)

2010-08-30 Thread Tom van der Woerdt

Actually, it looks very much wrong.

You are including your secret in the Base String and POST. Don't.

Tom


On 8/30/10 11:44 PM, Taylor Singletary wrote:
 Hi João,
 
 Can you share the code you use to actually execute the request? I'd like
 to make sure that all the OAuth-related parameters are being sent in the
 HTTP header, the x_auth_* parameters should be in the POST body. You
 shouldn't have any x_auth parameters in your authorization header, and
 you shouldn't have any oauth_* parameters in your POST body. 
 
 On first glance, your signature base string appears correct. Have you
 also verified that the timestamp on the machine executing the requests
 is in sync with our clock?
 
 Thanks,
 Taylor
 
 
 
 2010/8/30 João Paulo Sabino de Moraes jona...@gmail.com
 mailto:jona...@gmail.com
 
 Hi Everyone,
 
 I´ve got an application account that has already an xAuth access.
 But I still got 401 Error saying : Failed to validate oauth
 signature and token;
 
 I thinks I´m not missing any parameter, the code is in as3 but you
 can see the parameteres and more below the encoded signstring .
 
 request = ACCESS;
 var vars:String = ;
 var urlRequest:URLRequest = new
 URLRequest(https://api.twitter.com/oauth/access_token;);
 var params : URLVariables = new URLVariables();
params.oauth_consumer_key = consumerKey;
 vars += oauth_consumer_key=+consumerKey;
params.oauth_consumer_secret = consumerSecret;
 vars += oauth_consumer_secret=+consumerSecret;
 var temp = nonce;
params.oauth_nonce = temp;
 vars += oauth_nonce=+temp;
params.oauth_signature_method = HMAC-SHA1;
 vars += oauth_signature_method=HMAC-SHA1;
 var temp = time;
params.oauth_timestamp = temp;
vars += oauth_timestamp=+temp;
 params.oauth_version = 1.0;
vars += oauth_version=1.0;
 params.x_auth_mode = client_auth;
vars += x_auth_mode=client_auth;
 params.x_auth_password = password;
vars += x_auth_password=+password;
 params.x_auth_username = user;
 vars += x_auth_username=+user;
 var signString:String = POST +
 encodeURIComponent(https://api.twitter.com/oauth/access_token;) +
  + encodeURIComponent(vars);
 var hmac:HMAC =  Crypto.getHMAC(sha1);
 var key:ByteArray = Hex.toArray(
 Hex.fromString(encodeURIComponent(consumerSecret) +  +
 encodeURIComponent(oauthTokenSecret)));
 var data:ByteArray = Hex.toArray( Hex.fromString( signString ) );
 var sha:String = Base64.encodeByteArray( hmac.compute( key, data ) );
 trace(signString);
 params.oauth_signature = encodeURIComponent(sha);
 
 
 
 
 oauth_consumer_key=31NPH6FNUQi5HsWHzSbjQoauth_consumer_secret=jSwOaW3RDS9DnVmKvgHiNrx7sW0QYj9w9lMBL8P6bIoauth_nonce=94252oauth_signature_method=HMAC-SHA1oauth_timestamp=1283202704oauth_version=1.0x_auth_mode=client_authx_auth_password=passWordTestx_auth_username=usernameTest
 
 Ecoded SignString:
 
 POSThttps%3A%2F%2Fapi.twitter.com
 
 http://2Fapi.twitter.com%2Foauth%2Faccess_tokenoauth_consumer_key%3D31NPH6FNUQi5HsWHzSbjQ%26oauth_consumer_secret%3DjSwOaW3RDS9DnVmKvgHiNrx7sW0QYj9w9lMBL8P6bI%26oauth_nonce%3D94252%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1283202704%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3DpassWordTest%26x_auth_username%3DusernameTest
 
 
 thanks
 
 
 
 -- 
 João Paulo S. de Moraes
 +55 81 3432 3804
 +55 81 9189 3814 (mobile)
 
 -- 
 Twitter developer documentation and resources:
 http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en
 
 
 -- 
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] xAuth not Working (Help)

Good eye, Tom. Thanks -- missed that in my quick once-over.

João -- I had to regenerate your consumer key and secret. You'll want to go
to your application on dev.twitter.com to obtain your keys again.

Thanks,
Taylor



On Mon, Aug 30, 2010 at 2:46 PM, Tom van der Woerdt i...@tvdw.eu wrote:

 Actually, it looks very much wrong.

 You are including your secret in the Base String and POST. Don't.

 Tom


 On 8/30/10 11:44 PM, Taylor Singletary wrote:
  Hi João,
 
  Can you share the code you use to actually execute the request? I'd like
  to make sure that all the OAuth-related parameters are being sent in the
  HTTP header, the x_auth_* parameters should be in the POST body. You
  shouldn't have any x_auth parameters in your authorization header, and
  you shouldn't have any oauth_* parameters in your POST body.
 
  On first glance, your signature base string appears correct. Have you
  also verified that the timestamp on the machine executing the requests
  is in sync with our clock?
 
  Thanks,
  Taylor
 
 
 
  2010/8/30 João Paulo Sabino de Moraes jona...@gmail.com
  mailto:jona...@gmail.com
 
  Hi Everyone,
 
  I´ve got an application account that has already an xAuth access.
  But I still got 401 Error saying : Failed to validate oauth
  signature and token;
 
  I thinks I´m not missing any parameter, the code is in as3 but you
  can see the parameteres and more below the encoded signstring .
 
  request = ACCESS;
  var vars:String = ;
  var urlRequest:URLRequest = new
  URLRequest(https://api.twitter.com/oauth/access_token;);
  var params : URLVariables = new URLVariables();
 params.oauth_consumer_key = consumerKey;
  vars += oauth_consumer_key=+consumerKey;
 params.oauth_consumer_secret = consumerSecret;
  vars += oauth_consumer_secret=+consumerSecret;
  var temp = nonce;
 params.oauth_nonce = temp;
  vars += oauth_nonce=+temp;
 params.oauth_signature_method = HMAC-SHA1;
  vars += oauth_signature_method=HMAC-SHA1;
  var temp = time;
 params.oauth_timestamp = temp;
 vars += oauth_timestamp=+temp;
  params.oauth_version = 1.0;
 vars += oauth_version=1.0;
  params.x_auth_mode = client_auth;
 vars += x_auth_mode=client_auth;
  params.x_auth_password = password;
 vars += x_auth_password=+password;
  params.x_auth_username = user;
  vars += x_auth_username=+user;
  var signString:String = POST +
  encodeURIComponent(https://api.twitter.com/oauth/access_token;) +
   + encodeURIComponent(vars);
  var hmac:HMAC =  Crypto.getHMAC(sha1);
  var key:ByteArray = Hex.toArray(
  Hex.fromString(encodeURIComponent(consumerSecret) +  +
  encodeURIComponent(oauthTokenSecret)));
  var data:ByteArray = Hex.toArray( Hex.fromString( signString ) );
  var sha:String = Base64.encodeByteArray( hmac.compute( key, data ) );
  trace(signString);
  params.oauth_signature = encodeURIComponent(sha);
 
 
 
 
 oauth_consumer_key=31NPH6FNUQi5HsWHzSbjQoauth_consumer_secret=jSwOaW3RDS9DnVmKvgHiNrx7sW0QYj9w9lMBL8P6bIoauth_nonce=94252oauth_signature_method=HMAC-SHA1oauth_timestamp=1283202704oauth_version=1.0x_auth_mode=client_authx_auth_password=passWordTestx_auth_username=usernameTest
 
  Ecoded SignString:
 
  POSThttps%3A%2F%2Fapi.twitter.com
  http://2Fapi.twitter.com
 %2Foauth%2Faccess_tokenoauth_consumer_key%3D31NPH6FNUQi5HsWHzSbjQ%26oauth_consumer_secret%3DjSwOaW3RDS9DnVmKvgHiNrx7sW0QYj9w9lMBL8P6bI%26oauth_nonce%3D94252%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1283202704%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3DpassWordTest%26x_auth_username%3DusernameTest
 
 
  thanks
 
 
 
  --
  João Paulo S. de Moraes
  +55 81 3432 3804
  +55 81 9189 3814 (mobile)
 
  --
  Twitter developer documentation and resources:
  http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk?hl=en
 
 
  --
  Twitter developer documentation and resources:
 http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk?hl=en

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter:

[twitter-dev] adendum to previous mesage about URL shortener

2010-08-30 Thread shane davidson


I forgot to mention that we're working with PHP here.
thanks.
shane

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] implimenting a URL shortener into a PHP script that posts to twitter?

2010-08-30 Thread shane davidson


I've done this in python, but it's an on demand shortener, not automatic.
I get the occasional URL that the API, or a fluke of weirdness, will 
shorten, but I want every tweet, our archival system tweets out, that 
contains a URL, shortened, regardless of URL or tweet length.

Suggestions?
Thanks.
shane

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] My cursors problem

Hey Rick,

The cursor isn't a sequential page number so you can't 'page' through
the results by incrementing it. Instead you need to use the value we
provide in the API response. You can find the cursor for the next page
as the 'next_cursor' value. If you use that value you will be able to
retrieve all the followers.

The alternative method is to call /followers/ids which gives up to
5000 follower IDs in one request. Then, if you need more information
about a follower, you can lookup 100 users details using
/users/lookup.

More information on these two methods is available on our developer
resources site:
  http://dev.twitter.com/doc/get/followers/ids
  http://dev.twitter.com/doc/get/users/lookup

Hope that helps,
Matt

On Mon, Aug 30, 2010 at 2:13 PM, Rick rickstuivenb...@gmail.com wrote:
 My topic subject might be spam-attractive but I didn't had any
 insperation for a nicer one.

 I am playing around for 6 weeks with my cursor problem in PHP. I use
 the twitteroauth library and I am unable to solve my issue. I hope
 somebody can help me solving my cursor problem.

 My current code with error_reporting(E_ALL); returns a couple of
 errors. But it seems to not give me any satisfied result I want to (It
 only returns the last 100 followers).

 ?php

 // Above the cursor definition I include stuff like twitterOAuth.php
 and I have the access tokens etc. I leaved them out of this code for
 easyness

 $cursor = -1;

 $followers = $oauth-get('statuses/followers', array('cursor' =
 $cursor));
 $totaal = count($followers);

 while($totaal  1) {
  for($x=0; $x$totaal; $x++) {
    // Here I removed the code so you can see the overall code. Inside
 this while I get information on who made his last status. I check them
 trought $followers[$x]-status-created_at) and $followers[$x]-
protected) and then I process this information.
  }

  $cursor = $followers-next_cursor;
  $followers = $oauth-get('statuses/followers', array('cursor' =
 $cursor));
  $totaal = count($followers);

  $cursor++;
 }

 ?

 Thats the code. I removed some of the informatiob so you can easy see
 my bone code. What am I doing wrong? Should I process $totaal
 different? With this code I only get the last 100 followers and not
 anything else.

 Thank you for helping me before the basis xAuth ends.

 Regards

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Need help with MGTwitterEngine OAuth/xAuth

2010-08-30 Thread metawops

Hi everyone,

I’m struggling with MGTwitterEngine  OAuth/xAuth here with my Mac OS
X application.
The problem is that I get either SIGTRM or EXC_BAD_ACCESS crashes from
the call of the getXAuthAccessTokenForUsername method. And I just
don’t know what I’m doing wrong!

Here’s the (stripped) code of a very simple demo app, basically. Just
one window with a username  password textfield and a button to start
the action:

-(IBAction)pushLogin:(id)sender
{
  NSString *username = [NSString stringWithString:[tfUsername
stringValue]];
  NSString *password = [NSString stringWithString:[tfPassword
stringValue]];
  if ([username isEqualToString:@] || [password
isEqualToString:@]) {
// at least one of the text fields was empty!
[tfInfo setStringValue:@Please supply a username and a
password!];
  }
  else {
NSString *xAuthAccessToken = [[[NSString alloc] init]
autorelease];
// program crashes at the following line
xAuthAccessToken = [twitterEngine
getXAuthAccessTokenForUsername:username password:password];
[tfInfo setStringValue:xAuthAccessToken];
  }
}

#pragma mark MGTwitterEngine delegate methods
- (void)accessTokenReceived:(OAToken *)token forRequest:(NSString
*)connectionIdentifier
{
  [twitterEngine setAccessToken:token];
  [tfInfo setStringValue:@accessTokenReceived!];
}


Additionally, I set my consumer key  secret in my init method:

- (id) init
{
  self = [super init];
  if (self != nil) {
twitterEngine = [MGTwitterEngine twitterEngineWithDelegate:self];
NSString *consumerKey = @”123…”;
NSString *consumerSecret = @”123456…”;
[twitterEngine setConsumerKey:consumerKey secret:consumerSecret];
  }
  return self;
}

Does anyone has any advice? What am I missing?
(Checked out the latest revisions of MGTwitterEngine  OAuthConsumer.
Is there any Cocoa alternative to MGTwitterEngine that supports OAuth/
xAuth?)

Thank you so much!
Stefan.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Apigee Support for OAuth--

2010-08-30 Thread shanley

Hey all-

A number of Twitter devs are using www.apigee.com (free tools for API
analytics, testing, debugging and protection) so wanted to drop all of
you note to reassure you that we do support APIs using OAuth-

Here's how to do it, using the Twitter API as an example:

1. Do the OAuth dance with the canonical API endpoint (e.g.
api.twitter.com).
2. Once you have a user's token, use it to sign requests' base
strings, which you would also build using the canonical endpoint from
step 1.
3. Then send those signed requests to your Apigee URL, such as
twitter.myusername.apigee.com.

In this way traffic can flow to and from Twitter via your Apigee API
using OAuth.

Our Twitter console for reviewing  sharing requests and responses to
the Twitter API also supports OAuth with your Twitter sign-in:
http://app.apigee.com/console/twitter

Let me know if you have any questions, happy to help out.

Cheers,
Shanley
Apigee Support Team

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] verify_credentials longevity?

2010-08-30 Thread Jud

With the move to OAuth, are we going to see verify_credentials
deprecate?

http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Tweet Button - Need Success, Status Text Callbacks

This sounds like a great idea. Can you add this to our issues and
enhancements tracker so the team knows this would be useful.
  http://code.google.com/p/twitter-api/issues/list

Thanks,
Matt

On Mon, Aug 30, 2010 at 12:21 PM, Jeremy B jjblumenf...@gmail.com wrote:
 We are also looking for a similar functionality.  Is there anything in
 the tweet button API which will easily do this?
 thanks,
 /jeremy

 On Aug 13, 1:05 pm, Adam Stiles a...@stilesoft.com wrote:
 Facebook's JS SDK allows us to do something like theTweetButton...
 pre-populate the status message, use our Application Id, etc. We'd
 love to use thetweetbutton like this too but its missing some
 functionality that we need. The FB JS SDK gives us a javascriptcallbackthat 
 let's us know that a status update was posted
 successfully *and* it gives us the text that was posted. It'd be great
 if we could get the same kind of functionality from thetweetbutton.

 Adam

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] OAuth rate limit of 150

Hi Roger,

It sounds like the OAuth part of your request isn't being seen by our
servers. A rate limit of 150 will be reported whenever you make a
request without authorisation. Can you share the code you are using to
make the requests so we can see what might be going wrong?

Thanks,
Matt

On Mon, Aug 30, 2010 at 11:30 AM, Roger Ertesvåg webfo...@webfokus.no wrote:
 The OAuth rate limit for one of my accounts is stuck at 150. From what
 I'm reading, and seeing from other accounts I have, it is my
 understanding that it should be 350. What can I do to fix this?


 Regards
 Roger Ertesvag

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Team Widget

Hey Ryan,

You may also want to consider using the Streaming API to follow the
users you would have in the list. This would require you to store the
Tweets streamed to you somehow and then echo them out, but it will
mean you'll get them as they happen. You can read more about the
Streaming API here:
http://dev.twitter.com/pages/streaming_api

In particular you might want to use the follow predicate of the track method:
http://dev.twitter.com/pages/streaming_api_methods#statuses-filter

Best,
Matt

On Mon, Aug 30, 2010 at 6:19 AM, artesea ryancul...@gmail.com wrote:
 Suddenly wondered if a search would be better, trying q=from:steve OR
 from:mike gives me exactly what I need.

 Ryan

 On Aug 30, 11:14 am, artesea ryancul...@gmail.com wrote:
 Just wondering if anyone knew a way to get a decent team widget?

 We've got a conference coming up with a variety of events, whilst some
 might only have one member of the team going using the standard widget
 works as expected.
 However if we have two people going, we want both sets of tweets to
 appear in the same widget. I've tried creating a list and using that,
 however it has the following problem.

 Example tweets
 @steve timeline
 10:01 wow this is great
 10:05 i can't believe they are going to release this
 10:16 @mike me too!
 10:19 and that's all folks

 @mike timeline
 10:04 seriously i want one of these
 10:14 @jim they are coming out tomorrow? i'm getting one straight
 away!
 10:20 can't wait for the morning

 Team timeline
 10:01 steve - wow this is great
 10:04 mike - seriously i want one of these
 10:05 steve - i can't believe they are going to release this
 10:16 steve - @mike me too!
 10:19 steve - and that's all folks
 10:20 mike - can't wait for the morning

 The tweet @jim is missing because jim isn't in the list. And we are
 expecting quite a few @s to other people in the hall. All these useful
 tweets will be missing.

 I also have the same problem when trying to save all these tweets
 using the api as 
 thehttp://api.twitter.com/1/USER/lists/LISTNAME/statuses.jsondoes the
 same thing.
 For the saving I could go through both @mike and @steve timelines, and
 merge the two together. As it's a one of process this isn't too bad,
 however for the live tweets it would require me to set up a cron job
 checking for new tweets from either (and we could have up to 6 people
 tweeting at a time), creating a modified timeline containing both, and
 then creating a hacked widget to read my modified timeline instead of
 the lists.

 Is there a simpler method at getting all tweets from 2-6 users
 directly from the API?

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Count not working for url's with 2+ parameters

Hey Lukas,

The Tweet Button currently allows you to share one URL at a time.
Can you give an example of what you require two URLs on one button for?

Best,
Matt

On Sun, Aug 29, 2010 at 3:11 PM, Lukas lukas.winzenr...@gmail.com wrote:
 Hi

 The tweet button does not count if the data-url has more than 1 url
 parameters
 http://www.jobscout24.ch/JS24Web/JobView/JobDetail.aspx?lng=dewl=1jid=1979742
 (this is the canonical url)

 The request to the count api takes only the last one of the parameters
 into accout, all the others are lost ;-(

 Is there a workarouond for this issue (none of the encodings i tried
 seems to work, even with use of data-counturl) or does anyone know if
 theres a fix planned for this?

 Thanks
 Lukas

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] PHP Search Example

Hi lu5ceh,

It looks like you aren't using the Search API. Have you tried making
your request to:
http://search.twitter.com/search.json?q=%23linux

Best,
Matt

On Mon, Aug 30, 2010 at 9:10 AM, lu5ceh ignacio.santo...@gmail.com wrote:
 I using

 $SearchHashTag = $connection-get(search, array('q' = '#linux'));

 To search tweets and returns:

 stdClass Object ( [statuses] = Array ( [0] = 45070895939 [1] =
 45070904709 [2] = 45070915901 [3] = 45070939637 [4] = 45070939741
 [5] = 45071173851 [6] = 45071383871 [7] = 45071675705 [8] =
 45071733003 [9] = 45071893347 [10] = 45071895895 [11] = 45071907613
 [12] = 45071909151 [13] = 45072271867 [14] = 45072442737 [15] =
 45072456829 ) [created_in] = 0.010282 )

 how to return Tweets with #linux hashtag?!

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Twitter api request for a user's timeline w/ count=40 is returning ~20 records, why?

In addition, please ensure you are using the correct host for requests
to the API. Instead of http://twitter.com you should be using
http://api.twitter.com

Best,
Matt

On Mon, Aug 30, 2010 at 7:30 AM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
 With the timeline methods, the count you provide is optimistic in that
 you'll get up to those number of results if they are available.
 In most cases, the results you aren't seeing would be retweets, which aren't
 returned in user_timeline without an include_rts=true parameter.
 Taylor

 On Sat, Aug 28, 2010 at 6:09 PM, Erik Vold erikvv...@gmail.com wrote:

 why does
 http://twitter.com/statuses/user_timeline.xml?screen_name=erikvoldpage=0count=40
 return ~15 results? should it not return 40 results?

 http://dev.twitter.com/doc/get/statuses/user_timeline

 Erik

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Need a confirmation - no way to count number of tweets found when searching for a keyword?

Hey omri,

I'm not sure about adding a field to the response. It is possible that
number would be out of date by the time it is requested. Instead you
could count up the number of Tweets the first time you run the search,
and then use since_id with the ID of the most recent Tweet you have
for future calls. That way you only need to maintain a record of the
count and then add the number of Tweets returned since you last made a
request.

Matt

On Mon, Aug 30, 2010 at 1:20 AM, omri omridek...@gmail.com wrote:
 hi,
 I think that terrence wanted to know if there is a way to get the
 total number of results for a word in one click instead of
 downloading14 pages (each page has 100 results...)
 is there a place in your API whree you store the total number of
 search results
 can you add this field to your API?
 thanks.

 On 22 יולי, 23:23, Pascal Jürgens
 lists.pascal.juerg...@googlemail.com wrote:
 Hi Terrence,

 if you use the tracking stream, you will get limit notices telling you how 
 manytweetsyou missed (because the stream didn't provide the volume). This 
 should be a way to determine absolute N. Notice that this still means that 
 spamtweetsmight be filtered.

 Pascal

 On 22.Jul2010, at 10:44, Terrence Tee wrote:



  Then only i know thenumberof results available?
  Any smarter way? No?

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: 401 errors calling access_token

Hi Marc,

Did you get a chance to send this information through to our support team?
Best,
Matt

On Fri, Aug 27, 2010 at 5:16 PM, Marc Mims marc.m...@gmail.com wrote:
 * Taylor Singletary taylorsinglet...@twitter.com [100827 11:11]:
 Can you provide any more details about the error response you're
 giving (like the actual body of the error response)?

 Taylor, I will capture the full request and response.  I assume they are
 not suitable for posting in a public forum.  Should I email the to
 a...@twitter.com instead?

 Can you share an example of a signature base string and POST body that
 failed in this example?

 Have you verified that the clock on the device/system originating the
 request is in sync with Twitter's (returned in the Date header of
 every request) by about 5 minutes?

 Times are within 1 second.

 Do you have any successes to compare against?

 The error seems to occur infrequently.  The vast majority of calls
 succeed on exactly the same code path.

 The calls are being made with Perl the Net::Twitter library (of which I
 am the author).  Net::Twitter is used by many twitter apps and web apps.

 Are your HTTP methods in agreement between what your client is
 actually using (a GET) and the method declared in your signature base
 string?

 Yes.

        -Marc

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Install twurl without root access?

You should be able to install gems to your local user folder by
running 'gem install'. The only other thing you would then need to do,
as @epc says, is to add twurl either to you path variable or as an
alias to it's actual location.

Best,
Matt

On Fri, Aug 27, 2010 at 10:02 PM, @epc epcoste...@gmail.com wrote:
 I know nothing about Ruby, however gem install twurl appears to
 install it into ~/.gem/ruby/1.8/bin on OS X.  You then need to put
 that directory in your shell’s path variable.
 --
 -ed costello

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] a new field retweeted and retweeted tweet's status id

Hi hiro,

The ID of the retweeted status will not be available through these new
fields. Instead you should use either user_timeline or retweets_of_me
to get the retweeted status ID.
This could be a useful enhancement though so please file it on our
issues and enhancements tracker:
http://code.google.com/p/twitter-api/issues/list

Best,
Matt

On Sun, Aug 29, 2010 at 9:14 PM, hiro hirokazu.takat...@gmail.com wrote:
 Hi,

 A new field retweeted: (true|false) is very useful. It reduces
 calling statuses/retweeted_by_me.

 Recent API changes and new fields at Twitter API Announcements
 http://groups.google.com/group/twitter-api-announce/browse_thread/thread/4b08544f2c02d68f/32f81a8b2fa31a3d?show_docid=32f81a8b2fa31a3d

 I also need retweeted tweet's status id in home_timeline to undo my
 retweet.
 Does anybody know the id also be provide after activation of the
 retweeted field?
 If the id does not provide in home_timeline, statuses/
 retweeted_by_me is needed again.

 hiro

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Tweet Button Not Working

Hi Bruce,

Glad to hear it worked. We've seen this problem with iWeb but don't
have a better solution than data-url at the moment. If we do find a
way we'll update the documentation and let everyone know.

Best,
Matt

On Fri, Aug 27, 2010 at 11:36 PM, Bruce Aguilar bruce...@gmail.com wrote:
 I think that may have worked.  It's a pain in the patootie that I have to
 manually enter the web address in for each blog post, but still, it's better
 than nothing I guess.
 Thanks!

 On Fri, Aug 27, 2010 at 7:38 AM, Taylor Singletary
 taylorsinglet...@twitter.com wrote:

 You might find some help with working with the Tweet Button and iWeb
 here: http://bit.ly/tweet-button-iweb
 Taylor

 On Fri, Aug 27, 2010 at 7:20 AM, Yensid98 bruce...@gmail.com wrote:

 I've added the Tweet Button to my website for easy sharing of my
 content, but it's not working properly.  FYI, I'm operating at a very
 basic level here and have designed my website with iWeb.

 I've added the button to my page with no trouble but when I click on
 the Tweet Button, the link that gets posted only shows a tiny image of
 the Tweet Button itself and not my website.  Upon further inspection
 I've noticed the following added to the end of my page's url: _files/
 widget2_markup.html.  The correct url doesn't have this info.  In
 fact, deleting it from the address does bring up the page correctly.

 I have selected the Tweet Button to post the url for the page that
 it's posted on and not a custom url.

 Is this an incompatibility with iWeb?  Any help would be appreciated.

 Thanks!

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en



 --
  - Bruce
    What if the Hokey-Pokey really is what it's all about?

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] verify_credentials longevity?

Hey Jud,

There are no plans to deprecate verify_credentials. It's use is still
valid for OAuth as it allows you to check if the user token and secret
you have are still good.

Best,
Matt

On Mon, Aug 30, 2010 at 3:44 PM, Jud jvale...@gmail.com wrote:
 With the move to OAuth, are we going to see verify_credentials
 deprecate?

 http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Why only getting 4 results back?

2010-08-30 Thread Don Rhummy

I am using the search API and ajax to get the latest posts of a
specific user (to be displayed on a web page). Even when I use the
twitter widget ( http://twitter.com/goodies/widget_search ) it only
shows the last 5 posts. But if I do an RSS search, it shows 20
results! What could be wrong?

How do I get it to show more than 5 posts?

See example here:

Using twitter widget ( http://twitter.com/goodies/widget_search ), use
this search term:

from:unwiredben

RSS Feed:
http://twitter.com/statuses/user_timeline/784057.rss

How do I fix this?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Cron Jobs w/ twitter auth

2010-08-30 Thread Mahmoud Sakr

I created a twitter account, and a simple cron job that tweets every certain
period of time.

I fear my authentication mechanism might be affected by tonight's deadline,
is it? I use the following code to send twitter the tweet (the code that is
executed in the cron job)

/**
 * Tweets a new status given a statues, username, and password
 * @param status Status to tweet
 * @param username Username of account to post through
 * @param password Password of account to post through
 * @return void
 */
function tweet($status = 'Hello World', $username, $password) {
$status = urlencode(stripslashes(urldecode($status)));
$curl = curl_init();
curl_setopt($curl, CURLOPT_URL, 'http://www.twitter.com/statuses/update.xml'
);
curl_setopt($curl, CURLOPT_CONNECTTIMEOUT, 2);
curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($curl, CURLOPT_POST, 1);
curl_setopt($curl, CURLOPT_POSTFIELDS, status=$status);
curl_setopt($curl, CURLOPT_USERPWD, $username:$password);
curl_exec($curl);
curl_close($curl);
}

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Open Source CMS Module and Consumer Secret

2010-08-30 Thread John SJ Anderson

 I think it's far better developer/business practice to design
 *proprietary* applications that are secure and register them with Twitter
 using xAuth.

As has been said time and time again, proprietary is not a solution
for this, as any non-hosted app using OAuth can have the keys
extracted from it.

Additionally, some of us would like to write Free or Open Source
applications, that people can use on their own machines, without
requiring them to register as Twitter developers. It used to be
possible to do this. sigh

j.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Since Id on Favourites (recap)

Hey Daniel,

Thanks for pointing this out. I've reopened the original ticket
indicating this needs documenting:
   http://code.google.com/p/twitter-api/issues/list?cursor=125

Thanks,
Matt

On Fri, Aug 27, 2010 at 10:59 AM, Daniel Ribeiro dan...@gmail.com wrote:
 This issue has came up two years ago (http://groups.google.com/group/
 twitter-development-talk/browse_thread/thread/4e6b9b0ae26db3bf/
 84a9f110942a07b9?lnk=gstq=since_id+favorites#84a9f110942a07b9).

 The feature is still working, and still undocumented (as far as I
 know). Am i wrong? Is it documented somehwere other than its api
 (somewhere like global search parameters), and is it supported? If
 not, what is that status update on this issue (will it be supported,
 can it be removed without warnings)?

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: New SSL certificate issue with WTK 2.5.2

Hey Netroboost,

If the device doesn't support wildcard SSL these isn't much that can
be done except to use HTTP. This isn't recommended but if you have no
choice it's all you can do.

The only caveats to know about are:
* xAuth requires SSL so won't be available to any devices that do not
support our certificate
* transmitting OAuth secrets without SSL increases their risk of being
compromised

Hope that helps,
Matt


On Fri, Aug 27, 2010 at 3:18 AM, Netroboost netrobo...@gmail.com wrote:

 Hi Matt,

 Thank you for your response. Yes, I was finally able to get rid of the
 exception with the method you suggested.

 However as far as I know the issue extends beyond the Sun Java WTK.
 Various handset manufacturers have different implementations of this
 JSR and while some do accept wildcard SSL certificates, some do not.

 In such a case wouldn't it be sensible for mobile app developers to
 use the HTTP method as a fail-safe method for authentication? Is there
 any catch to this?

 Regards,

 Amit.


 On Aug 26, 6:22 am, Matt Harris thematthar...@twitter.com wrote:
 Hi Amit,

 This is an issue with the Sun WTK 2.5.2 not accepting wildcard SSL
 certificates and not with the Twitter API. In the future we would like
 to move to a single domain certificate but there is no date as to when
 that will be.

 Whilst it isn't something we like you to do, the OAuth process isn't
 forbidden over SSL, just strongly discouraged. This means HTTP could
 be used - but again, this is discouraged.

 Instead, as wildcard SSL certificates are perfectly valid I recommend
 asking on the developer forums for the Sun WTK to see if support will
 be added to the toolkit itself.

 Best,
 Matt



 On Mon, Aug 23, 2010 at 12:35 AM, Netroboost netrobo...@gmail.com wrote:
  Hi,

  Has this issue been resolved yet?

  I am using Sun WTK 2.5.2 and facing the same issue. The error message
  reads:

  Subject alternative name did not match site name

  Please help if anyone knows how to deal with this.

  Thanks,

  Amit.

  On Jul 23, 10:18 pm, Matt Harris thematthar...@twitter.com wrote:
  Hi,

  I've seen similar reports for other service providers about this issue as
  well. My concern is wildcard certificates are perfectly valid and are
  described in RFC2818 [1]. I'm not sure why Sun WTK doesn't support them or
  of any workarounds but I would suggest asking on their support channels.

  If there are any changes on our systems we will be communicate them 
  through
  this developer mailing list.

  Best,
  Matt

  1.http://www.ietf.org/rfc/rfc2818.txt

  On Fri, Jul 23, 2010 at 4:56 AM, bjcoredev jme...@gmail.com wrote:
   How  will we be warned when  api.twitter.com fixed SSL certificate
   will be effective ?

   On 22 juil, 21:17, John Adams j...@twitter.com wrote:
Unfortunately, the current situation is that api.twitter.com is on a
wildcard certificate.

We have plans to move it a fixed SSL certificate in the near future, 
but
   no
definite date yet.

-j

On Thu, Jul 22, 2010 at 11:50 AM, bjcoredev jme...@gmail.com wrote:

 My app doesn't use the mobile site.

 My twitter client is written in J2ME (Java Micro Edition) and is not
 using the mobile site but the Twitter API.

 I m coding  my client with WTK 2.5.2 Sun Wireless Toolkit (like many
 other Java mobile developers) and since  the 21/07/2001 1AM GMT
 my app  running under WTK can't access the url
https://api.twitter.com/oauth/access_token
 because the WTK CAN'T HANDLE WILDCARD SSL certificates.
 returning the error:Subject alternative name did not match site
 name.

 I'have read that real (real devices opposite to the emulator) mobile
 JAVA platforms (Sony ericsson,WM 5.0,..)  don't accept wildcard SSL
 certificates so twitter clients using twitter API  written in J2ME
 running under these platform can't access the url
https://api.twitter.com/oauth/access_token
 anymore so can't process xAuth authentication wich will be mandatory
 on 15 august
 So .

 On 22 juil, 20:20, John Adams j...@twitter.com wrote:
  The mobile site has used a wildcard certificate for the last two
   years;
 Did
  you recently begin experiencing this issue or was your code 
  working
   in
 the
  past?

  -j

  On Thu, Jul 22, 2010 at 6:43 AM, bjcoredev jme...@gmail.com 
  wrote:
   It seems that SUN WTK 2.5.2 doesn't accept wildcard certificates
   I hope that mobile platforms accept wildcard SSL certificates. 
   If
   this
   not the case, it will make twitter xAuth/oAuth unusable

   Regards

   On 22 juil, 14:57, bjcoredev jme...@gmail.com wrote:
Hi

My mobile app logged to twitter using xAuth and was working 
like
   a
charm until the last SSL certicate changed
(seehttp://
   groups.google.com/group/twitter-development-talk/browse_thread...)

My app logs correctly with the new

Re: [twitter-dev] Why only getting 4 results back?

Hi Don,

Search only has an index of 5 days and in that period @unwiredben only
made 5 posts.
For what you want to do the profile widget maybe more suitable:
http://twitter.com/goodies/widget_profile

Hope that helps,
Matt

On Mon, Aug 30, 2010 at 4:35 PM, Don Rhummy donrhu...@gmail.com wrote:
 I am using the search API and ajax to get the latest posts of a
 specific user (to be displayed on a web page). Even when I use the
 twitter widget ( http://twitter.com/goodies/widget_search ) it only
 shows the last 5 posts. But if I do an RSS search, it shows 20
 results! What could be wrong?

 How do I get it to show more than 5 posts?

 See example here:

 Using twitter widget ( http://twitter.com/goodies/widget_search ), use
 this search term:

    from:unwiredben

 RSS Feed:
 http://twitter.com/statuses/user_timeline/784057.rss

 How do I fix this?

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk?hl=en




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] How to get results older than last 100 tweets from a profile or search

2010-08-30 Thread Pablo Augusto

Hello,

I'm wondering if its possible to get back the twits from one account for
last 3 days for example.
im useing a class that do the follow search to capture tweets:

$request  = 'http://search.twitter.com/search.'.$this-type;
 $request .= '?q='.urlencode($this-query);

Using the methos of this class i do the fololow search:

$search = new TwitterSearch();
$search-from('@username');
$search-contains('#hashtag');
$search-since(22554873450);
$results = $search-rpp(100)-results();

But i only get the last 100 results (the newest ever)
I just try to put a low number at SINCE:

for example: $search-since(21554873450);

Buts aver show the last newest results.


Anyone knows how can i get results older than last 100 newest in any querry,
class, function, etc?

if anyone can help, ill be graceful.



*
*
*Pablo Augusto*
 MSN: m...@pabloaugusto.com
SKYPE: sk...@pabloaugusto.com
EMAIL: cont...@pabloaugusto.com
SITE: http://webtags.com.br

 [image: Linkedin] http://linkedin.com/in/pabloaugusto [image:
Twitter]http://twitter.com/pabloaugusto
 [image: Facebook][image: Flickr]
http://flickr.com/photos/pabloaugusto [image:
Youtube] http://youtube.com/pabloaugustoo [image:
FormSpring]http://formspring.me/pabloaugust0 [image:
LastFM] http://lastfm.com.br/user/pabloaugustoo [image:
DeviantART]http://deviantart.com/pabloaugustoo [image:
Tumblr] http://pabloaugusto.tumblr.com/ [image:
Vimeo]http://vimeo.com/pabloaugusto [image:
del.icio.us] http://del.icio.us/pabloaugusto [image:
Slideshare]http://slideshare.net/pabloaugusto [image:
Friendfeed] http://friendfeed.com/pabloaugusto

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Why only getting 4 results back?

2010-08-30 Thread Don Rhummy

I know there's no rate limits on search like on user stuff (well there
are, but they're pretty big) and you don't have to worry about oAuth.
Is that the case for profile too?

On Aug 30, 9:35 pm, Matt Harris thematthar...@twitter.com wrote:
 Hi Don,

 Search only has an index of 5 days and in that period @unwiredben only
 made 5 posts.
 For what you want to do the profile widget maybe more suitable:
    http://twitter.com/goodies/widget_profile

 Hope that helps,
 Matt



 On Mon, Aug 30, 2010 at 4:35 PM, Don Rhummy donrhu...@gmail.com wrote:
  I am using the search API and ajax to get the latest posts of a
  specific user (to be displayed on a web page). Even when I use the
  twitter widget (http://twitter.com/goodies/widget_search) it only
  shows the last 5 posts. But if I do an RSS search, it shows 20
  results! What could be wrong?

  How do I get it to show more than 5 posts?

  See example here:

  Using twitter widget (http://twitter.com/goodies/widget_search), use
  this search term:

     from:unwiredben

  RSS Feed:
 http://twitter.com/statuses/user_timeline/784057.rss

  How do I fix this?

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list
  Change your membership to this 
  group:http://groups.google.com/group/twitter-development-talk?hl=en

 --

 Matt Harris
 Developer Advocate, Twitterhttp://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: [twitter-api-announce] Streaming API access limits increased