Re: [twitter-dev] Question about rate limiting

[Tom van der Woerdt]

Per user per application. With 1000 users you can use 35 API calls 
per hour.


Tom


On 5/24/11 5:41 AM, Sam Oldak wrote:
I am developing an app that allows users to "login" with twitter.  I'm 
a bit confused about the rate limiting applied to verifying 
credentials of users.  Is it 350/hour for the application, or per user 
that uses the application?  For example, could 1000 people signin 
within an hour, or am I limited to 350 per hour? --

Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: 
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk 



--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Question about rate limiting

[Sam Oldak]

I am developing an app that allows users to "login" with twitter.  I'm a bit 
confused about the rate limiting applied to verifying credentials of users. 
 Is it 350/hour for the application, or per user that uses the application? 
 For example, could 1000 people signin within an hour, or am I limited to 
350 per hour?

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] question on authentication...

[jimmy6]

1) oath2 supported in twitter?

2) Why there is no proper document mention what parameter use in
following authenticated method?
http://dev.twitter.com/pages/sign_in_with_twitter

3) How to get access token in @anywhere?

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] question regarding twitter search api query parameters

[carrier24sg]

Hi people,

I want to use the twitter search api to search for some famous person.
For instance I want to search for a particular "Mr Patrick Lee C K". I
would construct my search term to be something like:

http://search.twitter.com/search?q=%22lee+c+k%22+OR+%22patrick+lee%22

However, knowing that tweets are often informal, I know that sometimes
people can address him by his initials 'lck'. To increase the
precision of my search, I figure it would be better if my query can
associate with his company, for instance my query could also be lck
microsoft.

Now, i want to string these 3 search terms "patrick lee"/"lee c k"/lck
microsoft together in one query. I probably will use OR. Then again,
my last search term should not be a fixed phrase i.e word lck and
microsoft can be some distance from each other.

Can anyone tell me how should i link these search terms together
inside one query?

-- 
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] Question about storing username & password like tweetdeck

[Scott Wilcox]

You can think what you like, but I can guarantee you that Tweetdeck uses XAuth 
to obtain OAuth tokens to use for your account instead of pushing you through 
the OAuth/OOB dance.

On 28 Mar 2011, at 14:54, jimmy6 wrote:

> I dont think so. Tweetdeck need to store our twiter's username and
> password. Look like it direct access our account. Right?
> 
> On Mar 27, 11:08 pm, Scott Wilcox  wrote:
>> Tweetdeck uses XAuth to obtain tokens for OAuth use.
>> 
>> On 27 Mar 2011, at 15:56, Jimmy Au wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> I am wondering what api is using by tweetdeck which is not using oauth
>>> authentication. It direct using username and password for it's app.
> 
> -- 
> 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] Question about storing username & password like tweetdeck

[Jimmy Au]

I am wondering what api is using by tweetdeck which is not using oauth
authentication. It direct using username and password for it's app.

-- 
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] Question about storing username & password like tweetdeck

[Scott Wilcox]

Tweetdeck uses XAuth to obtain tokens for OAuth use.

On 27 Mar 2011, at 15:56, Jimmy Au wrote:

> I am wondering what api is using by tweetdeck which is not using oauth
> authentication. It direct using username and password for it's app.

-- 
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] Question on Trend Searching

[JasonTheGreatM]

Hi all-

Is there anyway to do a search for a category value like "basketball"
and get the top Twitter trend topics?  For example, if I enter
"basketball" I would get top trend topics like "NCAA", "March
Madness", "NBA" etc.  Then I would want to be able to enter one of
those result topics as input and see all the resulting tweets for that
trending topic (I believe that is what the current Twitter search API
handles).  Hope that makes sense.

Thanks for any help you can provide.

-- 
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] Question about REST API design (not strictly Twitter related)

[craigpierce]

Hello All -

I'll try to keep this brief - I'm sure the answer is simple but I just
don't get it...

I'm looking to build a simple API similar to Twitter's (I don't care
whether it's actually considered RESTful or not - I'm just calling it
that), but there is one thing that NO ONE explains: how the *actual*
folder structure works...

Example:

http://www.url.com/api/user/123/

Let's say that's my URL to get user info for user ID '123'; does there
need to be a folder called 'api' with a folder called 'user' with a
folder for each and every user ID, each with its own index.php file in
it that returns that user's data? Surely not (especially when you're
Twitter with 100 million users and billions of tweets to deal with),
but how else could this work?

Thanks so much - sorry for the OT thread...

-- 
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] Question regarding ip based rate limiting

[Gautam Mr]

Hi,

I have a question regarding ip based rate limiting. As per documentation all
those api that does not require authentication falls under ip based limit
which is 150.

Is there a way to find what is the remaining number of hits available while
making an api call (that does not require authentication)? Also is there a
way to find out what is the next reset time.
There are option available to find these limits while doing home timeline
query or user timeline queries (apis that needs authentication). But could
not find anything while doing a lookup on a status using
http://dev.twitter.com/doc/get/statuses/show/:id.

Would appreciate your help.

Thanks
Gautam

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

[Shiva]

How to judge, the tweet message is retweetable or not using twitter4j
API.

Shiva
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] Question about Search

[Taylor Singletary]

There are several factors involved in surfacing in search results, chief
among them that the search index represents only around a week's worth of
Tweets. Additionally, the search index is filtered for quality and some
tweets and/or accounts will not be represented:
http://support.twitter.com/articles/66018-my-tweets-or-hashtags-are-missing-from-search

Here's a summary of reasons a user might not appear in search:

>
>1. *Your tweets aren't recent: *We only index tweets for about 6 days.
>If your most recent tweet is older than that, please tweet again and check.
>2. *Your account is private:* Private or "protected" accounts do not
>appear in search.Learn more about protected accounts 
> here
>.
>3. *Your account is new, or you recently changed your username: *It can
>take a few days for new and updated accounts to be indexed by search.
>4. *Your email is bouncing:* If you log in and see a big red warning
>when you're attwitter.com that says your email address is having
>delivery issues, please take the steps to fix it! We want to show you in
>search, but we need you to fix your email first (see Screenshot 2 below).
>5. *You are being filtered out of search due to a quality issue*: In
>order to provide the best search experience for users, Twitter 
> automatically
>filters search results for quality. This Search Quality help 
> page has
>information why accounts are filtered from search
>6. *You are missing because of current resource constraints: *Right
>now, some users may not be seeing their Tweets because of resource
>constraints. This is more likely affecting you if you're a new user (with 
> an
>account less than a couple of weeks old). Our search engineers are working
>on this known issue, and your Tweets should start showing up in search 
> soon!
>
> Taylor

On Sat, Jan 29, 2011 at 7:17 PM, jparicka  wrote:

> Why is it not returning all search results?  E.e. when I search for
> @fu2ri I can clearly see few tweets missing. No matter what token/
> credentials I use.  Are Search results also not guaranteed to appear?
> Is there a time-lock of some sort on Search? 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
>

-- 
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] Question about Search

[jparicka]

Why is it not returning all search results?  E.e. when I search for
@fu2ri I can clearly see few tweets missing. No matter what token/
credentials I use.  Are Search results also not guaranteed to appear?
Is there a time-lock of some sort on Search? 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

[twitter-dev] question

[mahesh]

how can I get the tweets of my logged in website users without
prompting everytime for usename and password

-- 
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] question about verify_credentials and rate limits

[Stephen Rife]

Hi

Through testing a call to verify_credentials when it returns true
seems to count against the oAuthed user's rate limit.

However if verify_credentials returns false it does not seem to count
against the IP's rate limit.

I just want to make sure this is correct and the verify_credentials
returning FALSE condition doesn't count against some other rate limit
in that case what it would be.

Thanks,
Steve
@melobubu

-- 
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] Question on Lists

[Abraham Williams]

If you are trying to pull in the statuses from a list then you would do:

$xml = $connection->get('twitter/lists/team/statuses');

Were twitter is the account who created the list and team is the ID or slug
of the list.

Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham  | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Thu, Jan 6, 2011 at 07:36, Jon  wrote:

> Hello,
>
> I have a script in which I am pulling my friends timeline from Twitter
> and putting it on my web site. I do so with the following:
>
>  $xml = $connection->get('statuses/friends_timeline');
>
> My question is, how do I grab a friends timeline based on a list?
>
> Help is greatly appreciated!
>
> Thanks,
>
> 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
>

-- 
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] Question on Lists

[Jon]

Hello,

I have a script in which I am pulling my friends timeline from Twitter
and putting it on my web site. I do so with the following:

  $xml = $connection->get('statuses/friends_timeline');

My question is, how do I grab a friends timeline based on a list?

Help is greatly appreciated!

Thanks,

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

Re: [twitter-dev] question regarding parameters for iframe version of Twitter button

[Matt Harris]

Hey,

When supplying Tweet Button arguments to the iframe version you should add
them as querystring arguments of the iframe URL.
In the iframe example below the count will be the vertical style, and the
shared URL will be http://dev.twitter.com/pages/tweet_button

http://platform.twitter.com/widgets/tweet_button.html?url=http%3A%2F%2Fdev.twitter.com%2Fpages%2Ftweet_button&count=vertical
"
style="width:60px; height:65px;">

Hope that helps,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris


On Sun, Jan 2, 2011 at 4:52 PM, SD admin  wrote:

> Hello all,
>
> I had a question that is probably very simple, but for some reason I'm
> missing something.
>
> I was trying to implement Twitter and Facebook buttons on my site
> presented on the same line. I have seen other do this, some using ul
> list overflows and other tricks, but I didn't like them. The issue was
> that the Facebook button uses an iframe, and the standard Twitter
> button did not. Putting them in a table did little to solve the issue.
>
> Anyway, I saw that the Twitter button is available in an iframe
> version as well, I've used it and it works great. There are a few
> issues however.
>
> On the Tweet button dev page [http://dev.twitter.com/pages/
> tweet_button], it shows that you can use an iframe, but says "When
> using this method you have to use query string parameters to customise
> the Tweet Button’s behavior."
>
> The iframe code presented is:
>
> src="http://platform.twitter.com/widgets/tweet_button.html";
>style="width:130px; height:50px;">
>
> And these are the parameters:
>
> url URL of the page to share
> via Screen name of the user to attribute the Tweet to
> textDefault Tweet text
> related Related accounts
> count   Count box position
> langThe language for the Tweet Button
> counturlThe URL to which your shared URL resolves to
>
> Typically one would just put the parameters after http://twitter.com/share
> ,
> but I am unsure where to do this with the iframe version???
>
> Can someone point me in the right direction please?
>
> 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
>

-- 
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] question regarding parameters for iframe version of Twitter button

[SD admin]

Hello all,

I had a question that is probably very simple, but for some reason I'm
missing something.

I was trying to implement Twitter and Facebook buttons on my site
presented on the same line. I have seen other do this, some using ul
list overflows and other tricks, but I didn't like them. The issue was
that the Facebook button uses an iframe, and the standard Twitter
button did not. Putting them in a table did little to solve the issue.

Anyway, I saw that the Twitter button is available in an iframe
version as well, I've used it and it works great. There are a few
issues however.

On the Tweet button dev page [http://dev.twitter.com/pages/
tweet_button], it shows that you can use an iframe, but says "When
using this method you have to use query string parameters to customise
the Tweet Button’s behavior."

The iframe code presented is:

http://platform.twitter.com/widgets/tweet_button.html";
style="width:130px; height:50px;">

And these are the parameters:

url URL of the page to share
via Screen name of the user to attribute the Tweet to
textDefault Tweet text
related Related accounts
count   Count box position
langThe language for the Tweet Button
counturlThe URL to which your shared URL resolves to

Typically one would just put the parameters after http://twitter.com/share,
but I am unsure where to do this with the iframe version???

Can someone point me in the right direction please?

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

Re: [twitter-dev] Question about TT's

[Emerson Damasceno]

Hello there. Obviously this is not the proper place, but since it's being a
lot of talking in Brazil, have you heard anything about Twitter monitoring
the TT's for political reasons?
In Brazil some are saying the Hashtag #dilma13 was somehow "pulled off" the
TT's (it's a brazilian Candidate to Presidential Pools).
Also as a Journalist I wonder if that is somehow possible (since Twitter is
able to accept a promoted TT) but as far as I know, not Stop a Trending (if
really trending).
Anyway, thank you all again

Emerson

2010/10/12 D. Smith 

> I noticed that the value of source field looks somewhat strange:
> "source":"http://www.echofon.com/\"; rel=\"nofollow\">Echofon<
> \/a>",
>
> Why in the world would you have an html string as a value and on top
> of than why do you include the rel="nofollow" tag?
>
> This just looks wrong, not structured.
> The right way whould have been to represent the source as an object
> with fileds: name, url, like this:
>
> "source":{"name" : "Echofon", "url":"http://www.echofon.com"},
>
> Usually you try to pre-parse everying for us, but in the case or
> source, we have to do extra parsing to extract values of title and url
>
> Will you fix this soon?
>
> --
> 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
>



-- 
*Emerson Damasceno
http://www.twitter.com/emersonanomia
http://www.blog.opovo.com.br/bloganomia/*
*http://www.opovo.com.br/colunas/tecnologia/listagemmidiaesocial/*
*Tel: +55 85-8697 3224/ 85-3458 1977/ 11- 7356 9693*
*Nextel: 55*86*28199*
*Damasceno & Associados*
*Shopping Aldeota 1620/1621*

-- 
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] Question about source field

[D. Smith]

I noticed that the value of source field looks somewhat strange:
"source":"http://www.echofon.com/\"; rel=\"nofollow\">Echofon<
\/a>",

Why in the world would you have an html string as a value and on top
of than why do you include the rel="nofollow" tag?

This just looks wrong, not structured.
The right way whould have been to represent the source as an object
with fileds: name, url, like this:

"source":{"name" : "Echofon", "url":"http://www.echofon.com"},

Usually you try to pre-parse everying for us, but in the case or
source, we have to do extra parsing to extract values of title and url

Will you fix this soon?

-- 
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] Question about truncated entities in the streaming API

[Justin]

Are entities not delivered if the tweet is truncated? Can they be in
the future?

I've noticed that when retweets are delivered they have "RT
@whateverusername: " prepended, this often shoves a url or hash tag
off the end of a message and I don't seem to receive the entity
either, even though it was in the original message. Am I missing
something? Is the original message available or could it be added as
original_text? Thanks for any insight!

-- 
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] Question about Authentication/Whitelisting and friends/ids

[Ramanathan Narayanan]

Hello,

   I have a whitelisted account. I was under the assumption that I can
use either a assigned IP address or authentication in order to make use of
the 20,000 API calls per hour. Earlier I used to authenticate using basic
authentication and issue a API call from a machine different from my
whitelisted IP, and I was able to make that count against my whitelisted
account.

   When I switched to oauth, I have a problem with the friends/ids call.

   Specifically , when I issue a API call to friends/ids using oauth, I
specify the user_id parameter. Now my problem is that this API call returns
the friends/ids list for my oauth authenticated user id, and not for the
user_id for which I want the friends/ids. Is there a simple solution to this
problem.

  -Ram



-- 
Ramanathan Narayanan
Dept. of EECS
Northwestern University
Evanston IL

-- 
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] Question about User Vs Site Streams, and Moving away from REST calls.

[John Kalucki]

I'm sorry, I laid out the difference between User Streams and Site Streams,
but I forgot to bring it all back to the specific question at hand.

The critical difference isn't Desktop vs. Web Site-- that's the general
case description. The key difference is that you must multiplex if you open
more than a handful of connections. In this specific case, there's nothing
to multiplex, so remaining on User Streams is OK, despite coming from a
server. The usage is really as if a single user was monitoring an account.

To answer Tom's question, currently a User Stream connection and a Site
Stream connection with a single user have the same cost.

Sorry for the incomplete answer. Does this make sense?

-John


On Wed, Sep 15, 2010 at 10:58 PM, Tom van der Woerdt  wrote:

> Hi John,
>
> This seems like a rather strange policy. Is the cost of having one User
> Streams connection not far lower than having a connection to Site
> Streams? That's what Justin asked, just one connection.
>
> Tom
>
>
> On 9/16/10 6:22 AM, John Kalucki wrote:
> > Our intention is that User Streams and Site Streams will, shortly, offer
> > the same data and filtering options at a similar, if not identical, QoS.
> > I'm sure some subtleties will creep in over time, as they always do, but
> > this parity is our goal.
> >
> > The major difference is that User Streams, given its higher per-user
> > cost, is limited only to user-based applications that connect directly
> > to the Twitter API. In this use case, we have no alternative but to
> > service a connection from each user device. Site Streams, on the other
> > hand, allows services, such as your website, to open many User Streams
> > multiplexed over a smaller number of connections. This reduces per-user
> > cost, and makes large scale integrations tractable. Several pretty large
> > services have integrated with Site Streams in just a few days, so this
> > multiplexing is unlikely to be an undue additional burden over a User
> > Streams integration, and might even save a lot of work over time.
> >
> > If you attempt to use User Streams from a service, we can trivially
> > detect this situation, and we'll classify your usage as against the TOS.
> > To put our current thinking as bluntly as possible: we intend to enforce
> > the distinction between User Streams and Site Streams via revocation of
> > access.
> >
> > -John Kalucki
> > http://twitter.com/jkalucki
> > Twitter, Inc.
> >
> >
> >
> > On Wed, Sep 15, 2010 at 12:24 PM, Justin  > > wrote:
> >
> > I've successfully migrated one of my sites away from making search
> and
> > mention rest calls, switched over to the streaming API and I'm loving
> > it. I still need to move it to OAuth but now that I have that in test
> > I'm reading up on the User and Site streams and I have a question.
> >
> > It seems the User stream states that websites should not use it, and
> > should use the Site stream instead, but I don't consume or care about
> > my user's activity, my site is centered around the messages and
> > interactions with the application user not the users themselves.
> >
> > Right now I track and evaluate followers and other bits using the
> rest
> > calls but from what I see I could eliminate those rest calls and be
> > off them (possibly) all together if I could use the User stream to
> > accept information about new and broken friendships, favorites, dms,
> > etc.
> >
> > Is it acceptable to use the User stream in that manor since I would
> > only need it for the app user account not my site user's accounts? If
> > so, I can just maintain the two streams (filtered streaming api and
> > user stream) and eliminate or cut back my rest calls dramatically?
> > Please let me know so I can plan accordingly.
> >
> > --
> > 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 Twit

Re: [twitter-dev] Question about User Vs Site Streams, and Moving away from REST calls.

[Tom van der Woerdt]

Hi John,

This seems like a rather strange policy. Is the cost of having one User
Streams connection not far lower than having a connection to Site
Streams? That's what Justin asked, just one connection.

Tom


On 9/16/10 6:22 AM, John Kalucki wrote:
> Our intention is that User Streams and Site Streams will, shortly, offer
> the same data and filtering options at a similar, if not identical, QoS.
> I'm sure some subtleties will creep in over time, as they always do, but
> this parity is our goal.
> 
> The major difference is that User Streams, given its higher per-user
> cost, is limited only to user-based applications that connect directly
> to the Twitter API. In this use case, we have no alternative but to
> service a connection from each user device. Site Streams, on the other
> hand, allows services, such as your website, to open many User Streams
> multiplexed over a smaller number of connections. This reduces per-user
> cost, and makes large scale integrations tractable. Several pretty large
> services have integrated with Site Streams in just a few days, so this
> multiplexing is unlikely to be an undue additional burden over a User
> Streams integration, and might even save a lot of work over time.
> 
> If you attempt to use User Streams from a service, we can trivially
> detect this situation, and we'll classify your usage as against the TOS.
> To put our current thinking as bluntly as possible: we intend to enforce
> the distinction between User Streams and Site Streams via revocation of
> access.
> 
> -John Kalucki
> http://twitter.com/jkalucki
> Twitter, Inc.
> 
> 
> 
> On Wed, Sep 15, 2010 at 12:24 PM, Justin  > wrote:
> 
> I've successfully migrated one of my sites away from making search and
> mention rest calls, switched over to the streaming API and I'm loving
> it. I still need to move it to OAuth but now that I have that in test
> I'm reading up on the User and Site streams and I have a question.
> 
> It seems the User stream states that websites should not use it, and
> should use the Site stream instead, but I don't consume or care about
> my user's activity, my site is centered around the messages and
> interactions with the application user not the users themselves.
> 
> Right now I track and evaluate followers and other bits using the rest
> calls but from what I see I could eliminate those rest calls and be
> off them (possibly) all together if I could use the User stream to
> accept information about new and broken friendships, favorites, dms,
> etc.
> 
> Is it acceptable to use the User stream in that manor since I would
> only need it for the app user account not my site user's accounts? If
> so, I can just maintain the two streams (filtered streaming api and
> user stream) and eliminate or cut back my rest calls dramatically?
> Please let me know so I can plan accordingly.
> 
> --
> 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] Question about User Vs Site Streams, and Moving away from REST calls.

[John Kalucki]

Our intention is that User Streams and Site Streams will, shortly, offer the
same data and filtering options at a similar, if not identical, QoS. I'm
sure some subtleties will creep in over time, as they always do, but this
parity is our goal.

The major difference is that User Streams, given its higher per-user cost,
is limited only to user-based applications that connect directly to the
Twitter API. In this use case, we have no alternative but to service a
connection from each user device. Site Streams, on the other hand, allows
services, such as your website, to open many User Streams multiplexed over a
smaller number of connections. This reduces per-user cost, and makes large
scale integrations tractable. Several pretty large services have integrated
with Site Streams in just a few days, so this multiplexing is unlikely to be
an undue additional burden over a User Streams integration, and might even
save a lot of work over time.

If you attempt to use User Streams from a service, we can trivially detect
this situation, and we'll classify your usage as against the TOS. To put our
current thinking as bluntly as possible: we intend to enforce the
distinction between User Streams and Site Streams via revocation of access.

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



On Wed, Sep 15, 2010 at 12:24 PM, Justin  wrote:

> I've successfully migrated one of my sites away from making search and
> mention rest calls, switched over to the streaming API and I'm loving
> it. I still need to move it to OAuth but now that I have that in test
> I'm reading up on the User and Site streams and I have a question.
>
> It seems the User stream states that websites should not use it, and
> should use the Site stream instead, but I don't consume or care about
> my user's activity, my site is centered around the messages and
> interactions with the application user not the users themselves.
>
> Right now I track and evaluate followers and other bits using the rest
> calls but from what I see I could eliminate those rest calls and be
> off them (possibly) all together if I could use the User stream to
> accept information about new and broken friendships, favorites, dms,
> etc.
>
> Is it acceptable to use the User stream in that manor since I would
> only need it for the app user account not my site user's accounts? If
> so, I can just maintain the two streams (filtered streaming api and
> user stream) and eliminate or cut back my rest calls dramatically?
> Please let me know so I can plan accordingly.
>
> --
> 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] Question about User Vs Site Streams, and Moving away from REST calls.

[Justin]

I've successfully migrated one of my sites away from making search and
mention rest calls, switched over to the streaming API and I'm loving
it. I still need to move it to OAuth but now that I have that in test
I'm reading up on the User and Site streams and I have a question.

It seems the User stream states that websites should not use it, and
should use the Site stream instead, but I don't consume or care about
my user's activity, my site is centered around the messages and
interactions with the application user not the users themselves.

Right now I track and evaluate followers and other bits using the rest
calls but from what I see I could eliminate those rest calls and be
off them (possibly) all together if I could use the User stream to
accept information about new and broken friendships, favorites, dms,
etc.

Is it acceptable to use the User stream in that manor since I would
only need it for the app user account not my site user's accounts? If
so, I can just maintain the two streams (filtered streaming api and
user stream) and eliminate or cut back my rest calls dramatically?
Please let me know so I can plan accordingly.

-- 
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] Question about transitioning from basic auth to oAuth

[Yardmaps]

Hi there,
My website, Yardmaps.org, has its own twitter account - actually
there's a twitter account for each city that yardmaps will be
available in.

When I was coding the site using basic auth, I had a simple function
that would update the twitter status of a given city whenever a yard
sale is posted.  Since I own the website, and the twitter accounts, I
don't need to ask a 3rd person for permission to update their status.
Basic auth was perfect.

However, now that basic auth is no more, I'm not sure how I'm supposed
to use oAuth to do the same thing?

My database has the username and password for each twitter account,
and when a yard sale is added, i simply want to tweet it out.  Since
oAuth doesn't (in my limited understanding) support asynchronous
calls, I don't know how I can upgrade?

Please help me.

Thanks
B

-- 
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] Question question of cursor-enabled GET's and API limits ...

[johnc]

Hi Twitter devs,

So does each chunk of a cursor-enabled GET you make count as an API
call from your account?  And if yes (I'd imagine so), and you may well
need to make more successive API calls in an hour than are allotted,
does the cursor offset allow you to start where you left off once your
API limit rolls over again?

Thanks!
/John

[twitter-dev] Question on handling oAuth Echo using twitteroauth lib

[YCBM]

Hi All,

Looking to use Abraham's twitteroauth lib on our site which is already
converted to oAuth for web-based login.

We have an open API that other apps (consumers -- if i understand that
correctly) will be posting to using oAuth Echo.

Are there any sample PHP code that I can take a look at in which the
PHP script receives the post from the consumer and takes the header
stuff to verify the user on Twitter?  Specifically in the oAuth Echo
flow?

I created a PHP script to simulate the consumer post to me which
includes the oauth_consumer_key, oauth_signature_method, oauth_token,
oauth_timestamp, oauth_nonce, oauth_version, oauth_signature, X-Auth-
Service-Provider, X-Verify-Credentials-Authorization and the signing
URL.

Once I post these to my PHP script, not quite sure what to do to
verify the user.  Perhaps I can use the twitteroauth and just fill in
some blanks?  Sample code will be extremely helpful.

Thanks in advance.
Y

Re: [twitter-dev] question about rate limiting and parsing user xml

[Raffi Krikorian]

yes. if you're not authenticated, then the rate limit is deducted from the
IP address.

On Mon, Apr 19, 2010 at 6:15 PM, Lil Peck  wrote:

> For those of us who have web page scripts that parse our sites'
> twitter accounts rss feeds to display as html: does the rate limit
> apply to that usage also?
>
>
> --
> Subscription settings:
> http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
>



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

[twitter-dev] question about rate limiting and parsing user xml

[Lil Peck]

For those of us who have web page scripts that parse our sites'
twitter accounts rss feeds to display as html: does the rate limit
apply to that usage also?


-- 
Subscription settings: 
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en

[twitter-dev] question about search rate limiting

[thoughtafter]

According to the docs the Search API has a higher limit than 150
requests per hour:

"Note that the Search API is not limited by the same 150 requests per
hour limit as the REST API."
http://apiwiki.twitter.com/Rate-limiting

However, I seem to be getting the following message when using the
search API:
"Rate limit exceeded. Clients may not make more than 150 requests per
hour."

An example request is:
/1/search.json?since=2010-03-27&q=from%3ATVWnews%20OR%20%40TVWnews%20OR
%20%23TVWnews

I'm using the Ruby Twitter GEM version 0.9.1.

What am I missing?

Thanks,
Jesse

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Question about xAuth.

[IoriAYANE]

I have trouble for xAuth.

I applied by sending an email to a...@twitter.com.
And I received the email of the following contents.

 received mail --
Thanks for your interest in XAuth. Your application now has the
ability to use XAuth, and you can read the documentation here:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-oauth-access_token-for-xAuth
.
 received mail --

I'm testing xAuth on my application.
However, I cannot certify it.
My application received HTTP 401 error.

I had the developer of my friend who test xAuth in the following
applications.
In that case, it was OK.
However, I fail with my key.

Test application Link
http://relog.xii.jp/download/test/xAuthTest.LZH

Please help me.

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] question regarding promoted apps

[Abraham Williams]

Last I heard the applications are selected by Twitter employees as being
awesome. So make your application awesome and maybe you will see yours
showing up too.

Abraham

On Thu, Feb 11, 2010 at 16:04, wael orabi  wrote:

> Dear twitter dev.
> anyone knows how to add an app to this little gray box on twitter main
> page? is it paid or random?
> any info would be appreciated.
> another thing I would love to hear some feedback on an app I developed, it
> is still in beta but any feedback would be great here is the URL
> http://mutweeps.com
> thanks
> --w43L
>



-- 
Abraham Williams | Community Advocate | http://abrah.am
Project | Out Loud | http://outloud.labs.poseurtech.com
This email is: [ ] shareable [x] ask first [ ] private.

[twitter-dev] question regarding promoted apps

[wael orabi]

Dear twitter dev.
anyone knows how to add an app to this little gray box on twitter main page?
is it paid or random?
any info would be appreciated.
another thing I would love to hear some feedback on an app I developed, it
is still in beta but any feedback would be great here is the URL
http://mutweeps.com
thanks
--w43L

Re: [twitter-dev] question regarding API FAQ: reclaim inactive username

[Anil Chawla]

Thanks, glad to know I'm not alone on this. I've looked at filing a
trademark but it is still frustrating to proceed through
lengthy/costly legal process in order to reclaim an inactive/spam
username -- especially for a completely free service. This entry in
the Twitter API FAQ is a glimmer of hope for app developers. I hope
someone at Twitter can help app developers get their specific
situation reviewed. In some cases, such as mine, it is an
all-around-win for the Twitter ecosystem to release these inactive
usernames.

-Anil

On Wed, Feb 10, 2010 at 5:17 PM, Aral Balkan  wrote:
> I had the same response :(
> Someone told me that the way to approach it may be to file a trademark
> dispute. This is what I'm going to be forced to do since it doesn't appear
> possible to talk to a human being at Twitter about this issue.
> All the best,
> Aral
> On Wed, Feb 10, 2010 at 6:04 PM, anilchawla  wrote:
>>
>> I develop and maintain a free Twitter application (http://
>> tweetymail.com) and I am desperately trying to reclaim the inactive
>> 'tweetymail' username because it is causing confusion among my users.
>> I was not able to get anywhere with Twitter support, but I came across
>> this entry in the API FAQ:
>>
>>
>> http://apiwiki.twitter.com/FAQ#HowcanIreclaimaninactiveTwitteraccountformyprojectorapplication
>>
>> I followed the instructions and emailed usern...@twitter.com. Five
>> minutes later, I received two simultaneous emails: 1) An automatic
>> notice indicating that support received my request, 2) An automatic
>> rejection indicating that Twitter is not releasing inactive usernames
>> at this time.
>>
>> Have any other app developers had success with this process? Is the
>> information on the FAQ still valid? Can someone from Twitter provide
>> an alternate avenue for app developers to have a request such as this
>> heard?
>>
>> The account I am seeking (http://twitter.com/tweetymail) has never
>> tweeted and has been inactive for at least 6 months.
>>
>> Thank  you.
>
>

Re: [twitter-dev] question regarding API FAQ: reclaim inactive username

[Aral Balkan]

I had the same response :(

Someone told me that the way to approach it may be to file a trademark
dispute. This is what I'm going to be forced to do since it doesn't appear
possible to talk to a human being at Twitter about this issue.

All the best,
Aral

On Wed, Feb 10, 2010 at 6:04 PM, anilchawla  wrote:

> I develop and maintain a free Twitter application (http://
> tweetymail.com) and I am desperately trying to reclaim the inactive
> 'tweetymail' username because it is causing confusion among my users.
> I was not able to get anywhere with Twitter support, but I came across
> this entry in the API FAQ:
>
>
> http://apiwiki.twitter.com/FAQ#HowcanIreclaimaninactiveTwitteraccountformyprojectorapplication
>
> I followed the instructions and emailed usern...@twitter.com. Five
> minutes later, I received two simultaneous emails: 1) An automatic
> notice indicating that support received my request, 2) An automatic
> rejection indicating that Twitter is not releasing inactive usernames
> at this time.
>
> Have any other app developers had success with this process? Is the
> information on the FAQ still valid? Can someone from Twitter provide
> an alternate avenue for app developers to have a request such as this
> heard?
>
> The account I am seeking (http://twitter.com/tweetymail) has never
> tweeted and has been inactive for at least 6 months.
>
> Thank  you.
>

[twitter-dev] question regarding API FAQ: reclaim inactive username

[anilchawla]

I develop and maintain a free Twitter application (http://
tweetymail.com) and I am desperately trying to reclaim the inactive
'tweetymail' username because it is causing confusion among my users.
I was not able to get anywhere with Twitter support, but I came across
this entry in the API FAQ:

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

I followed the instructions and emailed usern...@twitter.com. Five
minutes later, I received two simultaneous emails: 1) An automatic
notice indicating that support received my request, 2) An automatic
rejection indicating that Twitter is not releasing inactive usernames
at this time.

Have any other app developers had success with this process? Is the
information on the FAQ still valid? Can someone from Twitter provide
an alternate avenue for app developers to have a request such as this
heard?

The account I am seeking (http://twitter.com/tweetymail) has never
tweeted and has been inactive for at least 6 months.

Thank  you.

Re: [twitter-dev] Question about licensing

[Jesse Stay]

I think the OWF agreement is an excellent idea - I'd love to see Twitter
join in that agreement with its developers.  If Twitter has concerns with it
I'd love to see them get involved in the OWF discussions and perhaps the
agreement could be modified to meet Twitter's needs.  Why reinvent the
wheel?

Jesse

On Sat, Jan 23, 2010 at 6:28 PM, DeWitt Clinton  wrote:

> Thanks for the update, Ryan.  And thanks for the compliment on the Google
> Code policies page -- that page was one of the first things I launched at
> Google back when we were being asked the exact same questions.
>
> We also added patent licences, which follow this general format:
>
>   http://code.google.com/apis/gdata/patent-license.html
>
> Granted, that license is maybe even more liberal than most implementors
> require.   Also, that was before we had a reusable patent agreement, such as
> the OWFa: http://openwebfoundation.org/legal/agreement/.  If I did
> something new outside Google I'd probably go the OWF route now.
>
> Trademark is trickier.  I'm not sure we've quite nailed it yet at Google,
> actually.  But the basic framework might be a statement that enumerates
> specific marks and lists specific appropriate usages.  You can always add to
> that list over time, and this would protect Twitter's rights in the cases
> you haven't anticipated yet.
>
> Thanks again for pushing this forward.  Cheers,
>
> -DeWitt
>
>
> On Sat, Jan 23, 2010 at 11:28 AM, Ryan Sarver  wrote:
>
>> DeWitt,
>>
>> Thanks for the serious patience on this thread. We're constantly trying to
>> adapt to the needs of the developer community, and you're right that we
>> haven't published guidelines around use of the Twitter API specifications.
>> But, we are working on it and I wanted to share some of the thought that
>> will help drive the policy.
>>
>> What we do know is that there is a clear need for a flexible, friendly and
>> responsible policy. Policies such as this one (
>> http://code.google.com/policies.html#restrictions) are a good start, and
>> I can share some principles we'd like to live by. CC-BY should apply to a
>> lot of the tools we release. You should be able to copy, modify and make
>> derivatives of our specifications (with attribution). We shouldn't throw
>> arbitrary roadblocks in your way, such as preventing you from naming a
>> library "tweet." And last, we shouldn't pester you for utilizing our patents
>> underlying these specifications.
>>
>> These are flexible and friendly principles, and in exchange we ask the
>> development community to act responsibly. For example, naming a library
>> "twitter" is one thing. Naming your application "twitter" is quite another.
>>
>> We hear you loud and clear, so please bear with us as we translate these
>> principles into official policy.
>>
>> Thanks again for your patience and interest :)
>>
>> Best, Ryan
>>
>> On Tue, Nov 24, 2009 at 9:12 AM, DeWitt Clinton wrote:
>>
>>> Hi all,
>>>
>>> I recently received a request to implement the "retweet" api calls in the
>>> python-twitter and java-twitter libraries, but before I proceed I was hoping
>>> for a bit of clarification around the licensing terms for the Twitter API.
>>>
>>> My layman's understanding is that without explicit terms there are
>>> relatively few rights offered by default regarding a specification.  In
>>> particular, I have a few questions about copyright, trademark, and patents
>>> rights being offered to implementors of the Twitter API.  My longstanding
>>> sense is that Twitter has indicated the spirit of offering the API under
>>> generally permissive usage rights, so hopefully this thread can move the
>>> discussion forward a bit and perhaps turn that spirit into something more
>>> formal.
>>>
>>>
>>> *Copyright*
>>>
>>> **Question: Under what terms may third-party library and application
>>> developers use the text and images associated with the Twitter API
>>> specification?
>>>
>>> Example use case:  Third-party library developers would like to copy
>>> and/or modify the text of the Twitter API specification in the library's
>>> documentation.  This is preferred over inventing new text for the
>>> documentation, the meaning of which could deviate from the canonical version
>>> in the Twitter API specification.
>>>
>>> Potential concern:  Without a copyright license, implementors may not be
>>> permitted to use or reuse the Twitter API specification text in third-party
>>> library documentation.
>>>
>>> Current state:  While the Twitter API specification itself doesn't
>>> mention copyright, the Twitter Terms of Service (http://twitter.com/tos) 
>>> state:
>>> "The Services are protected by copyright, trademark, and other laws of both
>>> the United States and foreign countries," which could reasonably be
>>> interpreted to apply to the Twitter API service as well.
>>>
>>> Possible desired outcome:  The Twitter API specification is made
>>> available under a permissive and derivative works-friendly copyright
>>> license, such as th

Re: [twitter-dev] Question about licensing

[DeWitt Clinton]

Thanks for the update, Ryan.  And thanks for the compliment on the Google
Code policies page -- that page was one of the first things I launched at
Google back when we were being asked the exact same questions.

We also added patent licences, which follow this general format:

  http://code.google.com/apis/gdata/patent-license.html

Granted, that license is maybe even more liberal than most implementors
require.   Also, that was before we had a reusable patent agreement, such as
the OWFa: http://openwebfoundation.org/legal/agreement/.  If I did something
new outside Google I'd probably go the OWF route now.

Trademark is trickier.  I'm not sure we've quite nailed it yet at Google,
actually.  But the basic framework might be a statement that enumerates
specific marks and lists specific appropriate usages.  You can always add to
that list over time, and this would protect Twitter's rights in the cases
you haven't anticipated yet.

Thanks again for pushing this forward.  Cheers,

-DeWitt


On Sat, Jan 23, 2010 at 11:28 AM, Ryan Sarver  wrote:

> DeWitt,
>
> Thanks for the serious patience on this thread. We're constantly trying to
> adapt to the needs of the developer community, and you're right that we
> haven't published guidelines around use of the Twitter API specifications.
> But, we are working on it and I wanted to share some of the thought that
> will help drive the policy.
>
> What we do know is that there is a clear need for a flexible, friendly and
> responsible policy. Policies such as this one (
> http://code.google.com/policies.html#restrictions) are a good start, and I
> can share some principles we'd like to live by. CC-BY should apply to a lot
> of the tools we release. You should be able to copy, modify and make
> derivatives of our specifications (with attribution). We shouldn't throw
> arbitrary roadblocks in your way, such as preventing you from naming a
> library "tweet." And last, we shouldn't pester you for utilizing our patents
> underlying these specifications.
>
> These are flexible and friendly principles, and in exchange we ask the
> development community to act responsibly. For example, naming a library
> "twitter" is one thing. Naming your application "twitter" is quite another.
>
> We hear you loud and clear, so please bear with us as we translate these
> principles into official policy.
>
> Thanks again for your patience and interest :)
>
> Best, Ryan
>
> On Tue, Nov 24, 2009 at 9:12 AM, DeWitt Clinton wrote:
>
>> Hi all,
>>
>> I recently received a request to implement the "retweet" api calls in the
>> python-twitter and java-twitter libraries, but before I proceed I was hoping
>> for a bit of clarification around the licensing terms for the Twitter API.
>>
>> My layman's understanding is that without explicit terms there are
>> relatively few rights offered by default regarding a specification.  In
>> particular, I have a few questions about copyright, trademark, and patents
>> rights being offered to implementors of the Twitter API.  My longstanding
>> sense is that Twitter has indicated the spirit of offering the API under
>> generally permissive usage rights, so hopefully this thread can move the
>> discussion forward a bit and perhaps turn that spirit into something more
>> formal.
>>
>>
>> *Copyright*
>>
>> **Question: Under what terms may third-party library and application
>> developers use the text and images associated with the Twitter API
>> specification?
>>
>> Example use case:  Third-party library developers would like to copy
>> and/or modify the text of the Twitter API specification in the library's
>> documentation.  This is preferred over inventing new text for the
>> documentation, the meaning of which could deviate from the canonical version
>> in the Twitter API specification.
>>
>> Potential concern:  Without a copyright license, implementors may not be
>> permitted to use or reuse the Twitter API specification text in third-party
>> library documentation.
>>
>> Current state:  While the Twitter API specification itself doesn't mention
>> copyright, the Twitter Terms of Service (http://twitter.com/tos) state:
>> "The Services are protected by copyright, trademark, and other laws of both
>> the United States and foreign countries," which could reasonably be
>> interpreted to apply to the Twitter API service as well.
>>
>> Possible desired outcome:  The Twitter API specification is made available
>> under a permissive and derivative works-friendly copyright license, such as
>> the Creative Commons BY or BY-SA license.
>>
>>
>> *Trademark*
>>
>> Question: Under what terms may third-party library and application
>> developers use the various registered service marks of Twitter, Inc?
>>
>> Example use case:  Third-party library authors would like to use the words
>> "twitter", "tweet", "retweet" (all live service marks of Twitter, Inc) in
>> their libraries.  This is preferred over third-party library authors
>> inventing new terms for API methods such as "re

Re: [twitter-dev] Question about "Twitter" use in library names

[DeWitt Clinton]

That's great news.  Thank you, Ryan.

How about terms like "tweet" and "retweet"?  Or more generally, any word on
the questions raised in the "Question about licensing" thread?


http://groups.google.com/group/twitter-development-talk/browse_thread/thread/9f90046f6469fb7b/954f6dc75e00e992

In particular, it would be great to get clarification in writing on
twitter.com -- not sure if your mail here is binding :) -- about the terms
for acceptable trademark usage, copyright claims, and patent claims, for
third party libraries and third party implementations of the Twitter API.

I fully understand that these are difficult questions, and certainly
appreciate the effort it takes to get all the legal concerns addressed.
 Thanks again for chasing these down!

-DeWitt



On Wed, Jan 13, 2010 at 10:48 AM, Ryan Sarver  wrote:

> Duane,
>
> I've been able to follow up with our lawyers and they confirmed that it is
> ok to include "Twitter" in the name of libraries that developers build.
> Sorry it took so long to follow up, but I wanted to make sure we got a
> strong, final answer back before responding.
>
> Best, Ryan
>
>
> On Fri, Dec 4, 2009 at 1:39 PM, Duane Roelands 
> wrote:
>
>> A question for the Twitter team:
>>
>> I'm the developer and maintainer of an open source library called
>> "TwitterVB".  Can I expect a nastygram from your lawyers at some
>> point?  Or is there some way I can have the project "vetted" to avoid
>> such a thing in the future?
>>
>
>

Re: [twitter-dev] Question about "Twitter" use in library names

[Ryan Sarver]

Duane,

I've been able to follow up with our lawyers and they confirmed that it is
ok to include "Twitter" in the name of libraries that developers build.
Sorry it took so long to follow up, but I wanted to make sure we got a
strong, final answer back before responding.

Best, Ryan

On Fri, Dec 4, 2009 at 1:39 PM, Duane Roelands wrote:

> A question for the Twitter team:
>
> I'm the developer and maintainer of an open source library called
> "TwitterVB".  Can I expect a nastygram from your lawyers at some
> point?  Or is there some way I can have the project "vetted" to avoid
> such a thing in the future?
>

Re: [twitter-dev] question about PIN code

[ryan alford]

When you direct the user to oauth/authorize, the user will be presented with
an "Allow"/"Deny" page from Twitter.  If they "Allow", they then will be
given an PIN on the screen.  The user will need to give this PIN to you.

Ryan

On Tue, Jan 12, 2010 at 7:59 PM, dduby  wrote:

> hi,,,
> i am trying to make mobile app for Android.
> For athenticaion, i followed this procedure.
> i got concumer key and secret key,, problem is , i don't know how to
> generate PIN code..
> is there any web site?
> please answer my question.
> The application uses oauth/request_token to obtain a request token
> from twitter.com.
> The application directs the user to oauth/authorize on twitter.com.
> After obtaining approval from the user, a prompt on twitter.com will
> display a 7 digit PIN.
> The user is instructed to copy this PIN and return to the appliction.
> The application will prompt the user to enter the PIN from step 4.
> The application uses the PIN as the value for the oauth_verifier
> parameter in a call to oauth/access_token which will verify the PIN
> and exchange a request_token for an access_token.
> Twitter will return an access_token for the application to generate
> subsequent OAuth signatures.
>

[twitter-dev] question about PIN code

[dduby]

hi,,,
i am trying to make mobile app for Android.
For athenticaion, i followed this procedure.
i got concumer key and secret key,, problem is , i don't know how to
generate PIN code..
is there any web site?
please answer my question.
The application uses oauth/request_token to obtain a request token
from twitter.com.
The application directs the user to oauth/authorize on twitter.com.
After obtaining approval from the user, a prompt on twitter.com will
display a 7 digit PIN.
The user is instructed to copy this PIN and return to the appliction.
The application will prompt the user to enter the PIN from step 4.
The application uses the PIN as the value for the oauth_verifier
parameter in a call to oauth/access_token which will verify the PIN
and exchange a request_token for an access_token.
Twitter will return an access_token for the application to generate
subsequent OAuth signatures.

Re: [twitter-dev] Question concerning posts per hour

[Raffi Krikorian]

http://apiwiki.twitter.com/Rate-limiting

is that what you're looking for?

On Tue, Dec 22, 2009 at 7:35 AM, Mark Essel  wrote:

> Heyo, our company (Victus Media, http://victusmedia.com) is leveraging
> semantic processing on twitter public streams to market our service to
> potential users.
> Is there a healthy send rate that is acceptable for a user account for
> us to use?
>
> We're using http://www.twitter.com/semantic2 at the moment but only 12
> per hour, and would very much like to increase that rate to a higher
> level.
>
> What's a safe but fair limit?
>



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

[twitter-dev] Question concerning posts per hour

[Mark Essel]

Heyo, our company (Victus Media, http://victusmedia.com) is leveraging
semantic processing on twitter public streams to market our service to
potential users.
Is there a healthy send rate that is acceptable for a user account for
us to use?

We're using http://www.twitter.com/semantic2 at the moment but only 12
per hour, and would very much like to increase that rate to a higher
level.

What's a safe but fair limit?

Re: [twitter-dev] Question about "Twitter" use in library names

[Ryan Sarver]

Just wanted to follow up with everyone and let you know we are still on this
and haven't forgotten about the thread. Hopefully will have an answer for
you soon.

Best, Ryan

2009/12/5 Ryan Sarver 

> Duane,
>
> We definitely don't want to be sending any "nastygrams", especially for
> something that helps the community. I put a note into our legal / marks
> department so that I can get an answer back to you and everyone else. Please
> bear with us as it could take a bit, but I'll get you an answer.
>
> Best, Ryan
>
>
> On Fri, Dec 4, 2009 at 1:39 PM, Duane Roelands 
> wrote:
>
>> A question for the Twitter team:
>>
>> I'm the developer and maintainer of an open source library called
>> "TwitterVB".  Can I expect a nastygram from your lawyers at some
>> point?  Or is there some way I can have the project "vetted" to avoid
>> such a thing in the future?
>>
>
>

Re: [twitter-dev] Question regarding profile bg image... Please direct me

[Mark McBride]

You should be able to use this call to do what you describe

http://apiwiki.twitter.com/Twitter-REST-API-Method:-account
update_profile_background_image

You would have to have access to the image, but that shouldn't be too
tough (pick from a Flickr photo set, that sort of thing)

On Wed, Dec 9, 2009 at 11:46 AM, traxus  wrote:
> This is probably the wrong place to ask as this isn't quite an API
> matter, so please forgive me and point me in the right direction if it
> is...
>
> I have an idea where I would like to use php's imagecreate() to
> dynamically create a background image for a profile on a periodic
> basis...
>
> I'm thinking something along the lines of a 'photo of the week'
> appearing as a sidebar (on monitors that have a large enough width...)
>
> Being that custom background images have to be uploaded from the users
> local computer, what are the possibilities here? (Could this be done
> through the API?)
>
> Just a rough sketch in my head, thanks...
>



-- 
   ---Mark

http://twitter.com/mccv

[twitter-dev] Question regarding profile bg image... Please direct me

[traxus]

This is probably the wrong place to ask as this isn't quite an API
matter, so please forgive me and point me in the right direction if it
is...

I have an idea where I would like to use php's imagecreate() to
dynamically create a background image for a profile on a periodic
basis...

I'm thinking something along the lines of a 'photo of the week'
appearing as a sidebar (on monitors that have a large enough width...)

Being that custom background images have to be uploaded from the users
local computer, what are the possibilities here? (Could this be done
through the API?)

Just a rough sketch in my head, thanks...

Re: [twitter-dev] Question about "Twitter" use in library names

[Ryan Sarver]

Duane,

We definitely don't want to be sending any "nastygrams", especially for
something that helps the community. I put a note into our legal / marks
department so that I can get an answer back to you and everyone else. Please
bear with us as it could take a bit, but I'll get you an answer.

Best, Ryan

On Fri, Dec 4, 2009 at 1:39 PM, Duane Roelands wrote:

> A question for the Twitter team:
>
> I'm the developer and maintainer of an open source library called
> "TwitterVB".  Can I expect a nastygram from your lawyers at some
> point?  Or is there some way I can have the project "vetted" to avoid
> such a thing in the future?
>

Re: [twitter-dev] Question about "Twitter" use in library names

[John Meyer]

On 12/4/2009 2:39 PM, Duane Roelands wrote:

A question for the Twitter team:

I'm the developer and maintainer of an open source library called
"TwitterVB".  Can I expect a nastygram from your lawyers at some
point?  Or is there some way I can have the project "vetted" to avoid
such a thing in the future?

   


I don't play a lawyer on TV (it's too small for starters), but the fact 
that you aren't making any money off of it and the fact that they're 
linking to it with that name bodes pretty well. 
http://apiwiki.twitter.com/Terms-of-Service

RE: [twitter-dev] Question about licensing

[mycroftt]

 Ryan,
    I realized a few months ago that there were some problems along the lines you have mentioned. I stopped development on my project partially due to these issues and the extremely plastic state of the API. I continue to watch this forum to keep abreast of the state of things but I doubt I will get back into twitter deveopment as an individual. Thanks for your question and I'll watch for the answer. 
 

 Original Message Subject: Re: [twitter-dev] Question about licensingFrom: Ryan Sarver Date: Thu, December 03, 2009 11:51 amTo: twitter-development-talk@googlegroups.comJust an update from our end: I am still working with our General Counsel to get answers to the questions, but it's going to take a bit. So please bear with us but we'll get an update to you in the coming weeks after we get back from LeWeb.

Thanks, Ryan
On Tue, Nov 24, 2009 at 9:12 AM, DeWitt Clinton <dclin...@gmail.com> wrote:
Hi all,

I recently received a request to implement the "retweet" api calls in the python-twitter and java-twitter libraries, but before I proceed I was hoping for a bit of clarification around the licensing terms for the Twitter API.

My layman's understanding is that without explicit terms there are relatively few rights offered by default regarding a specification.  In particular, I have a few questions about copyright, trademark, and patents rights being offered to implementors of the Twitter API.  My longstanding sense is that Twitter has indicated the spirit of offering the API under generally permissive usage rights, so hopefully this thread can move the discussion forward a bit and perhaps turn that spirit into something more formal.


Copyright

Question: Under what terms may third-party library and application developers use the text and images associated with the Twitter API specification?

Example use case:  Third-party library developers would like to copy and/or modify the text of the Twitter API specification in the library's documentation.  This is preferred over inventing new text for the documentation, the meaning of which could deviate from the canonical version in the Twitter API specification.

Potential concern:  Without a copyright license, implementors may not be permitted to use or reuse the Twitter API specification text in third-party library documentation.

Current state:  While the Twitter API specification itself doesn't mention copyright, the Twitter Terms of Service (http://twitter.com/tos) state: "The Services are protected by copyright, trademark, and other laws of both the United States and foreign countries," which could reasonably be interpreted to apply to the Twitter API service as well.

Possible desired outcome:  The Twitter API specification is made available under a permissive and derivative works-friendly copyright license, such as the Creative Commons BY or BY-SA license.


Trademark

Question: Under what terms may third-party library and application developers use the various registered service marks of Twitter, Inc?  

Example use case:  Third-party library authors would like to use the words "twitter", "tweet", "retweet" (all live service marks of Twitter, Inc) in their libraries.  This is preferred over third-party library authors inventing new terms for API methods such as "retweet".

Potential concern: Without terms that specify where and how the various registered marks can be used, third-party library implementors may or may not be permitted to use terms such as "twitter", "tweet", "retweet", etc., in their libraries.

Current state:  The Twitter Terms of Service (http://twitter.com/tos) appear to prohibit such use: "Nothing in the Terms gives you a right to use the Twitter name or any of the Twitter trademarks, logos, domain names, and other distinctive brand features."

Possible desired outcome:  Twitter publishes acceptable-use guidelines for registered marks in third-party libraries and third-party applications.


Patent

Question:  Under what terms may third-party library and application developers make use of current or future patent claims made by Twitter, Inc?

Example use cases:  A third-party developer may wish to implement an independent service that conforms to the Twitter API method signatures, or a third-party developer may wish to implement a library that implements portions of the Twitter API on the client.

Potential concern:  Without terms that specify how third-party developers may use patent claims (if any) made by Twitter, Inc, implementors assume the risk of potentially infringing on current or future claims made by Twitter.

Current state:  Twitter (to my knowledge) has made no statement regarding patent claims with respect to implementations of the Twitter API.

Possible desired outcome:  The Twitter API specification is made available under a patent agreement, such as the Open Web F

[twitter-dev] Question about "Twitter" use in library names

[Duane Roelands]

A question for the Twitter team:

I'm the developer and maintainer of an open source library called
"TwitterVB".  Can I expect a nastygram from your lawyers at some
point?  Or is there some way I can have the project "vetted" to avoid
such a thing in the future?

Re: [twitter-dev] Question about licensing

[Ryan Sarver]

Just an update from our end: I am still working with our General Counsel to
get answers to the questions, but it's going to take a bit. So please bear
with us but we'll get an update to you in the coming weeks after we get back
from LeWeb.

Thanks, Ryan

On Tue, Nov 24, 2009 at 9:12 AM, DeWitt Clinton  wrote:

> Hi all,
>
> I recently received a request to implement the "retweet" api calls in the
> python-twitter and java-twitter libraries, but before I proceed I was hoping
> for a bit of clarification around the licensing terms for the Twitter API.
>
> My layman's understanding is that without explicit terms there are
> relatively few rights offered by default regarding a specification.  In
> particular, I have a few questions about copyright, trademark, and patents
> rights being offered to implementors of the Twitter API.  My longstanding
> sense is that Twitter has indicated the spirit of offering the API under
> generally permissive usage rights, so hopefully this thread can move the
> discussion forward a bit and perhaps turn that spirit into something more
> formal.
>
>
> *Copyright*
>
> **Question: Under what terms may third-party library and application
> developers use the text and images associated with the Twitter API
> specification?
>
> Example use case:  Third-party library developers would like to copy and/or
> modify the text of the Twitter API specification in the library's
> documentation.  This is preferred over inventing new text for the
> documentation, the meaning of which could deviate from the canonical version
> in the Twitter API specification.
>
> Potential concern:  Without a copyright license, implementors may not be
> permitted to use or reuse the Twitter API specification text in third-party
> library documentation.
>
> Current state:  While the Twitter API specification itself doesn't mention
> copyright, the Twitter Terms of Service (http://twitter.com/tos) state:
> "The Services are protected by copyright, trademark, and other laws of both
> the United States and foreign countries," which could reasonably be
> interpreted to apply to the Twitter API service as well.
>
> Possible desired outcome:  The Twitter API specification is made available
> under a permissive and derivative works-friendly copyright license, such as
> the Creative Commons BY or BY-SA license.
>
>
> *Trademark*
>
> Question: Under what terms may third-party library and application
> developers use the various registered service marks of Twitter, Inc?
>
> Example use case:  Third-party library authors would like to use the words
> "twitter", "tweet", "retweet" (all live service marks of Twitter, Inc) in
> their libraries.  This is preferred over third-party library authors
> inventing new terms for API methods such as "retweet".
>
> Potential concern: Without terms that specify where and how the various
> registered marks can be used, third-party library implementors may or may
> not be permitted to use terms such as "twitter", "tweet", "retweet", etc.,
> in their libraries.
>
> Current state:  The Twitter Terms of Service (http://twitter.com/tos)
> appear to prohibit such use: "Nothing in the Terms gives you a right to use
> the Twitter name or any of the Twitter trademarks, logos, domain names, and
> other distinctive brand features."
>
> Possible desired outcome:  Twitter publishes acceptable-use guidelines for
> registered marks in third-party libraries and third-party applications.
>
>
> *Patent*
>
> Question:  Under what terms may third-party library and application
> developers make use of current or future patent claims made by Twitter, Inc?
>
> Example use cases:  A third-party developer may wish to implement an
> independent service that conforms to the Twitter API method signatures, or a
> third-party developer may wish to implement a library that implements
> portions of the Twitter API on the client.
>
> Potential concern:  Without terms that specify how third-party developers
> may use patent claims (if any) made by Twitter, Inc, implementors assume the
> risk of potentially infringing on current or future claims made by Twitter.
>
> Current state:  Twitter (to my knowledge) has made no statement regarding
> patent claims with respect to implementations of the Twitter API.
>
> Possible desired outcome:  The Twitter API specification is made available
> under a patent agreement, such as the Open Web Foundation Agreement (
> http://openwebfoundation.org/legal/), or a similarly permissive agreement,
> such as the Microsoft Open Specification Promise (
> http://www.microsoft.com/Interop/osp/) or a Google-style patent license (
> http://code.google.com/apis/gdata/patent-license.html).
>
>
> ...
>
> I realize that these are meaty (and potentially legally sensitive)
> questions of course, and likely ones that are not easily answered in a
> public forum.  However, any feedback from the team would certainly be
> appreciated.
>
> The fact that people are even thinking about these types of questions 

Re: [twitter-dev] Question about licensing

[DeWitt Clinton]

Great, thank you, Ryan.  Looking forward to it.

Please let me know on or off list if there is anything I can do to help.

Cheers,

-DeWitt

On Tue, Nov 24, 2009 at 11:08 AM, Ryan Sarver  wrote:

> DeWitt,
>
> Thanks for the email. These are all great questions and I want to make
> sure I get all the appropriate answers for you and other people on the
> thread so it's clear and transparent. Let me work internally to make
> sure we get answers to these and get back to you.
>
> The more general answer is that we are working on this as we speak, so
> there should be some more clarity in the near future regardless of
> this thread. Thanks for the interest and support.
>
> Best, Ryan
>
> On Tue, Nov 24, 2009 at 9:12 AM, DeWitt Clinton 
> wrote:
> > Hi all,
> > I recently received a request to implement the "retweet" api calls in the
> > python-twitter and java-twitter libraries, but before I proceed I was
> hoping
> > for a bit of clarification around the licensing terms for the Twitter
> API.
> > My layman's understanding is that without explicit terms there are
> > relatively few rights offered by default regarding a specification.  In
> > particular, I have a few questions about copyright, trademark, and
> patents
> > rights being offered to implementors of the Twitter API.  My longstanding
> > sense is that Twitter has indicated the spirit of offering the API under
> > generally permissive usage rights, so hopefully this thread can move the
> > discussion forward a bit and perhaps turn that spirit into something more
> > formal.
> >
> > Copyright
> > Question: Under what terms may third-party library and application
> > developers use the text and images associated with the Twitter API
> > specification?
> > Example use case:  Third-party library developers would like to copy
> and/or
> > modify the text of the Twitter API specification in the library's
> > documentation.  This is preferred over inventing new text for the
> > documentation, the meaning of which could deviate from the canonical
> version
> > in the Twitter API specification.
> > Potential concern:  Without a copyright license, implementors may not be
> > permitted to use or reuse the Twitter API specification text in
> third-party
> > library documentation.
> > Current state:  While the Twitter API specification itself doesn't
> mention
> > copyright, the Twitter Terms of Service (http://twitter.com/tos) state:
> "The
> > Services are protected by copyright, trademark, and other laws of both
> the
> > United States and foreign countries," which could reasonably be
> interpreted
> > to apply to the Twitter API service as well.
> > Possible desired outcome:  The Twitter API specification is made
> available
> > under a permissive and derivative works-friendly copyright license, such
> as
> > the Creative Commons BY or BY-SA license.
> >
> > Trademark
> > Question: Under what terms may third-party library and application
> > developers use the various registered service marks of Twitter, Inc?
> > Example use case:  Third-party library authors would like to use the
> words
> > "twitter", "tweet", "retweet" (all live service marks of Twitter, Inc) in
> > their libraries.  This is preferred over third-party library authors
> > inventing new terms for API methods such as "retweet".
> > Potential concern: Without terms that specify where and how the various
> > registered marks can be used, third-party library implementors may or may
> > not be permitted to use terms such as "twitter", "tweet", "retweet",
> etc.,
> > in their libraries.
> > Current state:  The Twitter Terms of Service (http://twitter.com/tos)
> appear
> > to prohibit such use: "Nothing in the Terms gives you a right to use the
> > Twitter name or any of the Twitter trademarks, logos, domain names, and
> > other distinctive brand features."
> > Possible desired outcome:  Twitter publishes acceptable-use guidelines
> for
> > registered marks in third-party libraries and third-party applications.
> >
> > Patent
> > Question:  Under what terms may third-party library and application
> > developers make use of current or future patent claims made by Twitter,
> Inc?
> > Example use cases:  A third-party developer may wish to implement an
> > independent service that conforms to the Twitter API method signatures,
> or a
> > third-party developer may wish to implement a library that implements
> > portions of the Twitter API on the client.
> > Potential concern:  Without terms that specify how third-party developers
> > may use patent claims (if any) made by Twitter, Inc, implementors assume
> the
> > risk of potentially infringing on current or future claims made by
> Twitter.
> > Current state:  Twitter (to my knowledge) has made no statement regarding
> > patent claims with respect to implementations of the Twitter API.
> > Possible desired outcome:  The Twitter API specification is made
> available
> > under a patent agreement, such as the Open Web Foundation Agreement
> > (http://openw

Re: [twitter-dev] Question about licensing

[Ryan Sarver]

DeWitt,

Thanks for the email. These are all great questions and I want to make
sure I get all the appropriate answers for you and other people on the
thread so it's clear and transparent. Let me work internally to make
sure we get answers to these and get back to you.

The more general answer is that we are working on this as we speak, so
there should be some more clarity in the near future regardless of
this thread. Thanks for the interest and support.

Best, Ryan

On Tue, Nov 24, 2009 at 9:12 AM, DeWitt Clinton  wrote:
> Hi all,
> I recently received a request to implement the "retweet" api calls in the
> python-twitter and java-twitter libraries, but before I proceed I was hoping
> for a bit of clarification around the licensing terms for the Twitter API.
> My layman's understanding is that without explicit terms there are
> relatively few rights offered by default regarding a specification.  In
> particular, I have a few questions about copyright, trademark, and patents
> rights being offered to implementors of the Twitter API.  My longstanding
> sense is that Twitter has indicated the spirit of offering the API under
> generally permissive usage rights, so hopefully this thread can move the
> discussion forward a bit and perhaps turn that spirit into something more
> formal.
>
> Copyright
> Question: Under what terms may third-party library and application
> developers use the text and images associated with the Twitter API
> specification?
> Example use case:  Third-party library developers would like to copy and/or
> modify the text of the Twitter API specification in the library's
> documentation.  This is preferred over inventing new text for the
> documentation, the meaning of which could deviate from the canonical version
> in the Twitter API specification.
> Potential concern:  Without a copyright license, implementors may not be
> permitted to use or reuse the Twitter API specification text in third-party
> library documentation.
> Current state:  While the Twitter API specification itself doesn't mention
> copyright, the Twitter Terms of Service (http://twitter.com/tos) state: "The
> Services are protected by copyright, trademark, and other laws of both the
> United States and foreign countries," which could reasonably be interpreted
> to apply to the Twitter API service as well.
> Possible desired outcome:  The Twitter API specification is made available
> under a permissive and derivative works-friendly copyright license, such as
> the Creative Commons BY or BY-SA license.
>
> Trademark
> Question: Under what terms may third-party library and application
> developers use the various registered service marks of Twitter, Inc?
> Example use case:  Third-party library authors would like to use the words
> "twitter", "tweet", "retweet" (all live service marks of Twitter, Inc) in
> their libraries.  This is preferred over third-party library authors
> inventing new terms for API methods such as "retweet".
> Potential concern: Without terms that specify where and how the various
> registered marks can be used, third-party library implementors may or may
> not be permitted to use terms such as "twitter", "tweet", "retweet", etc.,
> in their libraries.
> Current state:  The Twitter Terms of Service (http://twitter.com/tos) appear
> to prohibit such use: "Nothing in the Terms gives you a right to use the
> Twitter name or any of the Twitter trademarks, logos, domain names, and
> other distinctive brand features."
> Possible desired outcome:  Twitter publishes acceptable-use guidelines for
> registered marks in third-party libraries and third-party applications.
>
> Patent
> Question:  Under what terms may third-party library and application
> developers make use of current or future patent claims made by Twitter, Inc?
> Example use cases:  A third-party developer may wish to implement an
> independent service that conforms to the Twitter API method signatures, or a
> third-party developer may wish to implement a library that implements
> portions of the Twitter API on the client.
> Potential concern:  Without terms that specify how third-party developers
> may use patent claims (if any) made by Twitter, Inc, implementors assume the
> risk of potentially infringing on current or future claims made by Twitter.
> Current state:  Twitter (to my knowledge) has made no statement regarding
> patent claims with respect to implementations of the Twitter API.
> Possible desired outcome:  The Twitter API specification is made available
> under a patent agreement, such as the Open Web Foundation Agreement
> (http://openwebfoundation.org/legal/), or a similarly permissive agreement,
> such as the Microsoft Open Specification Promise
> (http://www.microsoft.com/Interop/osp/) or a Google-style patent license
> (http://code.google.com/apis/gdata/patent-license.html).
>
> ...
> I realize that these are meaty (and potentially legally sensitive) questions
> of course, and likely ones that are not easily answered in a 

[twitter-dev] Question about licensing

[DeWitt Clinton]

Hi all,

I recently received a request to implement the "retweet" api calls in the
python-twitter and java-twitter libraries, but before I proceed I was hoping
for a bit of clarification around the licensing terms for the Twitter API.

My layman's understanding is that without explicit terms there are
relatively few rights offered by default regarding a specification.  In
particular, I have a few questions about copyright, trademark, and patents
rights being offered to implementors of the Twitter API.  My longstanding
sense is that Twitter has indicated the spirit of offering the API under
generally permissive usage rights, so hopefully this thread can move the
discussion forward a bit and perhaps turn that spirit into something more
formal.


*Copyright*

**Question: Under what terms may third-party library and application
developers use the text and images associated with the Twitter API
specification?

Example use case:  Third-party library developers would like to copy and/or
modify the text of the Twitter API specification in the library's
documentation.  This is preferred over inventing new text for the
documentation, the meaning of which could deviate from the canonical version
in the Twitter API specification.

Potential concern:  Without a copyright license, implementors may not be
permitted to use or reuse the Twitter API specification text in third-party
library documentation.

Current state:  While the Twitter API specification itself doesn't mention
copyright, the Twitter Terms of Service (http://twitter.com/tos) state: "The
Services are protected by copyright, trademark, and other laws of both the
United States and foreign countries," which could reasonably be interpreted
to apply to the Twitter API service as well.

Possible desired outcome:  The Twitter API specification is made available
under a permissive and derivative works-friendly copyright license, such as
the Creative Commons BY or BY-SA license.


*Trademark*

Question: Under what terms may third-party library and application
developers use the various registered service marks of Twitter, Inc?

Example use case:  Third-party library authors would like to use the words
"twitter", "tweet", "retweet" (all live service marks of Twitter, Inc) in
their libraries.  This is preferred over third-party library authors
inventing new terms for API methods such as "retweet".

Potential concern: Without terms that specify where and how the various
registered marks can be used, third-party library implementors may or may
not be permitted to use terms such as "twitter", "tweet", "retweet", etc.,
in their libraries.

Current state:  The Twitter Terms of Service (http://twitter.com/tos) appear
to prohibit such use: "Nothing in the Terms gives you a right to use the
Twitter name or any of the Twitter trademarks, logos, domain names, and
other distinctive brand features."

Possible desired outcome:  Twitter publishes acceptable-use guidelines for
registered marks in third-party libraries and third-party applications.


*Patent*

Question:  Under what terms may third-party library and application
developers make use of current or future patent claims made by Twitter, Inc?

Example use cases:  A third-party developer may wish to implement an
independent service that conforms to the Twitter API method signatures, or a
third-party developer may wish to implement a library that implements
portions of the Twitter API on the client.

Potential concern:  Without terms that specify how third-party developers
may use patent claims (if any) made by Twitter, Inc, implementors assume the
risk of potentially infringing on current or future claims made by Twitter.

Current state:  Twitter (to my knowledge) has made no statement regarding
patent claims with respect to implementations of the Twitter API.

Possible desired outcome:  The Twitter API specification is made available
under a patent agreement, such as the Open Web Foundation Agreement (
http://openwebfoundation.org/legal/), or a similarly permissive agreement,
such as the Microsoft Open Specification Promise (
http://www.microsoft.com/Interop/osp/) or a Google-style patent license (
http://code.google.com/apis/gdata/patent-license.html).


...

I realize that these are meaty (and potentially legally sensitive) questions
of course, and likely ones that are not easily answered in a public forum.
 However, any feedback from the team would certainly be appreciated.

The fact that people are even thinking about these types of questions is a
good thing, both for open specification development in general, but also
because it shows how successful and important the Twitter API is today.  So
again, continued success with the API, and I look forward to hearing more
from the team.

-DeWitt

Re: [twitter-dev] Question and/or Feature Request: in-reply-to-direct-message-id for DMs

[Chris Thomson]

I'd suggest opening a new issue on the Twitter API bug/enhancement tracker so 
others can 'star' it to show interest: 
http://code.google.com/p/twitter-api/issues/entry

--
Chris Thomson

On 2009-11-21, at 2:11 PM, Michael Steuer wrote:

>> Hi Twitter, Twitter Developers,
>> 
>> Let me start with the question: is there a good reason why the payload for 
>> direct_messages doesn’t have a “in-reply-to-direct-message-id”, just like 
>> the “in-reply-to-status-id” for status updates? I know that for my use 
>> cases, and I’m sure for some of yours, it’d be helpful to know if a DM was a 
>> reply to an earlier one, or a new DM to the recipient.
>> 
>> So here’s the feature request: can we pretty please have a 
>> “in-reply-to-direct-message-id” in the DM API payload? And if you consider 
>> this a reasonable request, how long do you think that would take ;)
>> 
>> THANK YOU!
>> 
>> Michael.

[twitter-dev] Question and/or Feature Request: in-reply-to-direct-message-id for DMs

[Michael Steuer]

Hi Twitter, Twitter Developers,

Let me start with the question: is there a good reason why the  
payload for direct_messages doesn’t have a “in-reply-to-direct- 
message-id”, just like the “in-reply-to-status-id” for status  
updates? I know that for my use cases, and I’m sure for some of your 
s, it’d be helpful to know if a DM was a reply to an earlier one, or 
 a new DM to the recipient.


So here’s the feature request: can we pretty please have a “in- 
reply-to-direct-message-id” in the DM API payload? And if you consid 
er this a reasonable request, how long do you think that would take ;)


THANK YOU!

Michael.

[twitter-dev] question with twitter color design

[爵溪]

hi,all
In twitter's 'setting' we can choose 5 colors (background, text,
links, sidebar, sidebar border),but i notice that links in the sidebar
have a hover background color( just like white+sidebar background
color ) ,which is not from the 5 colors i metioned above and not
privided by the api .
any idea how to calculate this color?

[twitter-dev] Question about cursors

[jim.renkel]

In working with the new "cursorized" statuses/friends and statuses/
followers methods, I noticed that in the block of users returned by
these methods that contain the last of the users following or followed
by the requesting user, the next_cursor value is "0".

Is this a reliable, guaranteed indicator of the last block of users,
that there's no point in going further 'cause there ain't no further?

If so, will the value always be exactly "0" (although without the
quotes in the responses, i.e., is a string comparison for "0" safe, or
could it be "000", say, in which case a conversion to numeric and a
numeric comparison for 0 would be necessary. I would certainly like it
to be the former!

Either way, string or numeric, if this is a reliable indicator of the
last block of users, the documentation should be updated to reflect
this.

Thanks in advance.

Jim Renkel

[twitter-dev] Question about longevity of geo-coded tweets

[jim.renkel]

I just noticed this in the API wiki, under the statuses/update method:

"Currently, all geolocated information will be removed after seven
days."

Two questions:

1. What exactly will be removed: the geocoding attached to the tweet?
Or the whole tweet?

2. Why? I.e., why remove the geocoding or the whole tweet? I can think
of many use cases where it is important for the geocoding to remain as
long as the tweet remains. For example, I take a great vacation
picture, upload it to Twitpic, then tweet about it, including where I
took it. The location where I took the picture remains the same
forever. Why delete the geocoding information from the tweet, or the
whole tweet. This will just cause folk to put the geocoding
information in the text of the tweet, taking up valuable space and
reducing the value of geocoding tweets, and cause developers (Like me,
admittedly) to develop applications that put the geocoding in the text
of the tweet. With applications like that available, twitter users are
less likely to go to the botther of opting-in to twitter geocoding of
their tweets.

Comments expected and welcome.

Jim Renkel

[twitter-dev] Question with OAuth

[Sanny]

Hi,

I've a question regarding OAuth that I couldn't find answer for. Say a
user has registered in my site and added his twitter account using
'sign in with twitter' in my site. So I've got a access code and token
secret for that user. Now can I use that access code when the user is
not logged in Twitter to update his status or do something that
requires authentication?

As I can see in the flowchart in this page - 
http://apiwiki.twitter.com/Sign-in-with-Twitter,
it is probably not possible. Is there any other way out (using OAuth)?

Thanks.

[twitter-dev] Question on Account Suspension

[Chris Latko]

According to the new terms of service, it seems that there is much  
more that can get an account suspended. I've seen many friends have  
their accounts obliterated for apparently no reason. I'm wondering if  
Twitter is just a bit too trigger happy now. Having just been  
suspended, now I'm feeling the pain. This is my main account and  
without it, I feel lost at sea. I expect there are thousands of others  
who feel the same way. Is there anything I can do to not wait what  
seems like an eternity for my account to be reinstated?


Thanks.

--
Chris Latko
www.latko.org
@clatko

[twitter-dev] Question for Twitter guys: How to detect "denied" condition on Twitter oAuth page ? (is my approach correct ?)

[Amicus]

Can someone from Twitter please confirm that (a) and (c) will both
continue to work for oAuth.

If not, can you please let me know how to detect the case where the
user denies access to the application.

In either case, can you please point me to documentation on this
subject (if any documentation exists)


On Sep 16, 1:08 pm, New guy  wrote:
> Hi, while testing oAuth consumer code, I noticed that ..if the user
> denies access to the app
> (a) the post data includes "cancel=Deny"
> and
> (b) the response includes the string "OK, you've denied "
> and if the user clicks on the app link, the user gets redirected to
> the app URL with
> (c) the app URL including the word "denied" in it.
>
> I couldn't find any documentation stating that (a) and (c) are both
> oficially supported behaviors for oAuth with Twitter.
>
> I'm assuming that (a) and (c) are both corrects ways to determine
> whether the app has been denied access, but can someone please point
> me to documentation that confirms this.

[twitter-dev] Question About Post Commands

[Dan Kurszewski]

Does anyone know if there is a way with VB.Net or C# to login to
twitter, call 100 post commands, and then logout?

Here is my code for making a single post command in VB.Net.  As you
can see every time I call this function it has to login.  I would love
to have an array of url's and/or data that need to be processed for
the same username and password and having only one login.  I have
tried rearranging things several different ways with no luck.

Any help would be greatly appreciated.

---

Public Function ExecutePostCommand(ByVal url As String, ByVal
username As String, ByVal password As String, _
ByVal data As String) As String

Try
Dim request As HttpWebRequest = HttpWebRequest.Create(url)
request.ServicePoint.Expect100Continue = False

If Not String.IsNullOrEmpty(username) And Not
String.IsNullOrEmpty(password) Then
request.Credentials = New NetworkCredential(username,
password)
request.ContentType = "application/x-www-form-
urlencoded"
request.Method = "POST"

Dim bytes As Byte() = Encoding.UTF8.GetBytes(data)

request.ContentLength = bytes.Length

Dim s As Stream
s = request.GetRequestStream
s.Write(bytes, 0, bytes.Length)

Dim r As HttpWebResponse
r = request.GetResponse

Dim sr As StreamReader
sr = New StreamReader(r.GetResponseStream)

Return sr.ReadToEnd

Else
Throw New Exception("Username or Password is Null")
End If

Catch ex As Exception
Throw ex
End Try

End Function

[twitter-dev] Question on example code

[BarefootSanders]

Hi all.  I've been working on a twitter app using the new OAuth
protocol and the example code provided by twitter (This is the code:
http://github.com/abraham/twitteroauth).  I'm sure some of you have
seen/used it before.  I had a question and was hoping someone could
help me out.

What I'm noticing is that when a twitter object is created, i.e.

$to = new TwitterOAuth($consumer_key, $consumer_secret, $_SESSION
['oauth_access_token'], $_SESSION['oauth_access_token_secret']);

The method OAuthRequest is called to actually perform the request from
the Twitter api.  However when I look in the TwitterOAuth class there
is no method named OAuthRequest.  There is a method named oAuthRequest
(notice the change in case and I thought PHP was case sensitive) and
I'm trying to figure out what function is actually being called.  It
seems like oAuthRequest is being called because the params match up
but idk.

What I'm trying to do with this is actually make an unauthenticated
request for api calls that dont need to be authenticated i.e.
http://twitter.com/users/show.xml?screen_name=dougw

So I changed the constructor to this.

if ($_SESSION['oauth_access_token'] === NULL && $_SESSION
['oauth_access_token_secret'] === NULL) {
  /* Create TwitterOAuth object with app key/secret and token key/
secret from default phase */
  $to = new TwitterOAuth($consumer_key, $consumer_secret, $_SESSION
['oauth_request_token'], $_SESSION['oauth_request_token_secret']);
  /* Request access tokens from twitter */
  $tok = $to->getAccessToken();

  /* Save the access tokens. Normally these would be saved in a
database for future use. */
  $_SESSION['oauth_access_token'] = $tok['oauth_token'];
  $_SESSION['oauth_access_token_secret'] = $tok
['oauth_token_secret'];
}

And want to do this:
$to = new TwitterOAuth();
$result = $to->OAuthRequest($url);

print_r($result);

But it's not working and I cant figure out what function is being
called.

Hope I didn't ramble to long.. Any help would be much appreciated.

[twitter-dev] Question on Whitelisting

[jester...@hotmail.com]

Recently my ip address and username were added to the whitelist. My
assumptions at that time were that all requests coming the application
(on this particular server) would be included in this pool of 20,000
regardless of whether they are authenticated or not.

When I do the get limit API call, for my user it says 20,000 but if I
do it for a logged in user it still says 100. Will all this get worked
out on Twitter's side?

We would like to have our users (only certain users) send DM's to
their followers and the limit of 100 per hour may get in the way.

Like I asked above, will twitter look at the ip address of the request
when it comes in or the authenticated user?

[twitter-dev] Question regarding twitter replies

[Brother]

I am trying to get replies to a twitt I am creating programmatically.
The returned JSON from the creation of the status is:

{"in_reply_to_screen_name":null,"favorited":false,"user":
{"followers_count":3,"description":null,"profile_image_url":"http:\/\/
static.twitter.com\/images\/
default_profile_normal.png","screen_name":"obrand","url":null,"name":"obrand","protected":false,"location":null,"id":
12001302},"text":"Test to
twitter","in_reply_to_user_id":null,"in_reply_to_status_id":null,"created_at":"Thu
Mar 26 05:33:19 + 2009","truncated":false,"id":
1392831512,"source":"web"}

I go on the Twitter site using a different account and reply to this
twitt.

Then I perform the following:

curl -u obrand:mypassword 
http://twitter.com/statuses/replies.json?since_id=1392831512

And get nothing???

What am I doing wrong? I thought I could use the id returned in the
creation of the status (in the attached JSON) and use it to get any
replies to it (as I am trying to do via CURL)

What am I doing wrong?

Olivier

[twitter-dev] Question on Limits and Basic Authentication

[API_Tester]

Hi,

I realize that answers to my question might be discussed somewhere
already, if so please pardon my redundant questions.

1. Upon OAuth going public, will Basic Auth be discontinued? Reason: I
am working on some internal desktop applications (non public and non
spam) and thus OAuth is not really required.

2. In the 100 API calls per hr, are POST requests also included (like
create, destroy, update etc)

3. I assume search API requests are not a part of the 100 API call
limit (which is for the REST API), is running about 20 search request
spread out over an hour a reasonable one?

4. I see the 1000 updates limit, is the 1000 updates per IP or per
account. Trying to know the limitation, not learning to spam . if
it is per account and answer to question 2 is "POST requests are not
limited", then "A system (IP) could post upto 1000 updates per account
without using any of the 100 per hour api quota" is this right?

I could apply for whitelisting and try these, but I want to design the
app to work within the 100 api limitation.

Thanks for your time.

[twitter-dev] Question about authority to view social graphs

[Kevin Makice]

There are currently two ways you can use the API to see someone's
follow network (followers and those you follow). The first is the
"old" way: paginating through the /statuses/friends and statuses/
followers methods. These give a lot more information but do so in
smaller chunks. The "new" way is using the social graph methods, /
friends/ids and /followers/ids, that return the entire list but only
user IDs.

My question is, why can I use the former on protected accounts but not
the latter?

https://twitter.com/friends/ids/cmakice.xml
https://twitter.com/followers/ids/cmakice.xml

return 'Not authorized' if the account is protected (this one is) and
the authenticating account hasn't been granted access.

https://twitter.com/statues/friends/cmakice.xml
https://twitter.com/statuses/followers/cmakice.xml

I don't have any problems getting this list. Once upon a time, I could
get one list but not the other, but that behavior seems to have been
opened up.

BTW, if no authentication is used on the request, the /followers/ids
and /statuses/followers returns a "Could not authenticate you." error.
For public accounts, /friends/ids does not require authentication and
will return the full list of IDs. For both public and private
accounts, /statuses/friends will return useful information.

Could someone explain the reasoning for these discrepancies?