On Wed, 16 Mar 2011 09:10:13 -0700 (PDT), "Ryan Sarver (@rsarver)" <ryan.sar...@gmail.com> wrote:

Also as we stated before, you can use User Streams or Site Streams and
get more data by getting more users to authorize your application.

Ryan, it's not as simple as "getting more users to authorize your application." You need to get *all* your users to *explicitly* authorize the application's *exact* usage of their data! Users tend not to "read the fine print". I'd hate to see some data collection / analytics application make some assumptions based on the implicit openness of the tweet stream and then get nailed by a bunch of angry users. Angry users tend to write to their Congressmen and Senators. ;-)

Managing a *single* user's User Streams feed is a relatively straightforward coding task - I've got a smallish Perl script that can do it for my own account. Managing multiple users' Site Streams is a much more complex endeavor, and to use that mechanism for a data collection / analytics application is ludicrous IMHO. Somehow, the notion of "the right tool for the job" seems to have been ignored. ;-)

http://twitter.com/znmeb http://borasky-research.net

"A mathematician is a device for turning coffee into theorems." -- Paul Erdős

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: 

Reply via email to