Re: [twitter-dev] Re: consistency and ecosystem opportunities

2011-03-16 Thread Caliban Darklock 
On Mon, Mar 14, 2011 at 8:43 AM, Dewald Pretorius  wrote:
>
> Would you mind taking a stab at clarifying Section 5.E of the new TOS,
> which reads, "You may not use Twitter Content or other data collected
> from end users of your Client to create or maintain a separate status
> update or social network database or service."

I believe this primarily exists to say "you may not use our own API to
compete with us."

But it does seem overly broad.

-- 
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

[twitter-dev] Re: consistency and ecosystem opportunities

2011-03-16 Thread Jef Poskanzer 
On Mar 16, 10:56 pm, jwinkle  wrote:
> For Facebook...network people together to share pics and relationship
> status.  You could probably make facebook server code OSS...it's the
> existing network in-place that keeps people there...it was first and it has
> a brand.

Actually the only reason Diaspora is getting any traction at all as a
Facebook replacement is that Facebook management consistently act like
dickheads.  Twitter take note.

-- 
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

[twitter-dev] Re: consistency and ecosystem opportunities

2011-03-16 Thread jwinkle 
@steveE:

You've made a fantastic argument.  The "official reasoning" stated in the 
original message is clearly contradictory as you point out...I think any 
jury would tilt their heads on that cross-x.  

I've been sitting on this for a few days and can only make some distant 
observations. Being relatively new to twitter (and to the API -- and 
especially to the dynamic going on at present) I'm trying to put this in 
context of corporate motivation *vis-a-vis* the User Experience  with 
Twitter Clients.

The apps I use on my iphone and Mac are...let's say...*very much possible*to 
improve upon IMO.  It is not comprehensible to me why Twitter would want 
to squelch* **something new or different* *introduced*  with regards to the 
User eXperience...*especially* for new users...with Twitter clients.  As a 
programmer...it's the first thing I wanted to do -- and the whole reason I 
started digging in the API in the first place a few weeks agoto bring 
something new to the table that I don't see there.  It seems many people on 
this site feel similarly with regards to existing Clients.  Innovation is 
far from over on the Client side...and...seemingly...should be encouraged as 
many posters have pointed out.

There is justifiable motivation for Twitter to capitalize on their 
service...it is brilliant, categorically historical, and as a comm channel 
blurs the lines between casual chat and causality in real-world events of 
true historical nature.  But is Twitter trying to put its own clients "on 
every desk and in every home?"

My personal opinion is that the threat to the company is not in the access 
to the twitter stream backend (data mining, streams, etc...)...it's to the 
frontend (the firehose backend is being 3rd partied already a la gnip.com).  
The user still has to enter 160 chars --somehow/where/way, and  if that 
stream were ever diverted --  game over.  A Twitter client is that front 
end.  The user entering text into a client is the *sine qua non* of 
Twitter.  That's not a local firehose per user...that's a sparse tweet ... 
once or twice a minute peak.  But the Twitter client frontend is the 
gateway, and it's not that hard to code a basic Twitter client via the API, 
so there can be a lot of Twitter clients out there...and some of them might 
be better than Twitter's.   Is this what they are trying to control?

For Google (search) ...it is to use their search engine and free services to 
bring you to advertising.  If users started using another search engine, 
Google doesn't get data.  Google's search engine has pretty good legs so 
far...and it's proprietary of course.  You enter search text on any handful 
of *standard* web browsers.

For Facebook...network people together to share pics and relationship 
status.  You could probably make facebook server code OSS...it's the 
existing network in-place that keeps people there...it was first and it has 
a brand.  Facebook gets a lot of traffic on their web clients...and a lot of 
data on what people say to each other.  You mostly post your status via *
Facebook's* clients:  web pages via standard browsers or *their* mobile 
apps.

For Twitter...there is an in-place network all right, but you can post your 
status (160 *golden* characters) via any number of clients. 

Is this really the threat??  If so...it would seem that most of the API 
accessibility would just steadily disappear over time...

@jameswinkle

-- 
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

[twitter-dev] Re: consistency and ecosystem opportunities

2011-03-16 Thread Steve Eley 
On Mar 11, 4:18 pm, Ryan Sarver  wrote:
>
> With more people joining Twitter and accessing the service in multiple ways,
> a consistent user experience is more crucial than ever.  As we talked about
> last April, this was our motivation for buying Tweetie and developing our
> own official iPhone app.  It is the reason why we have developed official
> apps for the Mac, iPad, Android and Windows Phone, and worked with RIM on
> their Twitter for Blackberry app. As a result, the top five ways that people
> access Twitter are official Twitter apps.

Something doesn't sound right here.  The official reasoning has some
contradictions in it:

* You're telling us that Twitter's own apps are topping the market,
and that an overwhelming majority of people are engaging with Twitter
using your own tools.

* In the same message, you say that people are confused about how to
engage with Twitter. You blame non-standard third party interfaces --
but if they're just a small minority of user contact points with
Twitter, wouldn't the impact be fairly low-level and mitigated by the
superior first-party experience?

* In that message and in subsequent followups, you tell us that client
applications will be "held to a higher bar."  This seems to imply that
the standards for acceptance or rejection are qualitative; however,
the revised Terms of Service imply that they are objective.  Which is
it?  Is it "If you implement X, we'll cut you off" -- or is it "We
encourage you not to implement X, but if you do, we'll decide whether
you're any good at it?"

Fundamentally, here's what doesn't smell right to me: if the superior
quality of Twitter's first-party platform is winning in the
marketplace, as you say it is, _why bother with this?_  The perceived
threat to the user experience doesn't make sense.  New users who don't
understand Twitter yet aren't going to pick up third-party clients;
they're going to follow the brand name.  They'll go to Twitter.com, or
buy a book, or ask their friends.  (If the books or friends are
confused, new API terms won't help.)

GOOD third-party clients don't compete with Twitter for new user
share.  They pick up the power users who've used Twitter for a while
and want to use it more, or who have particular needs or tastes, or
who _like_ crazy non-standard designs.  Shutting them down won't help
new users, and it won't enable current users to do things better.
It'll just turn power users into non-power users, or in some cases
into non-users.  The most valuable users don't settle for 'good
enough.'  If Twitter doesn't let them do things their own way, they'll
find a platform that does, or make one.

BAD third-party clients don't compete with Twitter at all.  They just
don't have users.  People don't use things that suck.  For the most
part, things that suck are rarely even noticed.  A million bad rock
bands aren't a threat to the Rolling Stones, and a million bad Twitter
applications aren't a threat to Twitter.

Finally, there's the damping effect on improvement.  Most of the
innovation in Twitter did not originate within Twitter.  Good ideas
climb upwards, and the best make it to the top of the canopy (the
official platform).  Bad ideas become compost and lessons learned.  If
you don't encourage this competition for sunlight, everything rots or
fossilizes.  This is obvious.  Smart people won't fail to consider it.

I think Ryan and Raffi know this.  I think it's even possible that
they agree with some of it but can't say so.  I can't imagine that the
backlash would take anyone at Twitter by surprise; it's inconceivable
that there was no discussion at all about the repercussions of telling
developers what they can and can't develop.  Ryan and Raffi are
technical people, and they advocate for the geeks.  Limiting the
freedom to create isn't the sort of decision that gets made by
technical people, or for technical reasons.

Something else is going on.  This was a business decision, probably
made from the top in defiance of cost/benefit analyses from those who
built the platform, and wrapped up as customer advocacy.  It doesn't
make _sense_, because the customers were never really at risk, but
then that wasn't the goal.  Corporate policy statements always have to
tell you how they're making things better, even if no one believes it,
because an honest "We need to make a profit" leaves a bad taste in PR
mouths.

Even so, though...  Something feels off.  This doesn't make
_intrinsic_ sense, not just marketing sense.  Someone is obviously
looking a few moves ahead, but what's the upside?  Twitter's delivered
a major upset to developers, but they're at no real risk from them and
have relatively few immediate revenue channels to protect.  The up-and-
coming revenue channels could have been worked into the API, and third
party clients pushed to leverage and grow them.  Instead, they're
being blocked.  "If you're winning, you don't need to change the
rules" is logic any businessman should understand.

So what's going

Re: [twitter-dev] Re: Requesting increased access levels for Streaming API

2011-03-16 Thread M. Edward (Ed) Borasky 
On Wed, 16 Mar 2011 09:10:13 -0700 (PDT), "Ryan Sarver (@rsarver)" 
 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: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Counting tweets by date

2011-03-16 Thread tripti 
Hi Everyone,
 I am working with Twitter 4j API and I want to count the number of
tweets that I posted last month. I came across getUserTimeline()
function but it displays just 20 recent tweets.
Has anyone done this before? Does anyone know how should I approach
this problem? Does twitter 4j have any function in place to enable us
to do this?

Thank you in advance for your help,
Tripti

-- 
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

[twitter-dev] twitter verified

2011-03-16 Thread Dean Collins 
Who is responsible for Twitter verified? I have someone who I'm helping
out with some Facebook stuff who just told me this is no longer possible
to get accounts twitter verified.

 

Yes you would have heard of them - yes it's appropriate to get this
account verified.

 

 

 

Regards,

Dean Collins
Cognation Inc
d...@cognation.net
 +1-212-203-4357   New York
+61-2-9016-5642   (Sydney in-dial).
+44-20-3129-6001 (London in-dial).

 

-- 
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

Re: [twitter-dev] Re: Requesting increased access levels for Streaming API

2011-03-16 Thread Hank Williams 
Ryan,

Are site streams actually available? As far as I can tell whitelisting is gone 
and site streams are in private beta meaning that it is now impossible to 
launch a website that needs access to twitter data. if I have misread the 
situation, please advise.

Thanks,
Hank

On Mar 16, 2011, at 12:10 PM, "Ryan Sarver (@rsarver)"  
wrote:

> We should have been more clear, but elevated levels of streaming was
> included in the previous statement about ending the whitelisting
> program. There are open levels for each stream or you can contact Gnip
> if you are looking for elevated access for the purposes of data
> analysis.
> 
> 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.
> 
> Hope that helps clarify.
> 
> Best, Ryan
> 
> On Mar 16, 1:47 am, Scott Wilcox  wrote:
>> Highly unlikely. At the present time it's either the Streaming API or using 
>> GNIP.
>> 
>> I don't believe there are any use cases where they would provide you with 
>> elevated Streaming API access to the level you desire.
>> 
>> Sent from my iPhone
>> 
>> On 16 Mar 2011, at 04:23, "manusis"  wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> Yeah I went through gnip in detail but their pricing is excessively
>>> expensive especially when I care only about twitter data and not the
>>> hundred other sources that they provide. I was hoping that if not
>>> "partner track", twitter might be open to give at least "restricted
>>> track" access to developers.
>> 
>>> On Mar 15, 8:10 pm, hax0rsteve  wrote:
 From that same post 
 :http://groups.google.com/group/twitter-development-talk/browse_thread...
>> 
> Developers
> interested in elevated access to the Twitter stream for the purpose of
> research or analytics can contact our partner Gnip for more
> information.
>> 
 Fromhttp://gnip.com/
>> 
> Gnip and Twitter have partnered to bring more Twitter feeds to Gnip 
> customers. Check out Power Track for 100% guaranteed coverage firehose 
> filtering and all commercial Twitter data, only from Gnip.
>> 
 Fromhttp://gnip.com/twitter/power-track
>> 
>• The only feed of its kind: Twitter firehose filtering with 100% 
> coverage guaranteed
>• Boolean operators, unwound URLs, and matching within unwound URLs 
> supported
>• Keyword, username, and location filtering supported
>• Unlimited capacity: no restrictions on filter parameters or results 
> volume - Premium Feed
>• Pay for what you get - pricing depends on Tweet volume delivered - 
> Premium Feed
>• Contact i...@gnip.com for more information - Premium Feed
>> 
 HTH
>> 
 On 15 Mar 2011, at 15:04, manusis wrote:
>> 
> Thanks Augusto.
>> 
> But the same thread indicates that tools like Streaming API will
> replace whitelisting. So it does not make sense for me for Streaming
> API to put under the same umbrella as whitelisting.
>> 
> "Since then, we've added new, more efficient tools for developers,
> including lookups, ID lists, authentication and the Streaming API.
> Instead of whitelisting, developers can use these tools to create
> applications and integrate with the Twitter platform."
>> 
> On Mar 15, 7:41 pm, Augusto Santos  wrote:
>> I think the answer is you never will.
>> This kind of benefit might follow the same rules that whitelist, that 
>> will
>> no longer be supported just as the thread below 
>> said.http://groups.google.com/group/twitter-development-talk/browse_thread...
>> 
>> On Tue, Mar 15, 2011 at 6:58 AM, manusis  wrote:
>>> The streaming API mentions about different access roles but does not
>>> indicate how one could apply for them.
>> 
>>> "The default access level allows up to 400 track keywords, 5,000
>>> follow userids and 25 0.1-360 degree location boxes. Increased access
>>> levels allow 100,000 follow userids (“shadow” role), 400,000 follow
>>> userids (“birddog” role), 10,000 track keywords (“restricted track”
>>> role), 200,000 track keywords (“partner track” role), and 200 0.1-360
>>> degree location boxes (“locRestricted” role). Increased track access
>>> levels also pass a higher proportion of statuses before limiting the
>>> stream."
>> 
>>> For our product, we need "shadow" and "partner track" access roles.
>>> Could somebody shed any light on how one could apply for the increased
>>> access levels?
>> 
>>> Thanks,
>>> Rajiv
>> 
>>> --
>>> 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
>> 
>> --
>> 氣
>> 
> --
> Twitter developer documentation

[twitter-dev] Re: Requesting increased access levels for Streaming API

2011-03-16 Thread Ryan Sarver (@rsarver) 
We should have been more clear, but elevated levels of streaming was
included in the previous statement about ending the whitelisting
program. There are open levels for each stream or you can contact Gnip
if you are looking for elevated access for the purposes of data
analysis.

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.

Hope that helps clarify.

Best, Ryan

On Mar 16, 1:47 am, Scott Wilcox  wrote:
> Highly unlikely. At the present time it's either the Streaming API or using 
> GNIP.
>
> I don't believe there are any use cases where they would provide you with 
> elevated Streaming API access to the level you desire.
>
> Sent from my iPhone
>
> On 16 Mar 2011, at 04:23, "manusis"  wrote:
>
>
>
>
>
>
>
> > Yeah I went through gnip in detail but their pricing is excessively
> > expensive especially when I care only about twitter data and not the
> > hundred other sources that they provide. I was hoping that if not
> > "partner track", twitter might be open to give at least "restricted
> > track" access to developers.
>
> > On Mar 15, 8:10 pm, hax0rsteve  wrote:
> >> From that same post 
> >> :http://groups.google.com/group/twitter-development-talk/browse_thread...
>
> >>> Developers
> >>> interested in elevated access to the Twitter stream for the purpose of
> >>> research or analytics can contact our partner Gnip for more
> >>> information.
>
> >> Fromhttp://gnip.com/
>
> >>> Gnip and Twitter have partnered to bring more Twitter feeds to Gnip 
> >>> customers. Check out Power Track for 100% guaranteed coverage firehose 
> >>> filtering and all commercial Twitter data, only from Gnip.
>
> >> Fromhttp://gnip.com/twitter/power-track
>
> >>>    • The only feed of its kind: Twitter firehose filtering with 100% 
> >>> coverage guaranteed
> >>>    • Boolean operators, unwound URLs, and matching within unwound URLs 
> >>> supported
> >>>    • Keyword, username, and location filtering supported
> >>>    • Unlimited capacity: no restrictions on filter parameters or results 
> >>> volume - Premium Feed
> >>>    • Pay for what you get - pricing depends on Tweet volume delivered - 
> >>> Premium Feed
> >>>    • Contact i...@gnip.com for more information - Premium Feed
>
> >> HTH
>
> >> On 15 Mar 2011, at 15:04, manusis wrote:
>
> >>> Thanks Augusto.
>
> >>> But the same thread indicates that tools like Streaming API will
> >>> replace whitelisting. So it does not make sense for me for Streaming
> >>> API to put under the same umbrella as whitelisting.
>
> >>> "Since then, we've added new, more efficient tools for developers,
> >>> including lookups, ID lists, authentication and the Streaming API.
> >>> Instead of whitelisting, developers can use these tools to create
> >>> applications and integrate with the Twitter platform."
>
> >>> On Mar 15, 7:41 pm, Augusto Santos  wrote:
>  I think the answer is you never will.
>  This kind of benefit might follow the same rules that whitelist, that 
>  will
>  no longer be supported just as the thread below 
>  said.http://groups.google.com/group/twitter-development-talk/browse_thread...
>
>  On Tue, Mar 15, 2011 at 6:58 AM, manusis  wrote:
> > The streaming API mentions about different access roles but does not
> > indicate how one could apply for them.
>
> > "The default access level allows up to 400 track keywords, 5,000
> > follow userids and 25 0.1-360 degree location boxes. Increased access
> > levels allow 100,000 follow userids (“shadow” role), 400,000 follow
> > userids (“birddog” role), 10,000 track keywords (“restricted track”
> > role), 200,000 track keywords (“partner track” role), and 200 0.1-360
> > degree location boxes (“locRestricted” role). Increased track access
> > levels also pass a higher proportion of statuses before limiting the
> > stream."
>
> > For our product, we need "shadow" and "partner track" access roles.
> > Could somebody shed any light on how one could apply for the increased
> > access levels?
>
> > Thanks,
> > Rajiv
>
> > --
> > 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
>
>  --
>  氣
>
> >>> --
> >>> 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
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitter

Re: [twitter-dev] - Each http request (home tweet) json data count

2011-03-16 Thread Georgooty varghese 
Thanks Taylor ..

I shall check it,

Regards,
George



On Wed, Mar 16, 2011 at 8:05 PM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> Hi George,
>
> The count parameter on timelines is more of an "up to" parameter -- you
> should get no more than the count value, but you won't be guaranteed exactly
> the number you asked for either.
>
> For legacy reasons, most timeline methods don't include retweets in the
> default response. By adding the query parameter include_rts=true to your
> requests, you'll be more likely to get the number of results you are looking
> for since they are included in the original underlying payload (and are
> often the "missing" tweets you are looking for when the default returns less
> than what you're asking for).
>
> Taylor
>
> @episod  - Taylor Singletary - Twitter
> Developer Advocate
>
>
> On Wed, Mar 16, 2011 at 7:29 AM, Georgooty varghese 
> wrote:
>
>> Dear Twitter,
>>
>> I have implemented a twitter client in C. I have used xAuth
>> authentication.
>>
>> I have used pagination for each http request for home page/user time line
>> request.
>>
>> Please look the below url, this was used for getting home tweets
>>
>> *http://api.twitter.com/1/statuses/home_timeline.json?page=1*
>>
>> This http request response json data count is 17 other times may be 20
>> I did not get consistent 20,,
>>
>>
>>
>> I expect the count is 20.
>>
>> My question is
>>
>> to getting 20 count of each http request, what can I do for the http
>> request?
>>
>> Could you please help me..
>>
>> I am waiting for your response..
>>
>> Regards,
>> George
>>
>>  --
>> 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
>>
>
>

-- 
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

Re: [twitter-dev] - Each http request (home tweet) json data count

2011-03-16 Thread Taylor Singletary 
Hi George,

The count parameter on timelines is more of an "up to" parameter -- you
should get no more than the count value, but you won't be guaranteed exactly
the number you asked for either.

For legacy reasons, most timeline methods don't include retweets in the
default response. By adding the query parameter include_rts=true to your
requests, you'll be more likely to get the number of results you are looking
for since they are included in the original underlying payload (and are
often the "missing" tweets you are looking for when the default returns less
than what you're asking for).

Taylor

@episod  - Taylor Singletary - Twitter Developer
Advocate


On Wed, Mar 16, 2011 at 7:29 AM, Georgooty varghese wrote:

> Dear Twitter,
>
> I have implemented a twitter client in C. I have used xAuth authentication.
>
>
> I have used pagination for each http request for home page/user time line
> request.
>
> Please look the below url, this was used for getting home tweets
>
> *http://api.twitter.com/1/statuses/home_timeline.json?page=1*
>
> This http request response json data count is 17 other times may be 20
> I did not get consistent 20,,
>
>
>
> I expect the count is 20.
>
> My question is
>
> to getting 20 count of each http request, what can I do for the http
> request?
>
> Could you please help me..
>
> I am waiting for your response..
>
> Regards,
> George
>
>  --
> 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
>

-- 
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

[twitter-dev] - Each http request (home tweet) json data count

2011-03-16 Thread Georgooty varghese 
Dear Twitter,

I have implemented a twitter client in C. I have used xAuth authentication.

I have used pagination for each http request for home page/user time line
request.

Please look the below url, this was used for getting home tweets

*http://api.twitter.com/1/statuses/home_timeline.json?page=1*

This http request response json data count is 17 other times may be 20
I did not get consistent 20,,



I expect the count is 20.

My question is

to getting 20 count of each http request, what can I do for the http
request?

Could you please help me..

I am waiting for your response..

Regards,
George

-- 
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

Re: [twitter-dev] Look up user's friends/followers who have authenticated your app?

2011-03-16 Thread Scott Wilcox 
At present there are no endpoints that can provide this. You would have to use 
your manual approach to achieve this.

On 16 Mar 2011, at 08:57, Dukeman330 wrote:

> Is there a way to specifically do a search for a user's friends/
> followers who have allowed access to your particular app?  Right now
> my approach is to store twitter uid's in a database whenever people
> authenticate, grab the user's friends/followers, and compare it
> against that database.  This seems like I'm passing around more
> information than is necessary, though, and I would prefer to do the
> "allowed" check on twitter's end.

-- 
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

Re: [twitter-dev] Is it possible to programmatically create Twitter accounts?

2011-03-16 Thread Scott Wilcox 
At present, no.

On 16 Mar 2011, at 10:37, Nimisha wrote:

> Hi,
> 
> Can I create a twitter account using the API?
> 
> Thanks,
> Nimisha

-- 
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

[twitter-dev] Re: How to send tweets from multiple accounts without having to login

2011-03-16 Thread Ken D. 
You will have stored the tokens for those accounts that you control
and on behalf of which you want to send Tweets. You no longer need to
authenticate via Twitter, just be logged in to your own system.

You can use a form that includes a SELECT tag allowing the choice of
account to use when tweeting. Bear in mind that consistently tweeting
the same tweets from multiple accounts is probably not a very good
idea.

As an aside, re-reading the TOS, I wonder whether this pattern on a
public web site - whereby a user is enabled to send Tweets without
passing the "Connect with Twitter" step -  requires display of "the
end user's Twitter identity, including visible display of the end
user's avatar, Twitter user name, and the Twitter bird mark". (Rules
III.3)


On Mar 16, 8:12 am, Laddi  wrote:
> HI,
>
>  I have registered application onhttp://dev.twitter.com/. Now please
> tell how to send tweets from multiple accounts without having to
> login.
>
> Thanks
> satinder singh hundal

-- 
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

[twitter-dev] Search/Query a user list

2011-03-16 Thread jslor 
Hi,

Is there a way to search statuses in an user list by keywords? I came
up with the following solutions but I hope there is a better way of
doing this:

Using REST and search API:
Get members from the defined list using the REST API. Create a query
with all usernames of the members seperated with OR and add the
keywords to the q.

Using REST and stream API:
Same as the first solution only then different parameter syntax for
the stream API.

Is there an option that I'm missing which is better?

Thanks,

Jeroen

-- 
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

[twitter-dev] User Search

2011-03-16 Thread arnaud 
Hello everybody, i try to make a little app wich use the twitter API.
I get the access token and i want to make a user search but i can't
find the good url.

I tried this : "http://api.twitter.com/1/users/show.xml?
screen_name=dougw" just to know if it works and i get this :



  1401881
  Doug Williams
  dougw
  San Francisco, CA
.

It's fine but then i tried this : "http://api.twitter.com/1/users/
search.json?q=Doug%20Wiliams"
and i get this  :  "The remote server returned an error: (401)
Unauthorized."

I don't understand why it doesn't work ...

Thank you.

-- 
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

[twitter-dev] Is it possible to programmatically create Twitter accounts?

2011-03-16 Thread Nimisha 
Hi,

Can I create a twitter account using the API?

Thanks,
Nimisha

-- 
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

[twitter-dev] Look up user's friends/followers who have authenticated your app?

2011-03-16 Thread Dukeman330 
Is there a way to specifically do a search for a user's friends/
followers who have allowed access to your particular app?  Right now
my approach is to store twitter uid's in a database whenever people
authenticate, grab the user's friends/followers, and compare it
against that database.  This seems like I'm passing around more
information than is necessary, though, and I would prefer to do the
"allowed" check on twitter's end.

-- 
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

[twitter-dev] How to send tweets from multiple accounts without having to login

2011-03-16 Thread Laddi 
HI,

 I have registered application on http://dev.twitter.com/. Now please
tell how to send tweets from multiple accounts without having to
login.


Thanks
satinder singh hundal

-- 
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

[twitter-dev] HTTP response - length field

2011-03-16 Thread sureshkm 
Hi,

I've been using "http://api.twitter.com/1/statuses/
friends_timeline.xml" to get the tweets for a particular account.

Most of the time, i get the #tweets 1 less than the given count.
The response carries the "length" parameter which has value -1. What
does it mean?

Example: for the request with "count=3", i get only 2 tweets.

Help is very much appreciated.

Thanks,
sureshkm@

-- 
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

[twitter-dev] Retweets and Mentions not returning for few accounts

2011-03-16 Thread DR.Smartbridge 
Hi,

In an application where integration is in place, we are using
Twitterizer API to get the list of Tweets, Retweets and Mentions using
oAuth authentication. For few accounts, using Twitterizer API Tweets
are returning but Retweets and Mentions are not being returned and for
few accounts we are able to get Tweets, Retweets and Mentions.

Is there any limitation why Retweets and Mentions are not being
returned for few accounts? It does not seem to be authentication issue
as Tweets are retrieved for that account.

Please suggest what could be wrong and if there are any limitations in
getting Retweets and Mentions please update.

Thank you,
Smartbridge

-- 
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

[twitter-dev] Starting point for blocks/blocking data?

2011-03-16 Thread Gerry Mulvenna 
Can anybody tell me if there is a cut-off date for the data returned by the 
blocks/blocking API call?

A few early-adopter Twitter users who have tried my tool http://blockedby.me 
are reporting that they expected their list of blocked users to be much 
bigger, so I'm speculating that Twitter is only providing data for this API 
call from a certain date.

Thanks

Gerry

-- 
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

[twitter-dev] Re: Twitter group API

2011-03-16 Thread Ken D. 
er, there might be..

For "Group" substitute "list". Maximum is 500 followers/list.
If they are following you, you can message them.
Where's the problem?

On Mar 15, 9:25 pm, Tim Haines  wrote:
> No, there's not.
>
> On Tue, Mar 15, 2011 at 1:03 PM, Richard  wrote:
> > Does anyone know if there is program available to create several
> > groups using one Twitter account and allowing you to message each of
> > those groups individually?
>
> > For example -
>
> > Twitter.com/username
> >    Group 1 (100 followers)
> >    Group 2 (56 followers)
> >    Group 3 (77 followers)
>
> > I would like to send separate messages to each of those groups.
> > Please let me know if you know of any way to do this via API or a 3rd
> > party program.  Thank you.
>
> > --
> > 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

-- 
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

[twitter-dev] Re: Signature generation issue

2011-03-16 Thread lappynet 
Yep, that's exactly what my token request looks like, but I get 401
every time... :(

On Mar 15, 10:47 pm, Taylor Singletary 
wrote:
> Hi Georgina,
>
> I'm sure you're pretty close to figuring this out. A few tips when you've
> gotten to this point:
>
> - Make sure that you're transporting the request correctly
>   - If you're using header-based OAuth, make sure that your HTTP
> Authorization header is being properly setup and formatted. This will be
> language-specific. Also make sure that you aren't repeating any of the
> oauth_* parameters in the POST body or URL of your actual executed request.
> Only parameters that don't begin with oauth_* should appear in the POST body
> or query string. (In other words, don't present double authentication)
>   - Make sure that your HTTP verbs are in agreement
>     - If you're sending a POST, make sure your HTTP client is actually
> sending a POST and that your OAuth signature base string's method component
> matched
>
> Here's a quick walkthrough of all the steps involved in obtaining an access
> token (though with my keys instead of yours).. note the signature base
> string, authorization header, URL, and POST body for each step (keeping in
> mind that the authorize step is kind of special in that it happens in a
> browser).
>
> Request Token Step
> --
> Request URL:https://api.twitter.com/oauth/request_token
> HTTP Method: POST
> POST body: (empty)
> Signature Basestring:
> POST&https%3A%2F%2Fapi.twitter.com
> %2Foauth%2Frequest_token&oauth_callback%3Dhttp%253A%252F%252Flocalhost%253A 
> 3005%252Fthe_dance%252Fprocess_callback%253Fservice_provider_id%253D1%26oau 
> th_consumer_key%3DOqEqJeafRSF10jBMStrZg%26oauth_nonce%3DK7ny27JTpKVsTgdyLdD 
> fmQQWVLERj2zAK5BslRsqyw%26oauth_signature_method%3DHMAC-SHA1%26oauth_timest 
> amp%3D1300228849%26oauth_version%3D1.0
>
> Authorization Header: OAuth
> oauth_nonce="K7ny27JTpKVsTgdyLdDfmQQWVLERj2zAK5BslRsqyw",
> oauth_callback="http%3A%2F%2Flocalhost%3A3005%2Fthe_dance%2Fprocess_callbac 
> k%3Fservice_provider_id%3D1",
> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1300228849",
> oauth_consumer_key="OqEqJeafRSF10jBMStrZg",
> oauth_signature="Pk%2BMLdv028fxCErFyi8KXFM%2BddU%3D", oauth_version="1.0"
>
> Response Body:
> oauth_token=IPPjb9gdAB15Gnw7to8idfCfePqJgem9MVyhcEkPsU&oauth_token_secret=x 
> xxx&oauth_callback_confirmed=true
>
> Authorization Step
> -
> Request 
> URL:https://api.twitter.com/oauth/authorize?oauth_token=IPPjb9gdAB15Gnw7t...
> HTTP Method: GET
> POST Body: N/A
> Signature Basestring: N/A
> Authorization Header: N/A
>
> Access Token Step
> -
> Request URL:https://api.twitter.com/oauth/access_token
> HTTP Method: POST
> POST Body: (empty)
>
> Signature Basestring:
> POST&https%3A%2F%2Fapi.twitter.com
> %2Foauth%2Faccess_token&oauth_consumer_key%3DOqEqJeafRSF10jBMStrZg%26oauth_ 
> nonce%3DFCKJcpPIhJpOLV1VQtP560IH0rKI9jMPrlkzqQWoA%26oauth_signature_method% 
> 3DHMAC-SHA1%26oauth_timestamp%3D1300228855%26oauth_token%3DIPPjb9gdAB15Gnw7 
> to8idfCfePqJgem9MVyhcEkPsU%26oauth_verifier%3DPmThbFiYNd3TOoFRBbFwwRRPHB3Pl 
> kFbxmX4lCqmnc%26oauth_version%3D1.0
>
> Authorization Header: OAuth
> oauth_nonce="FCKJcpPIhJpOLV1VQtP560IH0rKI9jMPrlkzqQWoA",
> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1300228855",
> oauth_consumer_key="OqEqJeafRSF10jBMStrZg",
> oauth_token="IPPjb9gdAB15Gnw7to8idfCfePqJgem9MVyhcEkPsU",
> oauth_verifier="PmThbFiYNd3TOoFRBbFwwRRPHB3PlkFbxmX4lCqmnc",
> oauth_signature="AFJr%2BdS%2FmWgPbMtJR3vdwMA4cTk%3D", oauth_version="1.0"
>
> Response Body:
> oauth_token=819797-bAOfajtcYw8xHm1UQ3v5V5WfUb90zN7OWlWmvl8ZU0&oauth_token_s 
> ecret=x&user_id=819797&screen_name=episod
>
>
>
>
>
>
>
> On Tue, Mar 15, 2011 at 7:22 AM, lappynet  wrote:
> > Thanks for everyone's help on this. I think that I now have this
> > working (twitter documentation values match up).
>
> > My problem now is that although I'm confident of my algorithm, twitter
> > is always responding 401. I've debugged my network service and the
> > message being returned is Incorrect Signature. I do not understand how
> > this can be... :S
>
> > On Mar 15, 6:03 am, kamesh SmartDude 
> > wrote:
> > > Hai lappynet,
>
> > > I Used GET method to retrive the Request Token And I Avoided the OAuth
> > > Callback, because it was registered when i registered my app.
>
> > > Below is the method how i am  doing.
>
> > >  ** SignatureBase String is *
>
> > > GET&https%3A%2F%2Fapi.twitter.com
> > > %2Foauth%2Frequest_token&oauth_consumer_key%3D
>
> > %26oauth_nonce%3DydBxFJKdzK%26oauth_signature_method%3DHMAC-SHA1%26oauth_ti
> > mestamp%3D1300167727%26oauth_version%3D1.0
>
> > > Signature Key U are appending "&" and it is correct.
>
> > > i am adding the oauth header like below
>
> > > OAuth realm="Twitter API", oauth_consumer_key=,
> > > oauth_nonce=ydBxFJKdzK,
> > oauth_signature=89%2BSoLKBdE%2FeHN5PFRxNl3G7tNo%3D,
> > > oauth_signature_method=HMAC-SHA1, oauth_timestamp=1300167727,
> > > oauth_version=1

Re: [twitter-dev] Re: Requesting increased access levels for Streaming API

2011-03-16 Thread Scott Wilcox 
Highly unlikely. At the present time it's either the Streaming API or using 
GNIP.

I don't believe there are any use cases where they would provide you with 
elevated Streaming API access to the level you desire.

Sent from my iPhone

On 16 Mar 2011, at 04:23, "manusis"  wrote:

> Yeah I went through gnip in detail but their pricing is excessively
> expensive especially when I care only about twitter data and not the
> hundred other sources that they provide. I was hoping that if not
> "partner track", twitter might be open to give at least "restricted
> track" access to developers.
> 
> On Mar 15, 8:10 pm, hax0rsteve  wrote:
>> From that same post 
>> :http://groups.google.com/group/twitter-development-talk/browse_thread...
>> 
>>> Developers
>>> interested in elevated access to the Twitter stream for the purpose of
>>> research or analytics can contact our partner Gnip for more
>>> information.
>> 
>> Fromhttp://gnip.com/
>> 
>>> Gnip and Twitter have partnered to bring more Twitter feeds to Gnip 
>>> customers. Check out Power Track for 100% guaranteed coverage firehose 
>>> filtering and all commercial Twitter data, only from Gnip.
>> 
>> Fromhttp://gnip.com/twitter/power-track
>> 
>>>• The only feed of its kind: Twitter firehose filtering with 100% 
>>> coverage guaranteed
>>>• Boolean operators, unwound URLs, and matching within unwound URLs 
>>> supported
>>>• Keyword, username, and location filtering supported
>>>• Unlimited capacity: no restrictions on filter parameters or results 
>>> volume - Premium Feed
>>>• Pay for what you get - pricing depends on Tweet volume delivered - 
>>> Premium Feed
>>>• Contact i...@gnip.com for more information - Premium Feed
>> 
>> HTH
>> 
>> On 15 Mar 2011, at 15:04, manusis wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> Thanks Augusto.
>> 
>>> But the same thread indicates that tools like Streaming API will
>>> replace whitelisting. So it does not make sense for me for Streaming
>>> API to put under the same umbrella as whitelisting.
>> 
>>> "Since then, we've added new, more efficient tools for developers,
>>> including lookups, ID lists, authentication and the Streaming API.
>>> Instead of whitelisting, developers can use these tools to create
>>> applications and integrate with the Twitter platform."
>> 
>>> On Mar 15, 7:41 pm, Augusto Santos  wrote:
 I think the answer is you never will.
 This kind of benefit might follow the same rules that whitelist, that will
 no longer be supported just as the thread below 
 said.http://groups.google.com/group/twitter-development-talk/browse_thread...
>> 
 On Tue, Mar 15, 2011 at 6:58 AM, manusis  wrote:
> The streaming API mentions about different access roles but does not
> indicate how one could apply for them.
>> 
> "The default access level allows up to 400 track keywords, 5,000
> follow userids and 25 0.1-360 degree location boxes. Increased access
> levels allow 100,000 follow userids (“shadow” role), 400,000 follow
> userids (“birddog” role), 10,000 track keywords (“restricted track”
> role), 200,000 track keywords (“partner track” role), and 200 0.1-360
> degree location boxes (“locRestricted” role). Increased track access
> levels also pass a higher proportion of statuses before limiting the
> stream."
>> 
> For our product, we need "shadow" and "partner track" access roles.
> Could somebody shed any light on how one could apply for the increased
> access levels?
>> 
> Thanks,
> Rajiv
>> 
> --
> 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
>> 
 --
 氣
>> 
>>> --
>>> 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
> 
> -- 
> 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

-- 
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