[twitter-dev] Re: Questions about friendship/create

[pl]

Thanks for the explanation - that's made it a lot easier to
understand.

Seems that I am actually doing the right thing, even if it was only by
virtue of not really understanding what the other options were for...



On Feb 4, 7:26 pm, Taylor Singletary 
wrote:
> This is pretty easy to miss -- "notifications" in this context enables the
> target user to be among those the "current user" receives SMS notifications
> for (if they have that feature enabled) -- it's the equivalent of sending a
> POST to notifications/follow for the user.
>
> The default "follow" behavior on Twitter.com is just the simple POST to
> friendships/create you're already doing.
>
> As for include_entities in this context -- probably not necessary unless you
> were going to display the "just followed" user's most recent status and
> wanted to use entities to help you render it.
>
> @episod  - Taylor Singletary - Twitter Developer
> Advocate
>

-- 
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: Streaming API stopwords

[L. Mohan Arun]

> Does anyone have experience using a list of stopwords to reduce noise
> when making streaming API requests to statuses/filter? I have a basic
> list (e.g. "a","an", "and", etc.) but wonder if anyone out there is
> using something more comprehensive.
>
> Thanks,
>
> Kenny

Kenny,

Simply google
http://www.lextek.com/manuals/onix/stopwords1.html

- Mohan

-- 
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: 401: Unauthorized (Python)

[Matt Harris]

Hi John,

That dict object doesn't contain the response body. In the response body we 
give an error reason such as 'Invalid signature', or 'timestamp out of bounds'.

Best,
Matt

On Feb 4, 2011, at 17:37, john  wrote:

> Hi Matt,
> 
> Thanks for responding. I've posted the response below (as a python
> dict).
> 
> {'status': '401', 'content-length': '1', 'x-xss-protection': '1;
> mode=block', 'x-transaction': 'Sat Feb 05 01:33:54 +
> 2011-76395-3097', 'set-cookie': 'k=74.128.37.77.1296869634703204;
> path=/; expires=Sat, 12-Feb-11 01:33:54 GMT; domain=.twitter.com,
> guest_id=129686963484327539; path=/; expires=Mon, 07 Mar 2011 01:33:54
> GMT,
> _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCBwzdPMtAToHaWQiJWY1OTdhNDQ2Yjg1YzIw
> %250AYTVjMmEyNWUyMjM2ZTY1ZGY3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
> %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--01f06bea7e9f7559080f47e3b046117c40c39212;
> domain=.twitter.com; path=/', 'expires': 'Tue, 31 Mar 1981 05:00:00
> GMT', 'vary': 'Accept-Encoding', 'x-runtime': '0.00533', 'server':
> 'hi', 'x-revision': 'DEV', 'last-modified': 'Sat, 05 Feb 2011 01:33:54
> GMT', 'connection': 'close', 'pragma': 'no-cache', 'cache-control':
> 'no-cache, no-store, must-revalidate, pre-check=0, post-check=0',
> 'date': 'Sat, 05 Feb 2011 01:33:54 GMT', 'x-frame-options':
> 'SAMEORIGIN', 'content-type': 'text/html; charset=utf-8'}
> 
> From what I've read, Twitter's oauth responses lack the error handling
> that one would like. Any idea where I should go from here? I found the
> section of the library I'm using that creates the UTC timestamp, by
> calling time.time(). I would think that Django's timezone property
> would set the runtime timezone, however I have not checked that
> specifically. Any ideas?
> 
> Thanks,
> John
> 
> On Feb 4, 4:58 pm, Matt Harris  wrote:
>> Hi John,
>> 
>> What is the does the body of the error response say? The message will tell 
>> you which part of the oauth request failed.
>> 
>> Also be aware that oauth timestamps are in UTC seconds.  
>> 
>> Best,
>> @themattharris
>> 
>> On Feb 4, 2011, at 12:45, john  wrote:
>> 
>>> I have an application that contains a simple setup using the
>>> oauthtwitter library found here.
>> 
>>> http://code.google.com/p/oauth-python-twitter/
>> 
>>> #Example code
>>> twitter = app.extras.oauthtwitter.OAuthApi(CONSUMER_KEY,
>>> CONSUMER_SECRET)
>>> request_token = twitter.getRequestToken()
>>> oauth_verifier = request.GET.get('oauth_verifier')
>>> access_token = twitter.getAccessToken(request_token, oauth_verifier)
>> 
>>> I'm failing at getting the access token. I have a verifier and am
>>> passing that along, like the example in the oauth lib, however am
>>> continuing to get (all day now) 401s. My system time is set correctly,
>>> as this is in a Django project, and I'm setting it via TIME_ZONE =
>>> 'America/Kentucky/Louisville' in my settings.py. Can anyone help?
>> 
>>> Thanks,
>>> John
>> 
>>> --
>>> 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-dev] Re: 401: Unauthorized (Python)

[john]

Hi Matt,

Thanks for responding. I've posted the response below (as a python
dict).

{'status': '401', 'content-length': '1', 'x-xss-protection': '1;
mode=block', 'x-transaction': 'Sat Feb 05 01:33:54 +
2011-76395-3097', 'set-cookie': 'k=74.128.37.77.1296869634703204;
path=/; expires=Sat, 12-Feb-11 01:33:54 GMT; domain=.twitter.com,
guest_id=129686963484327539; path=/; expires=Mon, 07 Mar 2011 01:33:54
GMT,
_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCBwzdPMtAToHaWQiJWY1OTdhNDQ2Yjg1YzIw
%250AYTVjMmEyNWUyMjM2ZTY1ZGY3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--01f06bea7e9f7559080f47e3b046117c40c39212;
domain=.twitter.com; path=/', 'expires': 'Tue, 31 Mar 1981 05:00:00
GMT', 'vary': 'Accept-Encoding', 'x-runtime': '0.00533', 'server':
'hi', 'x-revision': 'DEV', 'last-modified': 'Sat, 05 Feb 2011 01:33:54
GMT', 'connection': 'close', 'pragma': 'no-cache', 'cache-control':
'no-cache, no-store, must-revalidate, pre-check=0, post-check=0',
'date': 'Sat, 05 Feb 2011 01:33:54 GMT', 'x-frame-options':
'SAMEORIGIN', 'content-type': 'text/html; charset=utf-8'}

>From what I've read, Twitter's oauth responses lack the error handling
that one would like. Any idea where I should go from here? I found the
section of the library I'm using that creates the UTC timestamp, by
calling time.time(). I would think that Django's timezone property
would set the runtime timezone, however I have not checked that
specifically. Any ideas?

Thanks,
John

On Feb 4, 4:58 pm, Matt Harris  wrote:
> Hi John,
>
> What is the does the body of the error response say? The message will tell 
> you which part of the oauth request failed.
>
> Also be aware that oauth timestamps are in UTC seconds.  
>
> Best,
> @themattharris
>
> On Feb 4, 2011, at 12:45, john  wrote:
>
> > I have an application that contains a simple setup using the
> > oauthtwitter library found here.
>
> >http://code.google.com/p/oauth-python-twitter/
>
> > #Example code
> > twitter = app.extras.oauthtwitter.OAuthApi(CONSUMER_KEY,
> > CONSUMER_SECRET)
> > request_token = twitter.getRequestToken()
> > oauth_verifier = request.GET.get('oauth_verifier')
> > access_token = twitter.getAccessToken(request_token, oauth_verifier)
>
> > I'm failing at getting the access token. I have a verifier and am
> > passing that along, like the example in the oauth lib, however am
> > continuing to get (all day now) 401s. My system time is set correctly,
> > as this is in a Django project, and I'm setting it via TIME_ZONE =
> > 'America/Kentucky/Louisville' in my settings.py. Can anyone help?
>
> > Thanks,
> > John
>
> > --
> > 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] 401: Unauthorized (Python)

[Matt Harris]

Hi John,

What is the does the body of the error response say? The message will tell you 
which part of the oauth request failed.

Also be aware that oauth timestamps are in UTC seconds.  

Best,
@themattharris

On Feb 4, 2011, at 12:45, john  wrote:

> I have an application that contains a simple setup using the
> oauthtwitter library found here.
> 
> http://code.google.com/p/oauth-python-twitter/
> 
> 
> #Example code
> twitter = app.extras.oauthtwitter.OAuthApi(CONSUMER_KEY,
> CONSUMER_SECRET)
> request_token = twitter.getRequestToken()
> oauth_verifier = request.GET.get('oauth_verifier')
> access_token = twitter.getAccessToken(request_token, oauth_verifier)
> 
> 
> I'm failing at getting the access token. I have a verifier and am
> passing that along, like the example in the oauth lib, however am
> continuing to get (all day now) 401s. My system time is set correctly,
> as this is in a Django project, and I'm setting it via TIME_ZONE =
> 'America/Kentucky/Louisville' in my settings.py. Can anyone help?
> 
> Thanks,
> John
> 
> -- 
> 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] 401: Unauthorized (Python)

[john]

I have an application that contains a simple setup using the
oauthtwitter library found here.

http://code.google.com/p/oauth-python-twitter/


#Example code
twitter = app.extras.oauthtwitter.OAuthApi(CONSUMER_KEY,
CONSUMER_SECRET)
request_token = twitter.getRequestToken()
oauth_verifier = request.GET.get('oauth_verifier')
access_token = twitter.getAccessToken(request_token, oauth_verifier)


I'm failing at getting the access token. I have a verifier and am
passing that along, like the example in the oauth lib, however am
continuing to get (all day now) 401s. My system time is set correctly,
as this is in a Django project, and I'm setting it via TIME_ZONE =
'America/Kentucky/Louisville' in my settings.py. Can anyone help?

Thanks,
John

-- 
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] Questions about friendship/create

[Taylor Singletary]

This is pretty easy to miss -- "notifications" in this context enables the
target user to be among those the "current user" receives SMS notifications
for (if they have that feature enabled) -- it's the equivalent of sending a
POST to notifications/follow for the user.

The default "follow" behavior on Twitter.com is just the simple POST to
friendships/create you're already doing.

As for include_entities in this context -- probably not necessary unless you
were going to display the "just followed" user's most recent status and
wanted to use entities to help you render it.

@episod  - Taylor Singletary - Twitter Developer
Advocate


On Thu, Feb 3, 2011 at 10:52 PM, pl  wrote:

> Can someone descripe what the 'follow' options is actually used for -
> it's described as 'Enable notifications for the target user' but I'm
> not sure what that actually means.
>
> If I don't include this param, then the friendship gets created, and
> seems to work as expected. What am I missing but not putting this in?
>
> I'm also not using the 'include_entities' param. That says that these
> will be made a default component of output in the future, so should I
> just add them in now so that nothing changes when this is made the
> default (I've no idea how long this 'in the future' message has been
> there as I've only just started looking at this - could this future
> they speak of still be a very long way off...)
>
> What would be the values to set this to in order to exactly mirror the
> actions taken by clicking on the 'follow' button within twitter.
> Should they both be missing, both set, or some other combination?
>
> Thanks in advance for any hints on 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
>

-- 
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] Twiiter API - I can post tweets but where are they?

[new2TwitterAPI]

I have a desktop application which I have now authorized and have
started posting tweets. I can see from the callback that the tweets
are sent correctly. However, when I log into tweeter I cannot see the
tweets anywhere.
Does each registered app have a seperate account? All I want is for
users of the desktop app to be able to send tweets to their clients.

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

[Tweetertopics]

I started a blog some time ago initially designed and intended to do
well on Twitter. I believe it would do well on twitter if all readers
had to do was push a button without logging in or deciding what they
want to say like a retweet button. Users use the Facebook's like
button my website and pretty much ignore the tweet button because the
like button is easy. They also ignore facebook's share button because
it isn't as easy as the like button.

-- 
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] Whitelist Requests from REST API

[Arthur]

Hello,

I have a question about number of requests,
if I signed up with twitter, let's say, to allow visualizing my data,
then the app will consume my requests.

how does it work if the app got whitelisted,
the app will not consume my requests?

Many thanks in advance,

-- 
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] High number of 502 errors in REST API

[Adam Green]

Good suggestion, Taylor. I was using a count of 200 to reduce the
number of calls, and stay under the rate limit. I just tried a count
of 100 and had fewer errors. I need to backfill test from 32 accounts
with a total of 20,000 tweets. I will rewrite this to use a lower
count, perhaps 50, and then spread the testing out over the whole day,
instead of doing it in one run every 24 hours. Thanks.

On Thu, Feb 3, 2011 at 11:51 PM, Taylor Singletary
 wrote:
> What kind of count values are you using? When we're at capacity,
> higher count values' processing time can exceed our timeout filters. I
> would recommend lowering count values as a response to this error and
> retrying.
>
> Taylor
>
> On Thursday, February 3, 2011, Jan Paricka  wrote:
>> Adam, I noticed the same - 502 502 502 502 a lot lately!
>> Jan
>>
>> On Fri, Feb 4, 2011 at 5:14 AM, Adam Green <140...@gmail.com> wrote:
>> I'm using 1/statuses/user_timeline to verify that I am receiving all
>> the tweets for a set of users I am following with the streaming API.
>> Once per day I try to collect all the tweets for these users using
>> this API call. The total process takes about 100 calls to the API. For
>> the last week I have been receiving a very high level of 502 error
>> responses, about 1 for every 2 to 3 calls. Is this just due to very
>> high traffic related to Egypt, or is something else going on?
>>
>> --
>> 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
>>
>
> --
> @episod  - Taylor Singletary - Twitter Developer
> Advocate
>
> --
> 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
>



-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

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