[twitter-dev] Re: Hoping to clear my confusion about Twitter's announcement

[Tobias C. Jensen]

Very important questions, in my opinion, Tim. Looking forward to read
the clarifications.

Also, I don't seem to be able to find the original post by Ryan at
http://groups.google.com/group/twitter-api-announce

Does the link provided in the following tweet work for you guys?
https://twitter.com/#!/twitterapi/status/46304795866312704

Regards,
Tobias

On 15 Mar., 00:39, Tim Haines  wrote:
> Hey Ryan, Raffi, Taylor, Matt, and other Twitter staff,
>
> I've been confused about Ryan's post, and some of the follow up comments.
>  Some of the tweets I've seen since have been reassuring that my original
> interpretation of Ryan's email was inaccurate.  I thought you were saying
> 'no new client apps allowed', and I'm very relieved to hear I was wrong.
>
> I wanted to follow up with a few more questions and comments to make sure I
> understand Twitter's message correctly.  Twitter staff, if I have anything
> wrong here, please correct, or rephrase to be more accurate.
>
> Please excuse the length of this and the number of questions at the end of
> the email. Changing the API rules is changing the contract we have, and as
> I'm so invested in the ecosystem (my family's livelihood now depends on it),
> I want to be completely sure I understand what the new contract is that
> you're introducing.
>
> First off, some background.  Ryan said that developers are welcome to
> develop things that Twitter has said developers shouldn't be doing -
> "shouldn't" is guidance only, and not a prohibition.  Twitter will
> only interfere with applications if they break the API TOS. Tweets related
> to this (clicking on the last one and viewing the thread is easiest):
>
>    -https://twitter.com/joestump/status/47094929796759552
>    -https://twitter.com/rsarver/status/47095346899320832
>    -https://twitter.com/timhaines/status/47096379306291203
>    -https://twitter.com/rsarver/status/47096690288771072
>    -https://twitter.com/timhaines/status/47097497679708160
>    -https://twitter.com/rsarver/status/47097681591545856
>
> Furthermore, the most disturbing paragraph for me in Ryan's announcement:
>
> If you are an existing developer of client apps, you can continue to serve
>
> > your user base, but we will be holding you to high standards to ensure you
> > do not violate users’ privacy, that you provide consistency in the user
> > experience, and that you rigorously adhere to all areas of our Terms of
> > Service.
>
> This and the preceding paragraph together could be interpreted to mean that
> developers "aren't allowed" to build NEW client apps.  According to the
> tweets above, they are allowed, but Twitter is advising developers that they
> should focus their efforts elsewhere.  Likewise, existing applications "will
> be held to high standards".  As Ryan clarified in his tweets, these
> applications won't be interfered with unless they break the API TOS.  So all
> told, the email itself doesn't introduce anything new rulewise; you can do
> anything you want within the API TOS, but if you break the API TOS you'll
> potentially have your app revoked.  No change here.
>
> You won't be applying a subjective 'high standard' or 'high bar' and
> revoking an app unless it breaks the API TOS. Phew!  You are remaining an
> open API, within the confines of your stated rules.
>
> However, the email was accompanied with changes to the API TOS (of course
> Twitter can make any change to the API TOS at any time - including adding
> further restrictions in the future).  This round of changes included amongst
> other things, the addition of section I.5, adding restrictions to what
> client applications may and may not do.  For the purposes of this email, I'm
> considering my own application, Favstar, a client.  While it doesn't allow
> you to tweet at the moment, it will in the coming months, therefore meeting
> the criteria specified in the API TOS for Favstar to be regarded as a
> client.
>
> My questions:
>
> 5a: Your Client must use the Twitter API as the sole source for features
>
> > that are substantially similar to functionality offered by Twitter. Some
> > examples include trending topics, who to follow, and suggested user lists.
>
> *Question re 5a:*  Favstar has for a long time offered 'suggested user
> lists' in the form of it's popular page 
> (http://favstar.fm/popular-on-twitter-by-tweets-with-50-favorites)  Is this
> feature now in breach of the API TOS?  If it is in breach, does this place
> Favstar in breach until the feature is removed?
>
> *Question re 5a:*  If I was to add features that surfaced 'popular themes'
> found in tweets that Favstar collects, would this be considered similar to
> Trending topics, and put Favstar in breach of the API TOS?
>
> *Question re 5a:* Favstar users can buy 'bonus features', and receive a slew
> of extra features.  I've recently started promoting these users on the site.
> If follow buttons were added to their avatar's in the places of promotion,
> could this be considered as a 'who to foll

[twitter-dev] Short survey! Regarding our social media vs coding

[Dwi Sasongko Supriyadi]

Hello All,

I would like to ask a little time from all of you to join a survey here:

http://www.surveymonkey.com/s/Z9RPFDD

The idea is to collect answer of this question: Can you code and
tweet/update status at the same time?

Thanks in advance,

-- 
Good software can't be measured by `wc -l software.c`

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

[twitter-dev] Re: consistency and ecosystem opportunities

[Rob Aldred]

I agree, this is very short sighted of them to assume theirs some how 
better, or all people need.
I hate the Mac official client, they've bought Tweetie and made it worse, 
they've removed features and added a raft of bugs.
I use the original Tweetie on Mac and Seesmic on my Android.

Thankfully there are some decent programmers out there.

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

Re: [twitter-dev] Re: get user email address

[Andrey Kostromin]

Ok, how I can ask email using php? Has twitter api for it?
Scott Wilcox  писал(а) в своём письме Tue, 15 Mar 2011 01:19:40 
+0200:


Hello,

As Taylor has just said to you, it is impossible to get a users email address 
from the Twitter REST API. If you want a users email address you will have to 
explicitly ask them for it yourself.

Scott.

On 14 Mar 2011, at 22:32, Andrey Kostromin wrote:


I make site registration with twitter. How I can ask email? I have
twitter access token to get more info (user_id, name,
screen_name, ...) but not email

On Feb 23, 5:19 pm, Taylor Singletary 
wrote:

Hi Amrish,

User email addresses are not returned in the Twitter API. If you would like
a user's email address, you'll have to ask them for it in your application.

Taylor

On Wed, Feb 23, 2011 at 4:09 AM, amrish.prajapati <



amrish.prajap...@gmail.com> wrote:

hello,



I would like to get all details including email address of user.
When I make http request by parameter screen_name



http://api.twitter.com/1/users/show.xml?screen_name=



I am not able to get email address of that user.



How can I able to get it ?



Please help for same.



Thanks in advance.





--
Andrey Kostromin

--
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] Hoping to clear my confusion about Twitter's announcement

[Ryan Sarver]

Tim, thanks for taking the time to write up such an epic email. Give me some
time to parse through it so I can follow up on all the points.

Also, not sure what happened to the thread on api-announce, but I reposted
linking to this thread so people can still find it.

Best, Ryan

--
Ryan Sarver
@rsarver 



On Mon, Mar 14, 2011 at 11:39 PM, Tim Haines  wrote:

> Hey Ryan, Raffi, Taylor, Matt, and other Twitter staff,
>
> I've been confused about Ryan's post, and some of the follow up comments.
>  Some of the tweets I've seen since have been reassuring that my original
> interpretation of Ryan's email was inaccurate.  I thought you were saying
> 'no new client apps allowed', and I'm very relieved to hear I was wrong.
>
> I wanted to follow up with a few more questions and comments to make sure I
> understand Twitter's message correctly.  Twitter staff, if I have anything
> wrong here, please correct, or rephrase to be more accurate.
>
> Please excuse the length of this and the number of questions at the end of
> the email. Changing the API rules is changing the contract we have, and as
> I'm so invested in the ecosystem (my family's livelihood now depends on it),
> I want to be completely sure I understand what the new contract is that
> you're introducing.
>
> First off, some background.  Ryan said that developers are welcome to
> develop things that Twitter has said developers shouldn't be doing -
> "shouldn't" is guidance only, and not a prohibition.  Twitter will
> only interfere with applications if they break the API TOS. Tweets related
> to this (clicking on the last one and viewing the thread is easiest):
>
>- https://twitter.com/joestump/status/47094929796759552
>- https://twitter.com/rsarver/status/47095346899320832
>- https://twitter.com/timhaines/status/47096379306291203
>- https://twitter.com/rsarver/status/47096690288771072
>- https://twitter.com/timhaines/status/47097497679708160
>- https://twitter.com/rsarver/status/47097681591545856
>
>
> Furthermore, the most disturbing paragraph for me in Ryan's announcement:
>
> If you are an existing developer of client apps, you can continue to serve
>> your user base, but we will be holding you to high standards to ensure you
>> do not violate users’ privacy, that you provide consistency in the user
>> experience, and that you rigorously adhere to all areas of our Terms of
>> Service.
>
>
> This and the preceding paragraph together could be interpreted to mean that
> developers "aren't allowed" to build NEW client apps.  According to the
> tweets above, they are allowed, but Twitter is advising developers that they
> should focus their efforts elsewhere.  Likewise, existing applications "will
> be held to high standards".  As Ryan clarified in his tweets, these
> applications won't be interfered with unless they break the API TOS.  So all
> told, the email itself doesn't introduce anything new rulewise; you can do
> anything you want within the API TOS, but if you break the API TOS you'll
> potentially have your app revoked.  No change here.
>
> You won't be applying a subjective 'high standard' or 'high bar' and
> revoking an app unless it breaks the API TOS. Phew!  You are remaining an
> open API, within the confines of your stated rules.
>
> However, the email was accompanied with changes to the API TOS (of course
> Twitter can make any change to the API TOS at any time - including adding
> further restrictions in the future).  This round of changes included amongst
> other things, the addition of section I.5, adding restrictions to what
> client applications may and may not do.  For the purposes of this email, I'm
> considering my own application, Favstar, a client.  While it doesn't allow
> you to tweet at the moment, it will in the coming months, therefore meeting
> the criteria specified in the API TOS for Favstar to be regarded as a
> client.
>
>
> My questions:
>
>
> 5a: Your Client must use the Twitter API as the sole source for features
>> that are substantially similar to functionality offered by Twitter. Some
>> examples include trending topics, who to follow, and suggested user lists.
>
>
> *Question re 5a:*  Favstar has for a long time offered 'suggested user
> lists' in the form of it's popular page (
> http://favstar.fm/popular-on-twitter-by-tweets-with-50-favorites)  Is this
> feature now in breach of the API TOS?  If it is in breach, does this place
> Favstar in breach until the feature is removed?
>
> *Question re 5a:*  If I was to add features that surfaced 'popular themes'
> found in tweets that Favstar collects, would this be considered similar to
> Trending topics, and put Favstar in breach of the API TOS?
>
> *Question re 5a:* Favstar users can buy 'bonus features', and receive a
> slew of extra features.  I've recently started promoting these users on the
> site. If follow buttons were added to their avatar's in the places of
> promotion, could this be considered as a 'who t

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

[manusis]

The streaming API mentions about different access roles but does not
indicate how one could apply for them.

"The default access level allows up to 400 track keywords, 5,000
follow userids and 25 0.1-360 degree location boxes. Increased access
levels allow 100,000 follow userids (“shadow” role), 400,000 follow
userids (“birddog” role), 10,000 track keywords (“restricted track”
role), 200,000 track keywords (“partner track” role), and 200 0.1-360
degree location boxes (“locRestricted” role). Increased track access
levels also pass a higher proportion of statuses before limiting the
stream."

For our product, we need "shadow" and "partner track" access roles.
Could somebody shed any light on how one could apply for the increased
access levels?

Thanks,
Rajiv

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

[twitter-dev] Cannot find tweets from certain accounts

[Moosar]

Hi guys!

I'm wondering how it's possible that I can find tweets from some
Twitter accounts and cannot find tweets from other Twitter accounts.
Searching through the Twitter site, search.twitter.com and/or the API
all give the same results.

Examples of accounts that can find Tweets:
- http://search.twitter.com/search.atom?q=from%3AMrHeinLein
- http://search.twitter.com/search.atom?q=from%3ASreblov

But these don't give results:
- http://search.twitter.com/search.atom?q=from%3ABlexIT
- http://search.twitter.com/search.atom?q=from%3ASkodaChauffeur
- http://search.twitter.com/search.atom?q=from%3ASkodaChauffeur1

Really puzzled by this, since the non-working accounts don't have any
privacy option enabled or anything. What am I missing here?

-- 
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] Reg POST direct_messages/new API

[vimal]

Hi

Am a developer working for a social networking website company, Am
trying to access the API's provided by twitter.

I have a problem in accessing the API method direct_messages/new which
is under Direct Messages Resources ,
I couldn't get the xml file or data if i provide multiple parameters
like screenname = "value",text="description"

Could  you help me about this API on how to pass multiple required
parameters in the querystring.

Am accessing the API only after getting authentication from Twitter
for the user,

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

Re: [twitter-dev] Re: get user email address

[Emil Tullstedt]

MySQL+HTML forms+GET?
--
Emil "sakjur" Tullstedt
~~



2011/3/15 Andrey Kostromin 

> Ok, how I can ask email using php? Has twitter api for it?
> Scott Wilcox  писал(а) в своём письме Tue, 15 Mar 2011
> 01:19:40 +0200:
>
>
> Hello,
>>
>> As Taylor has just said to you, it is impossible to get a users email
>> address from the Twitter REST API. If you want a users email address you
>> will have to explicitly ask them for it yourself.
>>
>> Scott.
>>
>> On 14 Mar 2011, at 22:32, Andrey Kostromin wrote:
>>
>> I make site registration with twitter. How I can ask email? I have
>>> twitter access token to get more info (user_id, name,
>>> screen_name, ...) but not email
>>>
>>> On Feb 23, 5:19 pm, Taylor Singletary 
>>> wrote:
>>>
 Hi Amrish,

 User email addresses are not returned in the Twitter API. If you would
 like
 a user's email address, you'll have to ask them for it in your
 application.

 Taylor

 On Wed, Feb 23, 2011 at 4:09 AM, amrish.prajapati <



 amrish.prajap...@gmail.com> wrote:

> hello,
>

 I would like to get all details including email address of user.
> When I make http request by parameter screen_name
>

 http://api.twitter.com/1/users/show.xml?screen_name=
>

 I am not able to get email address of that user.
>

 How can I able to get it ?
>

 Please help for same.
>

 Thanks in advance.
>

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

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

[twitter-dev] Re: Signature generation issue

[lappynet]

Thanks for everyone's help on this. I think that I now have this
working (twitter documentation values match up).

My problem now is that although I'm confident of my algorithm, twitter
is always responding 401. I've debugged my network service and the
message being returned is Incorrect Signature. I do not understand how
this can be... :S

On Mar 15, 6:03 am, kamesh SmartDude 
wrote:
> Hai lappynet,
>
> I Used GET method to retrive the Request Token And I Avoided the OAuth
> Callback, because it was registered when i registered my app.
>
> Below is the method how i am  doing.
>
>  ** SignatureBase String is *
>
> GET&https%3A%2F%2Fapi.twitter.com
> %2Foauth%2Frequest_token&oauth_consumer_key%3D
> %26oauth_nonce%3DydBxFJKdzK%26oauth_signature_method%3DHMAC-SHA1%26oauth_ti 
> mestamp%3D1300167727%26oauth_version%3D1.0
>
> Signature Key U are appending "&" and it is correct.
>
> i am adding the oauth header like below
>
> OAuth realm="Twitter API", oauth_consumer_key=,
> oauth_nonce=ydBxFJKdzK, oauth_signature=89%2BSoLKBdE%2FeHN5PFRxNl3G7tNo%3D,
> oauth_signature_method=HMAC-SHA1, oauth_timestamp=1300167727,
> oauth_version=1.0
>
> I think u might have some problem with generating the signature.
>
> Try this,
> //kamesh
>
>
>
>
>
>
>
> On Mon, Mar 14, 2011 at 8:16 PM, lappynet  wrote:
> > cURL... I've heard about this, but I don't really know about it. Is
> > there a windows version as I don't have access to other OSs at work
> > (*sigh*)?
>
> > On Mar 14, 2:18 pm, Taylor Singletary 
> > wrote:
> > > Hi Georgina,
>
> > > Everything appears correct with your base string for this step.
>
> > > Are you performing this operation through a HTTP proxy of any kind? Have
> > you
> > > tried producing a valid OAuth header and executed it in curl (without
> > having
> > > "executed it" in C# first)? I'm not familiar with C#'s HTTP request
> > > libraries and the configuration options available to you in it.
>
> > > We were having an issue with occasionally hanging connections recently
> > and
> > > it's possible that it may be related -- but if that's the case, you
> > > shouldn't have it occur to you every time -- it would be one out of X
> > times.
>
> > > I'm curious where the connection is hanging -- while you are sending HTTP
> > > request headers or when your HTTP client is awaiting a response?
>
> > > Thanks,
> > > Taylor
>
> > > On Mon, Mar 14, 2011 at 7:02 AM, lappynet 
> > wrote:
> > > > Hi
>
> > > > I'm using C#.NET to produce an oob client. I've fallen at the first
> > > > hurdle though as I'm failing to make the token request.
>
> > > > I've gone through many iterations, and am no longer receiving a 417,
> > > > 404, or 401. This is very positive! Now my application hangs whilst
> > > > waiting for a response from twitter. (I left it running for an hour
> > > > over lunch and still nothing happened, and the code didn't appear to
> > > > want to step through.)
>
> > > > I've tried with the values detailed in the documentation to have a
> > > > look at the variables that have been produced from them in my
> > > > algorithm. I think that I've traced it down to being the way I
> > > > generate the signature string:
>
> > > > string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
> > > > HMACSHA1 hasher = new HMACSHA1(new
> > > > ASCIIEncoding().GetBytes(signingKey));
> > > > string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
> > > > ASCIIEncoding().GetBytes(baseString)));
>
> > > > My base string is:
>
> > > > POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > > > %2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
> > > > %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
> > > > %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0
>
> > > > Any pointers as to where I may be going wrong?
>
> > > > Thanks in advance
> > > > Georgina
>
> > > > --
> > > > Twitter developer documentation and resources:
> >http://dev.twitter.com/doc
> > > > API updates via Twitter:http://twitter.com/twitterapi
> > > > Issues/Enhancements Tracker:
> > > >http://code.google.com/p/twitter-api/issues/list
> > > > Change your membership to this group:
> > > >http://groups.google.com/group/twitter-development-talk
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

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

Re: [twitter-dev] Reg POST direct_messages/new API

[Taylor Singletary]

Hi Vimal,

Write actions like direct_messages/new should be used with an HTTP POST and
the parameters you want to send to the resource should be sent in the POST
body. Additionally, there are business logic rules with direct messages --
one such rule is that the recipient of the message needs to be following the
sender.

Here's a little on how the request would work with OAuth, if I was sending
the message "Hello" to @episod:

Signature base string example (used to compute your oauth_signature)
POST&https%3A%2F%2Fapi.twitter.com
%2F1%2Fdirect_messages%2Fnew.xml&oauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DIEBMCsz226ngPNe2vzZkkHIm3moBB64WfXP1uj0Jjo%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1300199092%26oauth_token%3D119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26screen_name%3Depisod%26text%3DHello

POST body
text=Hello&screen_name=episod

Authorization HTTP header:
OAuth oauth_nonce="IEBMCsz226ngPNe2vzZkkHIm3moBB64WfXP1uj0Jjo",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1300199092",
oauth_consumer_key="ri8JxYK2ddwSV5xIUfNNvQ",
oauth_token="119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8",
oauth_signature="3Qa0Med9nscjWdpprRKDCfSbuoE%3D", oauth_version="1.0"

After execution, I get a representation of the sent DM back in XML:


  2613595065
  119476949
  Hello
  819797
  Tue Mar 15 14:24:52 + 2011
  oauth_dancer
  episod
  
   
  
   .


Taylor

@episod  - Taylor Singletary - Twitter Developer
Advocate


On Tue, Mar 15, 2011 at 5:45 AM, vimal wrote:

> Hi
>
> Am a developer working for a social networking website company, Am
> trying to access the API's provided by twitter.
>
> I have a problem in accessing the API method direct_messages/new which
> is under Direct Messages Resources ,
> I couldn't get the xml file or data if i provide multiple parameters
> like screenname = "value",text="description"
>
> Could  you help me about this API on how to pass multiple required
> parameters in the querystring.
>
> Am accessing the API only after getting authentication from Twitter
> for the user,
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

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

Re: [twitter-dev] Cannot find tweets from certain accounts

[Taylor Singletary]

Hi Moosar,

There's a good help desk guide in our support center on this topic:
http://support.twitter.com/groups/32-something-s-not-working/topics/118-search/articles/66018-my-tweets-or-hashtags-are-missing-from-search-known-issue

Taylor

On Tue, Mar 15, 2011 at 4:00 AM, Moosar  wrote:

> Hi guys!
>
> I'm wondering how it's possible that I can find tweets from some
> Twitter accounts and cannot find tweets from other Twitter accounts.
> Searching through the Twitter site, search.twitter.com and/or the API
> all give the same results.
>
> Examples of accounts that can find Tweets:
> - http://search.twitter.com/search.atom?q=from%3AMrHeinLein
> - http://search.twitter.com/search.atom?q=from%3ASreblov
>
> But these don't give results:
> - http://search.twitter.com/search.atom?q=from%3ABlexIT
> - http://search.twitter.com/search.atom?q=from%3ASkodaChauffeur
> - http://search.twitter.com/search.atom?q=from%3ASkodaChauffeur1
>
> Really puzzled by this, since the non-working accounts don't have any
> privacy option enabled or anything. What am I missing here?
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

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

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

[Augusto Santos]

I think the answer is you never will.
This kind of benefit might follow the same rules that whitelist, that will
no longer be supported just as the thread below said.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84/688b8bfe26a5c178

On Tue, Mar 15, 2011 at 6:58 AM, manusis  wrote:

> The streaming API mentions about different access roles but does not
> indicate how one could apply for them.
>
> "The default access level allows up to 400 track keywords, 5,000
> follow userids and 25 0.1-360 degree location boxes. Increased access
> levels allow 100,000 follow userids (“shadow” role), 400,000 follow
> userids (“birddog” role), 10,000 track keywords (“restricted track”
> role), 200,000 track keywords (“partner track” role), and 200 0.1-360
> degree location boxes (“locRestricted” role). Increased track access
> levels also pass a higher proportion of statuses before limiting the
> stream."
>
> For our product, we need "shadow" and "partner track" access roles.
> Could somebody shed any light on how one could apply for the increased
> access levels?
>
> Thanks,
> Rajiv
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>



-- 
氣

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

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

[manusis]

Thanks Augusto.

But the same thread indicates that tools like Streaming API will
replace whitelisting. So it does not make sense for me for Streaming
API to put under the same umbrella as whitelisting.

"Since then, we've added new, more efficient tools for developers,
including lookups, ID lists, authentication and the Streaming API.
Instead of whitelisting, developers can use these tools to create
applications and integrate with the Twitter platform."





On Mar 15, 7:41 pm, Augusto Santos  wrote:
> I think the answer is you never will.
> This kind of benefit might follow the same rules that whitelist, that will
> no longer be supported just as the thread below 
> said.http://groups.google.com/group/twitter-development-talk/browse_thread...
>
>
>
>
>
>
>
>
>
> On Tue, Mar 15, 2011 at 6:58 AM, manusis  wrote:
> > The streaming API mentions about different access roles but does not
> > indicate how one could apply for them.
>
> > "The default access level allows up to 400 track keywords, 5,000
> > follow userids and 25 0.1-360 degree location boxes. Increased access
> > levels allow 100,000 follow userids (“shadow” role), 400,000 follow
> > userids (“birddog” role), 10,000 track keywords (“restricted track”
> > role), 200,000 track keywords (“partner track” role), and 200 0.1-360
> > degree location boxes (“locRestricted” role). Increased track access
> > levels also pass a higher proportion of statuses before limiting the
> > stream."
>
> > For our product, we need "shadow" and "partner track" access roles.
> > Could somebody shed any light on how one could apply for the increased
> > access levels?
>
> > Thanks,
> > Rajiv
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk
>
> --
> 氣

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

[twitter-dev] Re: consistency and ecosystem opportunities

[Dewald Pretorius]

Here's one of the best and most thoughtful articles yet on this latest
ecosystem bomb:

http://radar.oreilly.com/2011/03/twitter-developers.html

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

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

[hax0rsteve]

>From that same post : 
>http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84/688b8bfe26a5c178

> Developers 
> interested in elevated access to the Twitter stream for the purpose of 
> research or analytics can contact our partner Gnip for more 
> information.


>From http://gnip.com/


> Gnip and Twitter have partnered to bring more Twitter feeds to Gnip 
> customers. Check out Power Track for 100% guaranteed coverage firehose 
> filtering and all commercial Twitter data, only from Gnip.



>From http://gnip.com/twitter/power-track


>   • The only feed of its kind: Twitter firehose filtering with 100% 
> coverage guaranteed
>   • Boolean operators, unwound URLs, and matching within unwound URLs 
> supported
>   • Keyword, username, and location filtering supported
>   • Unlimited capacity: no restrictions on filter parameters or results 
> volume - Premium Feed
>   • Pay for what you get - pricing depends on Tweet volume delivered - 
> Premium Feed
>   • Contact i...@gnip.com for more information - Premium Feed




HTH



On 15 Mar 2011, at 15:04, manusis wrote:

> Thanks Augusto.
> 
> But the same thread indicates that tools like Streaming API will
> replace whitelisting. So it does not make sense for me for Streaming
> API to put under the same umbrella as whitelisting.
> 
> "Since then, we've added new, more efficient tools for developers,
> including lookups, ID lists, authentication and the Streaming API.
> Instead of whitelisting, developers can use these tools to create
> applications and integrate with the Twitter platform."
> 
> 
> 
> 
> 
> On Mar 15, 7:41 pm, Augusto Santos  wrote:
>> I think the answer is you never will.
>> This kind of benefit might follow the same rules that whitelist, that will
>> no longer be supported just as the thread below 
>> said.http://groups.google.com/group/twitter-development-talk/browse_thread...
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Tue, Mar 15, 2011 at 6:58 AM, manusis  wrote:
>>> The streaming API mentions about different access roles but does not
>>> indicate how one could apply for them.
>> 
>>> "The default access level allows up to 400 track keywords, 5,000
>>> follow userids and 25 0.1-360 degree location boxes. Increased access
>>> levels allow 100,000 follow userids (“shadow” role), 400,000 follow
>>> userids (“birddog” role), 10,000 track keywords (“restricted track”
>>> role), 200,000 track keywords (“partner track” role), and 200 0.1-360
>>> degree location boxes (“locRestricted” role). Increased track access
>>> levels also pass a higher proportion of statuses before limiting the
>>> stream."
>> 
>>> For our product, we need "shadow" and "partner track" access roles.
>>> Could somebody shed any light on how one could apply for the increased
>>> access levels?
>> 
>>> Thanks,
>>> Rajiv
>> 
>>> --
>>> Twitter developer documentation and resources:http://dev.twitter.com/doc
>>> API updates via Twitter:http://twitter.com/twitterapi
>>> Issues/Enhancements Tracker:
>>> http://code.google.com/p/twitter-api/issues/list
>>> Change your membership to this group:
>>> http://groups.google.com/group/twitter-development-talk
>> 
>> --
>> 氣
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk

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

[twitter-dev] Re: Cannot find tweets from certain accounts

[Moosar]

Hi Taylor,

thank you very much for your quick(!) reply.

I've read through all the information. The "Your account is new, or
you recently changed your username" could be my problem here, but only
on the SkodaChauffeur account(s) since those have been created
yesterday. The consequence of this, "It can take a few days for new
and updated accounts to be indexed by search.", could pose a problem
for the Skoda project I'm working on, since the deadline is in 3 days.
Let's hope the index is updated in time for these accounts (also have
SkodaChauffeur2, 3 and 4 accounts :-)).

Although, the other search I've linked (http://www.google.com/url?
sa=D&q=http://search.twitter.com/search.atom%3Fq%3Dfrom%253ABlexIT)
isn't really new. My own account (http://www.google.com/url?
sa=D&q=http://search.twitter.com/search.atom%3Fq%3Dfrom
%253AWouterHendriks) also exists for quite some time, yet I can't find
any tweets from these accounts. This could be due to "You are being
filtered out of search due to a quality issue", but this seems
unlikely, since both accounts aren't that active, let alone spammy.

Anyway, I could care less whether those last two accounts will work in
time or even at all, it's the Skoda accounts which I'm interested in.
I would appreciate any suggestions to get Tweets from those accounts
in the search results faster. :-)

Cheers,
Moosar




On Mar 15, 3:34 pm, Taylor Singletary 
wrote:
> Hi Moosar,
>
> There's a good help desk guide in our support center on this 
> topic:http://support.twitter.com/groups/32-something-s-not-working/topics/1...
>
> Taylor
>
> On Tue, Mar 15, 2011 at 4:00 AM, Moosar  wrote:
> > Hi guys!
>
> > I'm wondering how it's possible that I can find tweets from some
> > Twitter accounts and cannot find tweets from other Twitter accounts.
> > Searching through the Twitter site, search.twitter.com and/or the API
> > all give the same results.
>
> > Examples of accounts that can find Tweets:
> > -http://search.twitter.com/search.atom?q=from%3AMrHeinLein
> > -http://search.twitter.com/search.atom?q=from%3ASreblov
>
> > But these don't give results:
> > -http://search.twitter.com/search.atom?q=from%3ABlexIT
> > -http://search.twitter.com/search.atom?q=from%3ASkodaChauffeur
> > -http://search.twitter.com/search.atom?q=from%3ASkodaChauffeur1
>
> > Really puzzled by this, since the non-working accounts don't have any
> > privacy option enabled or anything. What am I missing here?
>
> > --
> > 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] gdata-objectivec-client to authenticate and update twitter status

[Israel Pasos]

This is my first time with GData and I'm trying to use it with OAuth
to connect to Twitter and post status updates.

Here's what I did:

1. I'm able to login using Gdata and OAuth to Twitter.
2. I save [mAuth token] in NSUserDefaults.
3. I changed the URL and set the HTTPMethod to POST in my app's
mainViewController:

NSString *urlStr;
 if ([self isGoogleSegmentSelected]) {
   // Google Contacts feed
   urlStr = @"http://www.google.com/m8/feeds/contacts/default/thin";;
 } else {
   // Twitter update status
 urlStr = @"https://api.twitter.com/1/statuses/update.xml";;
 }

 NSURL *url = [NSURL URLWithString:urlStr];
 NSMutableURLRequest *request = [NSMutableURLRequest
requestWithURL:url];
   [request setHTTPMethod:@"POST"];
   [mAuth authorizeRequest:request];



The only thing I'm missing is how to add the status parameter to the
request. I have no idea how to do this. Could anyone help me?



2011-03-15 10:51:32.793 OAuthSampleiPhone[73515:207] API response: 

 /1/statuses/update.xml
 Client must provide a 'status' parameter with a value.



I have tried this:

NSMutableURLRequest *request = [NSMutableURLRequest
requestWithURL:url];
[request setHTTPMethod:@"POST"];
NSString *requestBody = @"Request!";
//[request setValue:@"application/x-www-form-urlencoded"
forHTTPHeaderField:@"Content-Type"];
[request setHTTPBody:[requestBody
dataUsingEncoding:NSASCIIStringEncoding allowLossyConversion:YES]];
//[request setValue:[NSString stringWithFormat:@"%d",[requestBody
length]] forHTTPHeaderField:@"Content-Length"];
[mAuth authorizeRequest:request];

But I get this error:

2011-03-15 11:40:42.023 OAuthSampleiPhone[74083:207] API response: 

  /1/statuses/update.xml
  Incorrect signature



Thanks in advance,

Israel

-- 
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] gdata-objectivec-client to authenticate and update twitter status

[hax0rsteve]

Israel,

Assuming that everything else is correct (I have no experience with GData)
your post body should be something more like this : 

NSString *requestBody = @"status=somestatus";

Noting that the part after the '=' will need to be URL encoded as
per the docs : http://dev.twitter.com/pages/auth#auth-request

Otherwise twitter will not know what you are trying to do.

You should also probably do the following rather than using NSASCII :

[request setHTTPBody:[requestBody dataUsingEncoding:NSUTF8StringEncoding]]


HTH


On 15 Mar 2011, at 19:17, Israel Pasos wrote:

> This is my first time with GData and I'm trying to use it with OAuth
> to connect to Twitter and post status updates.
> 
> Here's what I did:
> 
> 1. I'm able to login using Gdata and OAuth to Twitter.
> 2. I save [mAuth token] in NSUserDefaults.
> 3. I changed the URL and set the HTTPMethod to POST in my app's
> mainViewController:
> 
> NSString *urlStr;
> if ([self isGoogleSegmentSelected]) {
>   // Google Contacts feed
>   urlStr = @"http://www.google.com/m8/feeds/contacts/default/thin";;
> } else {
>   // Twitter update status
> urlStr = @"https://api.twitter.com/1/statuses/update.xml";;
> }
> 
> NSURL *url = [NSURL URLWithString:urlStr];
> NSMutableURLRequest *request = [NSMutableURLRequest
> requestWithURL:url];
>   [request setHTTPMethod:@"POST"];
>   [mAuth authorizeRequest:request];
> 
> 
> 
> The only thing I'm missing is how to add the status parameter to the
> request. I have no idea how to do this. Could anyone help me?
> 
> 
> 
> 2011-03-15 10:51:32.793 OAuthSampleiPhone[73515:207] API response:  xml version="1.0" encoding="UTF-8"?>
> 
> /1/statuses/update.xml
> Client must provide a 'status' parameter with a value. error>
> 
> 
> 
> I have tried this:
> 
> NSMutableURLRequest *request = [NSMutableURLRequest
> requestWithURL:url];
>[request setHTTPMethod:@"POST"];
>NSString *requestBody = @"Request!";
>//[request setValue:@"application/x-www-form-urlencoded"
> forHTTPHeaderField:@"Content-Type"];
>[request setHTTPBody:[requestBody
> dataUsingEncoding:NSASCIIStringEncoding allowLossyConversion:YES]];
>//[request setValue:[NSString stringWithFormat:@"%d",[requestBody
> length]] forHTTPHeaderField:@"Content-Length"];
>[mAuth authorizeRequest:request];
> 
> But I get this error:
> 
> 2011-03-15 11:40:42.023 OAuthSampleiPhone[74083:207] API response:  xml version="1.0" encoding="UTF-8"?>
> 
>  /1/statuses/update.xml
>  Incorrect signature
> 
> 
> 
> Thanks in advance,
> 
> Israel
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk

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

Re: [twitter-dev] gdata-objectivec-client to authenticate and update twitter status

[Israel Pasos]

HTH,

It worked! I can't begin to thank you enough!

Sincerely,

Israel

On 15/03/2011, at 12:55, hax0rsteve wrote:

> 
> 
> Israel,
> 
> Assuming that everything else is correct (I have no experience with GData)
> your post body should be something more like this : 
> 
> NSString *requestBody = @"status=somestatus";
> 
> Noting that the part after the '=' will need to be URL encoded as
> per the docs : http://dev.twitter.com/pages/auth#auth-request
> 
> Otherwise twitter will not know what you are trying to do.
> 
> You should also probably do the following rather than using NSASCII :
> 
> [request setHTTPBody:[requestBody dataUsingEncoding:NSUTF8StringEncoding]]
> 
> 
> HTH
> 
> 
> On 15 Mar 2011, at 19:17, Israel Pasos wrote:
> 
>> This is my first time with GData and I'm trying to use it with OAuth
>> to connect to Twitter and post status updates.
>> 
>> Here's what I did:
>> 
>> 1. I'm able to login using Gdata and OAuth to Twitter.
>> 2. I save [mAuth token] in NSUserDefaults.
>> 3. I changed the URL and set the HTTPMethod to POST in my app's
>> mainViewController:
>> 
>> NSString *urlStr;
>> if ([self isGoogleSegmentSelected]) {
>>  // Google Contacts feed
>>  urlStr = @"http://www.google.com/m8/feeds/contacts/default/thin";;
>> } else {
>>  // Twitter update status
>>urlStr = @"https://api.twitter.com/1/statuses/update.xml";;
>> }
>> 
>> NSURL *url = [NSURL URLWithString:urlStr];
>> NSMutableURLRequest *request = [NSMutableURLRequest
>> requestWithURL:url];
>>  [request setHTTPMethod:@"POST"];
>>  [mAuth authorizeRequest:request];
>> 
>> 
>> 
>> The only thing I'm missing is how to add the status parameter to the
>> request. I have no idea how to do this. Could anyone help me?
>> 
>> 
>> 
>> 2011-03-15 10:51:32.793 OAuthSampleiPhone[73515:207] API response: > xml version="1.0" encoding="UTF-8"?>
>> 
>> /1/statuses/update.xml
>> Client must provide a 'status' parameter with a value.> error>
>> 
>> 
>> 
>> I have tried this:
>> 
>> NSMutableURLRequest *request = [NSMutableURLRequest
>> requestWithURL:url];
>>   [request setHTTPMethod:@"POST"];
>>   NSString *requestBody = @"Request!";
>>   //[request setValue:@"application/x-www-form-urlencoded"
>> forHTTPHeaderField:@"Content-Type"];
>>   [request setHTTPBody:[requestBody
>> dataUsingEncoding:NSASCIIStringEncoding allowLossyConversion:YES]];
>>   //[request setValue:[NSString stringWithFormat:@"%d",[requestBody
>> length]] forHTTPHeaderField:@"Content-Length"];
>>   [mAuth authorizeRequest:request];
>> 
>> But I get this error:
>> 
>> 2011-03-15 11:40:42.023 OAuthSampleiPhone[74083:207] API response: > xml version="1.0" encoding="UTF-8"?>
>> 
>> /1/statuses/update.xml
>> Incorrect signature
>> 
>> 
>> 
>> Thanks in advance,
>> 
>> Israel
>> 
>> -- 
>> 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] Twitter group API

[Richard]

Does anyone know if there is program available to create several
groups using one Twitter account and allowing you to message each of
those groups individually?

For example -

Twitter.com/username
Group 1 (100 followers)
Group 2 (56 followers)
Group 3 (77 followers)

I would like to send separate messages to each of those groups.
Please let me know if you know of any way to do this via API or a 3rd
party program.  Thank you.

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

Re: [twitter-dev] Twitter group API

[Tim Haines]

No, there's not.

On Tue, Mar 15, 2011 at 1:03 PM, Richard  wrote:

> Does anyone know if there is program available to create several
> groups using one Twitter account and allowing you to message each of
> those groups individually?
>
> For example -
>
> Twitter.com/username
>Group 1 (100 followers)
>Group 2 (56 followers)
>Group 3 (77 followers)
>
> I would like to send separate messages to each of those groups.
> Please let me know if you know of any way to do this via API or a 3rd
> party program.  Thank you.
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

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

[twitter-dev] Re: Source Parameter Doesn't Change

[Shannon Whitley]

My source parameter finally changed on its own.  I'm not sure what
triggered the change, but it's correct now.

Thanks!

On Mar 8, 6:02 pm, Shannon Whitley  wrote:
> I had previously setup a Twitter application and used it under one
> name.  I've recently changed the name and updated the Twitter app
> settings (trying bothhttp://twitter.com/oauthandhttp://dev.twitter.com/apps).
>
> Everything is fine except for thesourceparameter.  It still shows
> the old value.  Is there anything else that needs to be done to change
> thesourceparameter(short of creating a new Twitter application)?

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

Re: [twitter-dev] Re: Signature generation issue

[Taylor Singletary]

Hi Georgina,

I'm sure you're pretty close to figuring this out. A few tips when you've
gotten to this point:

- Make sure that you're transporting the request correctly
  - If you're using header-based OAuth, make sure that your HTTP
Authorization header is being properly setup and formatted. This will be
language-specific. Also make sure that you aren't repeating any of the
oauth_* parameters in the POST body or URL of your actual executed request.
Only parameters that don't begin with oauth_* should appear in the POST body
or query string. (In other words, don't present double authentication)
  - Make sure that your HTTP verbs are in agreement
- If you're sending a POST, make sure your HTTP client is actually
sending a POST and that your OAuth signature base string's method component
matched

Here's a quick walkthrough of all the steps involved in obtaining an access
token (though with my keys instead of yours).. note the signature base
string, authorization header, URL, and POST body for each step (keeping in
mind that the authorize step is kind of special in that it happens in a
browser).

Request Token Step
--
Request URL: https://api.twitter.com/oauth/request_token
HTTP Method: POST
POST body: (empty)
Signature Basestring:
POST&https%3A%2F%2Fapi.twitter.com
%2Foauth%2Frequest_token&oauth_callback%3Dhttp%253A%252F%252Flocalhost%253A3005%252Fthe_dance%252Fprocess_callback%253Fservice_provider_id%253D1%26oauth_consumer_key%3DOqEqJeafRSF10jBMStrZg%26oauth_nonce%3DK7ny27JTpKVsTgdyLdDfmQQWVLERj2zAK5BslRsqyw%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1300228849%26oauth_version%3D1.0

Authorization Header: OAuth
oauth_nonce="K7ny27JTpKVsTgdyLdDfmQQWVLERj2zAK5BslRsqyw",
oauth_callback="http%3A%2F%2Flocalhost%3A3005%2Fthe_dance%2Fprocess_callback%3Fservice_provider_id%3D1",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1300228849",
oauth_consumer_key="OqEqJeafRSF10jBMStrZg",
oauth_signature="Pk%2BMLdv028fxCErFyi8KXFM%2BddU%3D", oauth_version="1.0"

Response Body:
oauth_token=IPPjb9gdAB15Gnw7to8idfCfePqJgem9MVyhcEkPsU&oauth_token_secret=&oauth_callback_confirmed=true

Authorization Step
-
Request URL:
https://api.twitter.com/oauth/authorize?oauth_token=IPPjb9gdAB15Gnw7to8idfCfePqJgem9MVyhcEkPsU
HTTP Method: GET
POST Body: N/A
Signature Basestring: N/A
Authorization Header: N/A

Access Token Step
-
Request URL: https://api.twitter.com/oauth/access_token
HTTP Method: POST
POST Body: (empty)

Signature Basestring:
POST&https%3A%2F%2Fapi.twitter.com
%2Foauth%2Faccess_token&oauth_consumer_key%3DOqEqJeafRSF10jBMStrZg%26oauth_nonce%3DFCKJcpPIhJpOLV1VQtP560IH0rKI9jMPrlkzqQWoA%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1300228855%26oauth_token%3DIPPjb9gdAB15Gnw7to8idfCfePqJgem9MVyhcEkPsU%26oauth_verifier%3DPmThbFiYNd3TOoFRBbFwwRRPHB3PlkFbxmX4lCqmnc%26oauth_version%3D1.0

Authorization Header: OAuth
oauth_nonce="FCKJcpPIhJpOLV1VQtP560IH0rKI9jMPrlkzqQWoA",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1300228855",
oauth_consumer_key="OqEqJeafRSF10jBMStrZg",
oauth_token="IPPjb9gdAB15Gnw7to8idfCfePqJgem9MVyhcEkPsU",
oauth_verifier="PmThbFiYNd3TOoFRBbFwwRRPHB3PlkFbxmX4lCqmnc",
oauth_signature="AFJr%2BdS%2FmWgPbMtJR3vdwMA4cTk%3D", oauth_version="1.0"

Response Body:
oauth_token=819797-bAOfajtcYw8xHm1UQ3v5V5WfUb90zN7OWlWmvl8ZU0&oauth_token_secret=x&user_id=819797&screen_name=episod

On Tue, Mar 15, 2011 at 7:22 AM, lappynet  wrote:

> Thanks for everyone's help on this. I think that I now have this
> working (twitter documentation values match up).
>
> My problem now is that although I'm confident of my algorithm, twitter
> is always responding 401. I've debugged my network service and the
> message being returned is Incorrect Signature. I do not understand how
> this can be... :S
>
> On Mar 15, 6:03 am, kamesh SmartDude 
> wrote:
> > Hai lappynet,
> >
> > I Used GET method to retrive the Request Token And I Avoided the OAuth
> > Callback, because it was registered when i registered my app.
> >
> > Below is the method how i am  doing.
> >
> >  ** SignatureBase String is *
> >
> > GET&https%3A%2F%2Fapi.twitter.com
> > %2Foauth%2Frequest_token&oauth_consumer_key%3D
> >
> %26oauth_nonce%3DydBxFJKdzK%26oauth_signature_method%3DHMAC-SHA1%26oauth_ti
> mestamp%3D1300167727%26oauth_version%3D1.0
> >
> > Signature Key U are appending "&" and it is correct.
> >
> > i am adding the oauth header like below
> >
> > OAuth realm="Twitter API", oauth_consumer_key=,
> > oauth_nonce=ydBxFJKdzK,
> oauth_signature=89%2BSoLKBdE%2FeHN5PFRxNl3G7tNo%3D,
> > oauth_signature_method=HMAC-SHA1, oauth_timestamp=1300167727,
> > oauth_version=1.0
> >
> > I think u might have some problem with generating the signature.
> >
> > Try this,
> > //kamesh
> >
> >
> >
> >
> >
> >
> >
> > On Mon, Mar 14, 2011 at 8:16 PM, lappynet 
> wrote:
> > > cURL... I've heard about this, but I don't really know about it. Is
> > > there a windows version as I don't have access to other OSs

Re: [twitter-dev] users/lookup returns duplicates, missing records for valid users

[Adrian Petrescu]

Hi Taylor,

Not trying to be pushy or anything, but have you guys uncovered anything 
related to this issue? It's still happening quite regularly for a couple of 
weeks now.

Thanks,
Adrian

-- 
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] users/lookup returns duplicates, missing records for valid users

[Taylor Singletary]

Still working on it, unfortunately. No ETA for a fix yet. I know it's an
aggravating bug for anyone who runs into it. Thanks for being patient.

Taylor

On Mar 15, 2011, at 5:09 PM, Adrian Petrescu  wrote:

Hi Taylor,

Not trying to be pushy or anything, but have you guys uncovered anything
related to this issue? It's still happening quite regularly for a couple of
weeks now.

Thanks,
Adrian

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

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

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

[Ryan Sarver]

Adam, I don't know how else to make this any more clear. As long as you stay
within the rules, your app will not get shut off. We would like to see, and
recommend that, developers focus on bigger opportunities with more potential
than writing another consumer client app.

--
Ryan Sarver
@rsarver 



On Mon, Mar 14, 2011 at 9:28 AM, Adam Green <140...@gmail.com> wrote:

> But you will allow it, right? Even if it is thinking small, it will not be
> blocked? That is our problem. We can't separate business advice from a
> warning to prepare to be cut off. We can't help watching the hand that holds
> the kill switch. It makes it hard to hear what you say. Have patience, and
> keep explaining please. If something will not cause a ban, then say this
> explicitly to us. Don't just think it was implied.
>
>
> On Mon, Mar 14, 2011 at 11:20 AM, Raffi Krikorian wrote:
>
>> my statement here was not providing "small" on the size of the company,
>> but rather, "small" on the size of the idea. to re-iterate, making a piece
>> of software that simply renders home_timeline is thinking too small.
>>
>>
>> On Sun, Mar 13, 2011 at 6:21 PM, Lil Peck  wrote:
>>
>>> On Sun, Mar 13, 2011 at 7:45 PM, @siculars  wrote:
>>> > @raffi @rsarver, I wrote up my two cents earlier,
>>> > http://siculars.posterous.com/twitter-monoculture. I just don't
>>> > appreciate the direction you all are going in. @raffi, I spoke with
>>> > you at the CU recruiting event a few weeks back and I got to tell you
>>> > that if I were asked I would tell those kids to reconsider working at
>>> > twitter and possibly consider a Twitter competitor. you say "building
>>> > clients is ... Thinking too small" I would say your policy change is
>>> > thinking small and alienating your ardent supporters.
>>> >
>>>
>>> To which I would add, what is Twitter to arbitrate that which is and
>>> is not "too small?" Has Twitter subscribed to the fallacious "bigger
>>> is always better" philosophy?
>>>
>>> How small is too small?
>>>
>>> Less than $25 million in startup funds?
>>>
>>> OR
>>>
>>> One creative, fun loving person and their sweat equity?
>>>
>>> --
>>> 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
>>>
>>
>>
>>
>> --
>> Raffi Krikorian
>> Twitter, Application Services
>> http://twitter.com/raffi
>>
>>
>>  --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>>
>
>
>
> --
> Adam Green
> Twitter API Consultant and Trainer
> http://140dev.com
> @140dev
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

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

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

[Adam Green]

That is perfectly clear, Ryan.

The fact that people are still asking if they have Twitter's
permission to build a client and writing blog posts that say they
don't, shows that there is still confusion out there. My goal
throughout this has been to get simple statements like yours into this
list from Twitter HQ that eliminate the confusion. If someone at
Twitter could be given the task of saying what you just said every
time someone asks "Why can't I build a client?", or "Does this mean I
have to stop building my client?", the confusion will eventually be
removed. It may take days or weeks to reverse all the negative press.

In the future, please remember that every time you mention the
hundreds of apps you turn off each week  developers stop reading
anything else. It is not a good way to start a conversation. Thanks
for your patience.

On Tue, Mar 15, 2011 at 9:28 PM, Ryan Sarver  wrote:
> Adam, I don't know how else to make this any more clear. As long as you stay
> within the rules, your app will not get shut off. We would like to see, and
> recommend that, developers focus on bigger opportunities with more potential
> than writing another consumer client app.
>
> --
> Ryan Sarver
> @rsarver
>
>
> On Mon, Mar 14, 2011 at 9:28 AM, Adam Green <140...@gmail.com> wrote:
>>
>> But you will allow it, right? Even if it is thinking small, it will not be
>> blocked? That is our problem. We can't separate business advice from a
>> warning to prepare to be cut off. We can't help watching the hand that holds
>> the kill switch. It makes it hard to hear what you say. Have patience, and
>> keep explaining please. If something will not cause a ban, then say this
>> explicitly to us. Don't just think it was implied.
>>
>> On Mon, Mar 14, 2011 at 11:20 AM, Raffi Krikorian 
>> wrote:
>>>
>>> my statement here was not providing "small" on the size of the company,
>>> but rather, "small" on the size of the idea. to re-iterate, making a piece
>>> of software that simply renders home_timeline is thinking too small.
>>>
>>> On Sun, Mar 13, 2011 at 6:21 PM, Lil Peck  wrote:

 On Sun, Mar 13, 2011 at 7:45 PM, @siculars  wrote:
 > @raffi @rsarver, I wrote up my two cents earlier,
 > http://siculars.posterous.com/twitter-monoculture. I just don't
 > appreciate the direction you all are going in. @raffi, I spoke with
 > you at the CU recruiting event a few weeks back and I got to tell you
 > that if I were asked I would tell those kids to reconsider working at
 > twitter and possibly consider a Twitter competitor. you say "building
 > clients is ... Thinking too small" I would say your policy change is
 > thinking small and alienating your ardent supporters.
 >

 To which I would add, what is Twitter to arbitrate that which is and
 is not "too small?" Has Twitter subscribed to the fallacious "bigger
 is always better" philosophy?

 How small is too small?

 Less than $25 million in startup funds?

 OR

 One creative, fun loving person and their sweat equity?

 --
 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
>>>
>>>
>>>
>>> --
>>> Raffi Krikorian
>>> Twitter, Application Services
>>> http://twitter.com/raffi
>>>
>>>
>>> --
>>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>>> API updates via Twitter: http://twitter.com/twitterapi
>>> Issues/Enhancements Tracker:
>>> http://code.google.com/p/twitter-api/issues/list
>>> Change your membership to this group:
>>> http://groups.google.com/group/twitter-development-talk
>>
>>
>>
>> --
>> Adam Green
>> Twitter API Consultant and Trainer
>> http://140dev.com
>> @140dev
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>
>



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

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

[twitter-dev] Re: consistency and ecosystem opportunities

[David Newman]

Exactly how can someone develop a client for blind and partially
sighted people while staying within your new rules? Or are they stuck
with using a screen reader on the Twitter web pages (which are
notoriously inaccessible)?

Because speech synthesis is slower than reading, it will be necessary
to remove some of the proprietary notices and marks, rather than
repeating them all the time, so breaking term 4B. And exporting to
datastore to drive speech synthesis might break 4A.

I am not sure what 5C means in practice, but it would be important to
reproduce all parts of the Twitter service that make sense when done
through sound and typing, not vision.

As most disability aids are distributed through charities or social
service programs, people are paid to distribute them and teach people
how to use them. That breaks 5B.

It is common to let disabled users store pre-written pieces of text
they can send at a keystroke (or mouth blow if they cannot type on
normal keyboards). That would break 5D.

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

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

[manusis]

Yeah I went through gnip in detail but their pricing is excessively
expensive especially when I care only about twitter data and not the
hundred other sources that they provide. I was hoping that if not
"partner track", twitter might be open to give at least "restricted
track" access to developers.

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

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