Re: [twitter-dev] What is the status of profile image changes via API?

[Raghu Prasad]

On Mon, Sep 13, 2010 at 8:40 PM, Taylor Singletary
 wrote:
> Hi Raghu,
> One thing I recommend checking is that you're using the supported URL scheme
> for API-based profile image uploads,
> http://api.twitter.com/1/account/update_profile_image.json

Spot on! This was the issue. I was using the older end point. After
using this URL,
my problem is solved. :)

Thanks.

Raghu

-- 
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] /statuses/update.xml Read-only application cannot POST error show

[Shambhu Patnaik]

in connection show

 *socialcms * by socialcms.com


socialcms.com twitter plugin
Revoke Access  · approved on 4:42
PM Sep 1st · read and write access


my code work in off line but not work online. any addtional parmeter
required?




On 9/10/10, Taylor Singletary  wrote:
>
> Hi there,
>
>
> You may have issued your access token at some point in time when the
> application was marked as read-only. The best thing to do in this scenario
> is go to http://twitter.com/settings/connections to first sever the access
> token, then re-issue an access token while your application is in read-write
> mode.
>
>
> Taylor
>
>
> On Fri, Sep 10, 2010 at 1:01 AM, Shambhu wrote:
>
>> /statuses/update.xml  Read-only application cannot POST  error show
>>
>> my application work in off line (localhost) but not work in online
>>
>> twitter consul i test all parameter it work
>>
>> in application setting type is read write and type set to browser.
>>
>>
>> have you any idea ?
>>
>> --
>> 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] What is the status of profile image changes via API?

[Raghu Prasad]

On Mon, Sep 13, 2010 at 8:33 PM, CWorster  wrote:
> Hi Raghu,
>
> the profile image upload via API works fine. The new image is returned
> immediately. No caching issues.

Thanks for the info. That means I'm doing something wrong. I'll check.

>
> I'm using the PHP library from Matt Harris.
> http://github.com/themattharris/tmhOAuth

I am using Python's poster library. I am sure that there is no issue
in poster. It must be something to do with the way I am trying to
update the image.

Thanks again.

Raghu

-- 
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] Re: Seeing duplicate Twitter User ID's under the same Username in our DB

[Mark McBride]

Right.  But here's the scenario:

User ID 1 has screen name "foo"

You load user ID 1's data.

User ID 1 decides that "foo" is a silly screen name and changes it to "bar".
A new user, ID 10 signs up and decides that "foo" is an awesome screen name.

You load user 10's data.

So the important question:  if you go look at these IDs with duplicate
screen names, are they *currently* duplicates?  If so, can you email
me affected IDs?

   ---Mark

http://twitter.com/mccv



On Mon, Sep 13, 2010 at 6:08 PM, Sean Callahan  wrote:
> That is the problem. User ID's are not suppose to change, though in
> our DB we see the same screen name with a different User ID. Of the
> 5,000 users in the DB, some have 6 ID's, a few have 5, 4 and 3 ID's
> but many have 2 User ID's. We are talking 5,000 users being affected
> of 5 million users in our DB.
>
> Sean
>
> On Sep 13, 5:46 pm, Mark McBride  wrote:
>> One thought is that people change screen names at some frequency.  IDs
>> never change.
>>
>>    ---Mark
>>
>> http://twitter.com/mccv
>>
>>
>>
>> On Mon, Sep 13, 2010 at 4:41 PM, Sean Callahan  
>> wrote:
>> > Hello Twitter Support,
>>
>> > We are seeing something really weird.
>>
>> > We just noticed about 5,000 users in our database that have multiple
>> > User ID's under the same Username.
>>
>> > Have you every seen this and know why it happens and how we can
>> > prevent it from occurring again?
>>
>> > Thanks so much!
>>
>> > Sean
>>
>> > --
>> > 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-dev] Re: Seeing duplicate Twitter User ID's under the same Username in our DB

[Sean Callahan]

That is the problem. User ID's are not suppose to change, though in
our DB we see the same screen name with a different User ID. Of the
5,000 users in the DB, some have 6 ID's, a few have 5, 4 and 3 ID's
but many have 2 User ID's. We are talking 5,000 users being affected
of 5 million users in our DB.

Sean

On Sep 13, 5:46 pm, Mark McBride  wrote:
> One thought is that people change screen names at some frequency.  IDs
> never change.
>
>    ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Mon, Sep 13, 2010 at 4:41 PM, Sean Callahan  wrote:
> > Hello Twitter Support,
>
> > We are seeing something really weird.
>
> > We just noticed about 5,000 users in our database that have multiple
> > User ID's under the same Username.
>
> > Have you every seen this and know why it happens and how we can
> > prevent it from occurring again?
>
> > Thanks so much!
>
> > Sean
>
> > --
> > 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] Seeing duplicate Twitter User ID's under the same Username in our DB

[Mark McBride]

One thought is that people change screen names at some frequency.  IDs
never change.

   ---Mark

http://twitter.com/mccv



On Mon, Sep 13, 2010 at 4:41 PM, Sean Callahan  wrote:
> Hello Twitter Support,
>
> We are seeing something really weird.
>
> We just noticed about 5,000 users in our database that have multiple
> User ID's under the same Username.
>
> Have you every seen this and know why it happens and how we can
> prevent it from occurring again?
>
> Thanks so much!
>
> Sean
>
> --
> 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] Re: Request Token Failure

[sdenike]

Hey Tom,

I think I am falling into this pitfall myself.  I don't have the users
information only the information that the iPhone twitter app sends me
for posting an image on a custom end point.  With that header
information they send should be enough to send back to twitter to get
the user information? Or am I not understanding the process of doing
this?

Thanks,
Shelby

On Sep 10, 4:18 pm, Tom van der Woerdt  wrote:
> You don't need request_token for Echo - unless you don't have the user's
> credentials yet, but in that case you aren't using OAuth Echo.
>
> Tom
>
> On 9/11/10 1:13 AM, AS_Drone wrote:
>
>
>
> > We have been trying to implement the OAuth Echo method, but cannot get
> > a request-token. It returns with "Failed to validate oauth signature
> > and token".
>
> > Below is our Post data. Our signature aligns with data on the API
> > document. Any thoughts as to why we fail to oauth signature?
>
> > Post data:
>
> > Request Header:
> > POST /oauth/request_token HTTP/1.1
> > Content-Type: application/x-www-form-urlencoded
> > Authorization:
> > OAuth oauth_nonce="QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk",
> > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1272323042",
> > oauth_consumer_key="XX",
> > oauth_signature="Sr%2FKoecPb7D%2FnZNxt4qoM517Xjs%3D",
> > oauth_version="1.0"
> > Host: api.twitter.com
> > Content-Length: 0
> > Connection: Keep-Alive
> > Cache-Control: no-cache
> > Cookie: k=12.22.61.130.1283734903045073; guest_id=128373490305755705;
> > __utma=43838368.1906297211.1283734907.1283734907.1283762670.2;
> > __utmz=43838368.1283734907.1.1.utmcsr=(direct)|utmccn=(direct)|
> > utmcmd=(n
> > one); __utmv=43838368.lang%3A%20en; __qca=P0-1782216308-1283735015637;
> > __utmb=43838368.3.10.1283762670
> > Response Header:
> > HTTP/1.1 401 Unauthorized
> > Date: Mon, 06 Sep 2010 09:13:15 GMT
> > Server: hi
> > Status: 401 Unauthorized
> > X-Transaction: 1283764395-39211-63478
> > Last-Modified: Mon, 06 Sep 2010 09:13:15 GMT
> > X-Runtime: 0.00573
> > Content-Type: text/html; charset=utf-8
> > Content-Length: 44
> > Pragma: no-cache
> > X-Revision: DEV
> > Expires: Tue, 31 Mar 1981 05:00:00 GMT
> > Cache-Control: no-cache, no-store, must-revalidate, pre-check=0,
> > post-check=0
> > Set-Cookie:
> > _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCKEfUuYqAToHaWQiJWVhY2RjNDQ3NGNmMm
> > Mw%250ANjUwYWIzMGE3OWE4NDNlZTM3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
> > %250A
> > OjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
> > c7925282fe8f92e14b1a250c09ddff
> > e386a925be; domain=.twitter.com; path=/
> > Vary: Accept-Encoding
> > Connection: close
> > Failed to validate oauth signature and token

-- 
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] PHP, Curl an OAuth Echo errors

[sdenike]

I have been trying for weeks here to get this going and cant seem to
figure this out.  I am trying to create a simple PHP/MySQL image
uploader much like that of twitpic, yfrog etc etc to host my images on
my own server.  I am using the iPhone twitter app and have created a
custom end point on my server, it handles the uploads fine.  After
shooting some emails back with twitter support I was told to look into
the twitter oauth echo command to get such information like username
etc etc from that tweet.  To do so my understanding is that the iPhone
twitter app sends header information to my script. my script should
then take that header information as well as my consumer key and send
that request back to twitter.

That header that I create should include:
X-Auth-Service-Provider: 
https://api.twitter.com/1/account/verify_credentials.json
X-Verify-Credentials-Authorization OAuth oauth_consumer_key="...",
oauth_token="...", oauth_signature_method="...",
oauth_signature="...", oauth_timestamp="...", oauth_nonce="...",
oauth_version="..."

I am sending all this information back with curl in my php script and
keep getting the following sent back to me
{"request":"/1/account/verify_credentials.json","error":"Could not
authenticate you."}

Does anyone have a working example as I am not finding any PHP code
that clearly outlines this whole statement, I cant imagine it being
that hard thats why its bothering me that it has taken this long to
figure out.

-- 
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] Seeing duplicate Twitter User ID's under the same Username in our DB

[Sean Callahan]

Hello Twitter Support,

We are seeing something really weird.

We just noticed about 5,000 users in our database that have multiple
User ID's under the same Username.

Have you every seen this and know why it happens and how we can
prevent it from occurring again?

Thanks so much!

Sean

-- 
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] How to authorize from Client-Mobile-Application

[Tom van der Woerdt]

Currently, they don't expire. You may, however, like to implement some
checks on whether they are still valid, because the user may decide to
revoke access.

Tom


On 9/13/10 11:46 PM, Ronak Kumar Samantray wrote:
> Once i get the access token, how long can i retain i use it for ? So
> that i need not ask the user to do the whole process again ? Is it that
> once in a lifetime ?
> 
> Ronak Kumar Samantray
> Hyderabad
> 
> Mobile : +91-9347290267
>040-66933916
> 
> 
> On Tue, Sep 14, 2010 at 2:05 AM, Taylor Singletary
> mailto:taylorsinglet...@twitter.com>> wrote:
> 
> Correct, you would still need to ask the user to go to a specific
> web page, where they will be asked to authorize your application and
> then be presented with a PIN code that they would enter in your
> application.
> 
> Taylor
> 
> On Mon, Sep 13, 2010 at 1:32 PM, Ronak Kumar Samantray
> mailto:ronak@gmail.com>> wrote:
> 
> In the OOB flow also i need to redirect the user to an URL isnt
> it where he needs to key-in a PIN code ? Or am i missing something ?
>  
> Thanks
> Ronak
> --
> 
> Ronak Kumar Samantray
> Hyderabad
> 
> Mobile : +91-9347290267
>040-66933916
> 
> 
> On Tue, Sep 14, 2010 at 1:59 AM, Taylor Singletary
>  > wrote:
> 
> Some mobile clients opt to use a form of OAuth called xAuth
> for authenticating users without the
> web-page-song-and-dance. You can find out more about xAuth
> at http://dev.twitter.com/pages/xauth and can request
> permissions to utilize it by sending a detailed note to
> a...@twitter.com  -- it is unlikely
> whether you'll receive authorization to use xAuth within 20
> hours (it generally takes 3 or more days). Otherwise, you
> can still direct users through the "out of band" OAuth flow.
> 
> Thanks,
> Taylor
> 
> On Mon, Sep 13, 2010 at 12:29 PM, ronak  > wrote:
> 
> Hi,
> 
> I am developing a client application (not a web
> application). I am
> able to get the token and the token secret. Now how do i
> authorize the
> user ? Because for authorization i see the documentation
> asking me to
> redirect the user to a particular web-location !! How
> can i achieve
> this using a client-app ?
> 
> Please help me out. I have to hit a delivery date in
> another 20 hours :
> (
> 
> Thanks
> Ronak
> 
> --
> 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 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
x

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterap

Re: [twitter-dev] How to authorize from Client-Mobile-Application

[Ronak Kumar Samantray]

Once i get the access token, how long can i retain i use it for ? So that i
need not ask the user to do the whole process again ? Is it that once in a
lifetime ?

Ronak Kumar Samantray
Hyderabad

Mobile : +91-9347290267
   040-66933916


On Tue, Sep 14, 2010 at 2:05 AM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> Correct, you would still need to ask the user to go to a specific web page,
> where they will be asked to authorize your application and then be presented
> with a PIN code that they would enter in your application.
>
> Taylor
>
>   On Mon, Sep 13, 2010 at 1:32 PM, Ronak Kumar Samantray <
> ronak@gmail.com> wrote:
>
>>   In the OOB flow also i need to redirect the user to an URL isnt it
>> where he needs to key-in a PIN code ? Or am i missing something ?
>>
>> Thanks
>> Ronak
>> --
>>
>> Ronak Kumar Samantray
>> Hyderabad
>>
>> Mobile : +91-9347290267
>>040-66933916
>>
>>
>>   On Tue, Sep 14, 2010 at 1:59 AM, Taylor Singletary <
>> taylorsinglet...@twitter.com> wrote:
>>
>>>  Some mobile clients opt to use a form of OAuth called xAuth for
>>> authenticating users without the web-page-song-and-dance. You can find out
>>> more about xAuth at http://dev.twitter.com/pages/xauth and can request
>>> permissions to utilize it by sending a detailed note to a...@twitter.com-- 
>>> it is unlikely whether you'll receive authorization to use xAuth within
>>> 20 hours (it generally takes 3 or more days). Otherwise, you can still
>>> direct users through the "out of band" OAuth flow.
>>>
>>> Thanks,
>>> Taylor
>>>
>>>   On Mon, Sep 13, 2010 at 12:29 PM, ronak  wrote:
>>>
  Hi,

 I am developing a client application (not a web application). I am
 able to get the token and the token secret. Now how do i authorize the
 user ? Because for authorization i see the documentation asking me to
 redirect the user to a particular web-location !! How can i achieve
 this using a client-app ?

 Please help me out. I have to hit a delivery date in another 20 hours :
 (

 Thanks
 Ronak

 --
 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 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] Changing to Read/Write application

[Tom van der Woerdt]

Instant. However, any existing credential will have to be re-created for
security reasons.

Tom


On 9/13/10 11:30 PM, IDOL wrote:
> How long does it take for to permission a Read-only application  to
> become a Read/Write application after changing the Access Level to
> read and write on the Application settings page?
> 

-- 
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] Changing to Read/Write application

[IDOL]

How long does it take for to permission a Read-only application  to
become a Read/Write application after changing the Access Level to
read and write on the Application settings page?

-- 
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] Re: XML hashtags missing

[james.eats.wo...@gmail.com]

Hi,

Cheers for the fast reply Taylor. Is there any scope as to when these
issues may be solved, as several clients sites may have to be changed
as their feeds are not being updated.

Thanks again,

James

On Sep 13, 4:28 pm, Taylor Singletary 
wrote:
> Hi James,
>
> We still have some intermittent issues with entities returning
> consistently across tweets. We are working to fix this.
>
> I would also recommend using include_entities=true, even though =1 should
> work.
>
> Thanks,
> Taylor
>
> On Mon, Sep 13, 2010 at 8:20 AM, james.eats.wo...@gmail.com <
>
>
>
> james.eats.wo...@gmail.com> wrote:
> > Has twitter changed there output for xml ?  below is one of the status
> > that are returned through the request
>
> >http://api.twitter.com/1/statuses/user_timeline.xml?include_entities=...
> > which does have entities; hash tags specifically returned on several
> > status. however none as of the 9th of September like the one bellow
> > anyone got any ideas on this would be greatly appreciated!
> > I am developing in c# asp.net however this shouldn't be an issue as it
> > appears to be the XML that is causing the issue...
>
> > 
> >  Wed Sep 08 15:27:44 + 2010
> >  23923594634
> >  iOS4 to be released today?http://bit.ly/b1Du5eI saw this at
> > the weekend too... Bring on HDR photos! #apple #iphone
> >   > rel="nofollow">TweetDeck
> >  false
> >  
> >  
> >  false
> >  
> >  
> >  false
> >  
> >    6595462
> >    Tim Harper
> >    superbreaker
> >    East Central and Sarf London
> >    Creative Director of TheTin Ideas Activation Agency > description>
> >    http://a3.twimg.com/profile_images/1115764091/
> > SuperbreakerCrop_normal.png
> > 
> >    http://www.thetin.net
> >    false
> >    101
> >    352726
> >    3E4415
> >    D02B55
> >    99CC33
> >    829D5E > profile_sidebar_border_color>
> >    182
> >    Tue Jun 05 14:40:25 + 2007
> >    1
> >    0
> >    London
> >    http://s.twimg.com/a/1283564528/
> > images/themes/theme5/bg.gif
> > 
> >    false
> >    true
> >    false
> >    false
> >    false
> >    false
> >    317
> >    en
> >    false
> >    false
> >    4
> >    false
> >  
> >  
> >  
> >  
> >  
> > 
>
> > --
> > 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] Javascript Twitter API

[Tom van der Woerdt]

http://dev.twitter.com/anywhere

Tom


On 9/13/10 10:39 PM, Pavel wrote:
> Hello Twitter community,
> 
> I'm a newbie in API and have a simple question:
> 
> Is this a way to use some Twitter API and post message in Twitter?
> So I need something like this: Twitter.send(user, name, message);
> 
> I know, that Twitter uses OAuth, but all examples what I have seen
> uses backend scripts.
> I'm using Sencha Touch framework in my application and I don't want to
> use any backend scripts for sending message to Twitter.
> Is this possible?
> 
> Thanks,
> Pavel
> 

-- 
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] Javascript Twitter API

[Pavel]

Hello Twitter community,

I'm a newbie in API and have a simple question:

Is this a way to use some Twitter API and post message in Twitter?
So I need something like this: Twitter.send(user, name, message);

I know, that Twitter uses OAuth, but all examples what I have seen
uses backend scripts.
I'm using Sencha Touch framework in my application and I don't want to
use any backend scripts for sending message to Twitter.
Is this possible?

Thanks,
Pavel

-- 
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] twitter search with 'following' flag

[Felipe Peña Riveros]

Hi there

I'm developing a twitter app with two states. The first displays a
public timeline based on a hashtag (for instance #alliwant). The
second one displays an user timeline.

In both of them, there's a search functionality in which you can
choose whether to look for a hashtag, twitter user or words.

While searching, I'm looking for a way to know if the user who posted
that tweet (displayed on the search result) is friend with the user
who's logged. As far as I can see, the search call does not need
authentication, so for that matter it would be impossible to know
this.

Another way would be to ask for every single tweet, but my hands are
tied with the rate call limit.

Any help will be appreciated.

Thanks

Felipe

-- 
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] How to authorize from Client-Mobile-Application

[Taylor Singletary]

Correct, you would still need to ask the user to go to a specific web page,
where they will be asked to authorize your application and then be presented
with a PIN code that they would enter in your application.

Taylor

On Mon, Sep 13, 2010 at 1:32 PM, Ronak Kumar Samantray
wrote:

> In the OOB flow also i need to redirect the user to an URL isnt it where he
> needs to key-in a PIN code ? Or am i missing something ?
>
> Thanks
> Ronak
> --
>
> Ronak Kumar Samantray
> Hyderabad
>
> Mobile : +91-9347290267
>040-66933916
>
>
> On Tue, Sep 14, 2010 at 1:59 AM, Taylor Singletary <
> taylorsinglet...@twitter.com> wrote:
>
>> Some mobile clients opt to use a form of OAuth called xAuth for
>> authenticating users without the web-page-song-and-dance. You can find out
>> more about xAuth at http://dev.twitter.com/pages/xauth and can request
>> permissions to utilize it by sending a detailed note to a...@twitter.com-- 
>> it is unlikely whether you'll receive authorization to use xAuth within
>> 20 hours (it generally takes 3 or more days). Otherwise, you can still
>> direct users through the "out of band" OAuth flow.
>>
>> Thanks,
>> Taylor
>>
>>   On Mon, Sep 13, 2010 at 12:29 PM, ronak  wrote:
>>
>>>  Hi,
>>>
>>> I am developing a client application (not a web application). I am
>>> able to get the token and the token secret. Now how do i authorize the
>>> user ? Because for authorization i see the documentation asking me to
>>> redirect the user to a particular web-location !! How can i achieve
>>> this using a client-app ?
>>>
>>> Please help me out. I have to hit a delivery date in another 20 hours :
>>> (
>>>
>>> Thanks
>>> Ronak
>>>
>>> --
>>> 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 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] How to authorize from Client-Mobile-Application

[Ronak Kumar Samantray]

In the OOB flow also i need to redirect the user to an URL isnt it where he
needs to key-in a PIN code ? Or am i missing something ?

Thanks
Ronak
--

Ronak Kumar Samantray
Hyderabad

Mobile : +91-9347290267
   040-66933916


On Tue, Sep 14, 2010 at 1:59 AM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> Some mobile clients opt to use a form of OAuth called xAuth for
> authenticating users without the web-page-song-and-dance. You can find out
> more about xAuth at http://dev.twitter.com/pages/xauth and can request
> permissions to utilize it by sending a detailed note to a...@twitter.com --
> it is unlikely whether you'll receive authorization to use xAuth within 20
> hours (it generally takes 3 or more days). Otherwise, you can still direct
> users through the "out of band" OAuth flow.
>
> Thanks,
> Taylor
>
>   On Mon, Sep 13, 2010 at 12:29 PM, ronak  wrote:
>
>>  Hi,
>>
>> I am developing a client application (not a web application). I am
>> able to get the token and the token secret. Now how do i authorize the
>> user ? Because for authorization i see the documentation asking me to
>> redirect the user to a particular web-location !! How can i achieve
>> this using a client-app ?
>>
>> Please help me out. I have to hit a delivery date in another 20 hours :
>> (
>>
>> Thanks
>> Ronak
>>
>> --
>> 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] How to authorize from Client-Mobile-Application

[Taylor Singletary]

Some mobile clients opt to use a form of OAuth called xAuth for
authenticating users without the web-page-song-and-dance. You can find out
more about xAuth at http://dev.twitter.com/pages/xauth and can request
permissions to utilize it by sending a detailed note to a...@twitter.com --
it is unlikely whether you'll receive authorization to use xAuth within 20
hours (it generally takes 3 or more days). Otherwise, you can still direct
users through the "out of band" OAuth flow.

Thanks,
Taylor

On Mon, Sep 13, 2010 at 12:29 PM, ronak  wrote:

> Hi,
>
> I am developing a client application (not a web application). I am
> able to get the token and the token secret. Now how do i authorize the
> user ? Because for authorization i see the documentation asking me to
> redirect the user to a particular web-location !! How can i achieve
> this using a client-app ?
>
> Please help me out. I have to hit a delivery date in another 20 hours :
> (
>
> Thanks
> Ronak
>
> --
> 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] How to authorize from Client-Mobile-Application

[ronak]

Hi,

I am developing a client application (not a web application). I am
able to get the token and the token secret. Now how do i authorize the
user ? Because for authorization i see the documentation asking me to
redirect the user to a particular web-location !! How can i achieve
this using a client-app ?

Please help me out. I have to hit a delivery date in another 20 hours :
(

Thanks
Ronak

-- 
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] Re: Privacy Policy Question

[Brian Sutorius]

As a developer of an application open for public use, it is a best
practice to offer your own privacy policy on your website or within
your application. At the very least, you must be clear about how you
will use your users' account data and/or take actions on their behalf.
This is mirrored in our Developer Principles within the API Terms of
Service [1]: Don't Surprise Users.

Of course, there are applications that interface with Twitter's API
without being open to public usage. Twitter's privacy policy [2]
states that public account data is distributed through the service via
the API.

Brian Sutorius
Twitter API Policy

[1] http://dev.twitter.com/pages/api_terms
[2] http://twitter.com/privacy

On Sep 11, 2:54 am, Hermi  wrote:
> The Twitter Privacy Policy says that 'developers must clearly disclose
> what they will be doing with data collected from users".
>
> Does anyone know how this works in practice with Twitter data?  Do I
> need to include a privacy policy on my website telling saying that I
> use personal data from Twitter users?  What if the Twitter users don't
> even know I am using their data and they never look at my website?
>
> If anyone knows the answer 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?hl=en

Re: [twitter-dev] Re: Is gardenhose being ramped up?

[John Kalucki]

I don't know what it could be. We took a spike during the VMAs, but that
doesn't match with your data. I'd examine your connection logs to see if you
were cycling excessively in the past, or dropping tweets due to parsing
errors, or something of that sort...

-John


On Mon, Sep 13, 2010 at 11:42 AM, Sanjay  wrote:

> John - yeah, I saw the increase from that bump previously but if you
> look at the graph I included, this current bump is greater still.
> Mind you, I'm not complaining just trying to understand what is going
> on.  If this increase is short lived I won't try to design around it.
> If it's going to be sustained, I want this data being sent down the
> pipe.  Right now I'm seeing between 2k and 3k updates every 30 seconds
> whereas before a few days ago it was between 1k and 2k updates every
> 30 seconds.  Any scoop would be helpful for planning purposes.
> Thanks!
>
> Sanjay
>
> On Sep 13, 12:05 pm, John Kalucki  wrote:
> > We increased the Gardenhose on August 30, as announced here:
> http://groups.google.com/group/twitter-api-announce/browse_thread/thr...
> > .
> >
> > We haven't changed the proportion since. A Streaming API application
> should
> > always be prepared for accept spikes of at least three, if not four times
> as
> > large as daily peak traffic.
> >
> > -John Kaluckihttp://twitter.com/jkalucki
> > Twitter, Inc.
> >
> >
> >
> >
> >
> >
> >
> > On Mon, Sep 13, 2010 at 8:43 AM, Sanjay  wrote:
> > > I just took a look at my bandwidth usage from last night to see the
> > > effect of the VMAs (dramatic BTW), and thought I'd check it out over
> > > the last week.  It looks like gardenhose has been ramping up since
> > > late Sept 10th/early Sept 11th.  Is this intentional?  Any idea where
> > > we're ending.  My DB isn't keeping up with this so I need to
> > > reorganize if we're going to keep at this level.  Help?  Thoughts?
> >
> > >http://twitpic.com/2o3ewf
> >
> > > Sanjay
> >
> > > --
> > > 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-dev] Re: iPhone::Incorrect oauth_signature for xAuth?

[Nikolay Klimchuk]

Thanks Tom

I feel better now LoL

On Sep 13, 2:41 pm, Tom van der Woerdt  wrote:
> 2010-09-13 20:39:11.190 Test[56513:207] NSData *HMAC: <3146268a 86d17682
> bab34655 aa8e3140 d34ed7bc>
> 2010-09-13 20:39:11.191 Test[56513:207] NSString *HMAC64:
> MUYmiobRdoK6s0ZVqo4xQNNO17w=
>
> Looks like you're right :-)
>
> @episod: You should fix that! :-)
>
> Tom
>
> On 9/13/10 8:23 PM, Nikolay Klimchuk wrote:
>
>
>
> > Still no luck
>
> > With your code I'm gettings exactly the same result
> > MUYmiobRdoK6s0ZVqo4xQNNO17w=
>
> > Something really strange in example herehttp://dev.twitter.com/pages/xauth
>
> > Nikolay Klimchuk
>
> > On Sep 13, 7:19 am, Tom van der Woerdt  wrote:
> >> Oh, hehe, good point. That's because my Base String has one extra
> >> urlencoded '&' on the end, and that shouldn't be there.
>
> >> Tom
>
> >> On Mon, 13 Sep 2010 04:18:06 -0700 (PDT), Nikolay Klimchuk
>
> >>  wrote:
> >>> Thank you Tom
>
> >>> I will try your algorithm and compare results.
> >>> Quick question: why you do this [str substringToIndex:[str
> >>> length]-3] ?
>
> >>> Nikolay Klimchuk
>
> >>> On Sep 13, 2:46 am, Tom van der Woerdt  wrote:
>  Hi Nikolay,
>
>  The first part of your code looks fine. You may, however, like to do
>  some debugging on the HMAC part - it looks a bit too simple to me.
>
>  This works :
>          NSString *compKey = [NSString 
>  stringWithFormat:@"%@&%@",secret,userSecret];
>          const char *cKey = [compKey 
>  cStringUsingEncoding:NSUTF8StringEncoding];
>          const char *cData = [[str substringToIndex:[str length]-3]
>  cStringUsingEncoding:NSUTF8StringEncoding];
>          unsigned char cHMAC[CC_SHA1_DIGEST_LENGTH];
>          CCHmac(kCCHmacAlgSHA1, cKey, strlen(cKey), cData, strlen(cData), 
>  cHMAC);
>          NSData *HMAC = [[NSData alloc] initWithBytes:cHMAC 
>  length:sizeof(cHMAC)];
>  (str being the Base String)
>
>  Hope it helps :-)
>
>  Tom
>
>  On 9/13/10 3:02 AM, Nikolay Klimchuk wrote:
>
> > I'm trying to understand why algorithm for calculation of
> > oauth_signature does not give me the same result as shown here:
> >http://dev.twitter.com/pages/xauth
>
> > In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
>
> > If I URL encode such result it's still very different from
> > yUDBrcMMm6ghqBEKCFKVoJPIacU%3D
>
> > I've tried different implementations, all of them give the same
> > result. After few hours of exercises with all this stuff I completely
> > run out of ideas, please help
>
> > // Test with input data taken from Twitter page
>
> > NSString *s= @"POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> > %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> > %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> > %26x_auth_password%3D%2525%2526123%2521aZ%252B
> > %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant";
>
> > NSString *k = @"5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&";
>
> > NSString *signedSK = [NetworkManager base64forData:[NetworkManager
> > HMACSHA1withKey:k forString:s]];
>
> > // Source code
>
> > + (NSData *)HMACSHA1withKey:(NSString *)key forString:(NSString
> > *)string
> > {
> >    NSData *clearTextData = [string
> > dataUsingEncoding:NSUTF8StringEncoding];
> >    NSData *keyData = [key dataUsingEncoding:NSUTF8StringEncoding];
>
> >    uint8_t digest[CC_SHA1_DIGEST_LENGTH] = {0};
>
> >    CCHmacContext hmacContext;
> >    CCHmacInit(&hmacContext, kCCHmacAlgSHA1, keyData.bytes,
> > keyData.length);
> >    CCHmacUpdate(&hmacContext, clearTextData.bytes,
> > clearTextData.length);
> >    CCHmacFinal(&hmacContext, digest);
>
> >    return [NSData dataWithBytes:digest length:CC_SHA1_DIGEST_LENGTH];
> > }
>
> > //Sourcehttp://www.cocoadev.com/index.pl?BaseSixtyFour
>
> > + (NSString *)base64forData:(NSData *)data
> > {
> >     static const char encodingTable[] =
> > "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
>
> >     if ([data length] == 0)
> >         return @"";
>
> >     char *characters = malloc((([data length] + 2) / 3) * 4);
> >     if (characters == NULL)
> >         return nil;
> >     NSUInteger length = 0;
>
> >     NSUInteger i = 0;
> >     while (i < [data length])
> >     {
> >         char buffer[3] = {0,0,0};
> >         short bufferLength = 0;
> >         while (bufferLength < 3 && i < [data length])
> >                    buffer[bufferLength++] = ((char *)[data bytes])[i++];
>
> >         //  Encode the bytes in the buffer to four characters,
> > including padding "=" characters if necessary.
> >         characters[length++] = encodingTable[(buffer[0] & 0xF

[twitter-dev] Re: Is gardenhose being ramped up?

[Sanjay]

John - yeah, I saw the increase from that bump previously but if you
look at the graph I included, this current bump is greater still.
Mind you, I'm not complaining just trying to understand what is going
on.  If this increase is short lived I won't try to design around it.
If it's going to be sustained, I want this data being sent down the
pipe.  Right now I'm seeing between 2k and 3k updates every 30 seconds
whereas before a few days ago it was between 1k and 2k updates every
30 seconds.  Any scoop would be helpful for planning purposes.
Thanks!

Sanjay

On Sep 13, 12:05 pm, John Kalucki  wrote:
> We increased the Gardenhose on August 30, as announced 
> here:http://groups.google.com/group/twitter-api-announce/browse_thread/thr...
> .
>
> We haven't changed the proportion since. A Streaming API application should
> always be prepared for accept spikes of at least three, if not four times as
> large as daily peak traffic.
>
> -John Kaluckihttp://twitter.com/jkalucki
> Twitter, Inc.
>
>
>
>
>
>
>
> On Mon, Sep 13, 2010 at 8:43 AM, Sanjay  wrote:
> > I just took a look at my bandwidth usage from last night to see the
> > effect of the VMAs (dramatic BTW), and thought I'd check it out over
> > the last week.  It looks like gardenhose has been ramping up since
> > late Sept 10th/early Sept 11th.  Is this intentional?  Any idea where
> > we're ending.  My DB isn't keeping up with this so I need to
> > reorganize if we're going to keep at this level.  Help?  Thoughts?
>
> >http://twitpic.com/2o3ewf
>
> > Sanjay
>
> > --
> > 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] Missing entities in REST

[Jesse]

Hi, I'm trying to view my last tweet, but I can't seem to be able to
see the Tweet Entities.

Here is what I'm trying to view:
http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=(redacted)&count=1&include_entities=t

But I don't see the "entities" element.

Any help would be appreciated
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?hl=en

[twitter-dev] Re: XAuth signature error

[Nikolay Klimchuk]

What algorithm you're using for hmac-sha1 and base64

I'm getting different oauth_signature for the xAuth test example
http://dev.twitter.com/pages/xauth

Nikolay Klimchuk

On Sep 13, 1:01 am, Double K  wrote:
> hi, my name is Kim.
> I will make XAuth module. So i need developer help.
> i make signature base string
> for example
>
> POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> %26x_auth_password%3D%2525%2526123%2521aZ%252B
> %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant
>
> this is dev.twitter.com example
> i saw it that oauth_signature is signature base string's hmac-sha1
> encoding and base64 encoding's result
> oauth_signature="yUDBrcMMm6ghqBEKCFKVoJPIacU%3D"
> is it right?
> i can't do this.
> somebody help me. T.T
>
> Q1. i want to know signature base string's hmac-sha1 encoding result.
> Q2. oauth-signature="yUDBrcMMm6ghqBEKCFKVoJPIacU%3D" is it correct?

-- 
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] Re: iPhone::Incorrect oauth_signature for xAuth?

[Tom van der Woerdt]

2010-09-13 20:39:11.190 Test[56513:207] NSData *HMAC: <3146268a 86d17682
bab34655 aa8e3140 d34ed7bc>
2010-09-13 20:39:11.191 Test[56513:207] NSString *HMAC64:
MUYmiobRdoK6s0ZVqo4xQNNO17w=

Looks like you're right :-)

@episod: You should fix that! :-)

Tom


On 9/13/10 8:23 PM, Nikolay Klimchuk wrote:
> Still no luck
> 
> With your code I'm gettings exactly the same result
> MUYmiobRdoK6s0ZVqo4xQNNO17w=
> 
> Something really strange in example here http://dev.twitter.com/pages/xauth
> 
> Nikolay Klimchuk
> 
> On Sep 13, 7:19 am, Tom van der Woerdt  wrote:
>> Oh, hehe, good point. That's because my Base String has one extra
>> urlencoded '&' on the end, and that shouldn't be there.
>>
>> Tom
>>
>> On Mon, 13 Sep 2010 04:18:06 -0700 (PDT), Nikolay Klimchuk
>>
>>
>>
>>  wrote:
>>> Thank you Tom
>>
>>> I will try your algorithm and compare results.
>>> Quick question: why you do this [str substringToIndex:[str
>>> length]-3] ?
>>
>>> Nikolay Klimchuk
>>
>>> On Sep 13, 2:46 am, Tom van der Woerdt  wrote:
 Hi Nikolay,
>>
 The first part of your code looks fine. You may, however, like to do
 some debugging on the HMAC part - it looks a bit too simple to me.
>>
 This works :
 NSString *compKey = [NSString 
 stringWithFormat:@"%@&%@",secret,userSecret];
 const char *cKey = [compKey 
 cStringUsingEncoding:NSUTF8StringEncoding];
 const char *cData = [[str substringToIndex:[str length]-3]
 cStringUsingEncoding:NSUTF8StringEncoding];
 unsigned char cHMAC[CC_SHA1_DIGEST_LENGTH];
 CCHmac(kCCHmacAlgSHA1, cKey, strlen(cKey), cData, strlen(cData), 
 cHMAC);
 NSData *HMAC = [[NSData alloc] initWithBytes:cHMAC 
 length:sizeof(cHMAC)];
 (str being the Base String)
>>
 Hope it helps :-)
>>
 Tom
>>
 On 9/13/10 3:02 AM, Nikolay Klimchuk wrote:
>>
> I'm trying to understand why algorithm for calculation of
> oauth_signature does not give me the same result as shown here:
> http://dev.twitter.com/pages/xauth
>>
> In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
>>
> If I URL encode such result it's still very different from
> yUDBrcMMm6ghqBEKCFKVoJPIacU%3D
>>
> I've tried different implementations, all of them give the same
> result. After few hours of exercises with all this stuff I completely
> run out of ideas, please help
>>
> // Test with input data taken from Twitter page
>>
> NSString *s= @"POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> %26x_auth_password%3D%2525%2526123%2521aZ%252B
> %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant";
>>
> NSString *k = @"5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&";
>>
> NSString *signedSK = [NetworkManager base64forData:[NetworkManager
> HMACSHA1withKey:k forString:s]];
>>
> // Source code
>>
> + (NSData *)HMACSHA1withKey:(NSString *)key forString:(NSString
> *)string
> {
>NSData *clearTextData = [string
> dataUsingEncoding:NSUTF8StringEncoding];
>NSData *keyData = [key dataUsingEncoding:NSUTF8StringEncoding];
>>
>uint8_t digest[CC_SHA1_DIGEST_LENGTH] = {0};
>>
>CCHmacContext hmacContext;
>CCHmacInit(&hmacContext, kCCHmacAlgSHA1, keyData.bytes,
> keyData.length);
>CCHmacUpdate(&hmacContext, clearTextData.bytes,
> clearTextData.length);
>CCHmacFinal(&hmacContext, digest);
>>
>return [NSData dataWithBytes:digest length:CC_SHA1_DIGEST_LENGTH];
> }
>>
> //Sourcehttp://www.cocoadev.com/index.pl?BaseSixtyFour
>>
> + (NSString *)base64forData:(NSData *)data
> {
> static const char encodingTable[] =
> "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
>>
> if ([data length] == 0)
> return @"";
>>
> char *characters = malloc((([data length] + 2) / 3) * 4);
> if (characters == NULL)
> return nil;
> NSUInteger length = 0;
>>
> NSUInteger i = 0;
> while (i < [data length])
> {
> char buffer[3] = {0,0,0};
> short bufferLength = 0;
> while (bufferLength < 3 && i < [data length])
>buffer[bufferLength++] = ((char *)[data bytes])[i++];
>>
> //  Encode the bytes in the buffer to four characters,
> including padding "=" characters if necessary.
> characters[length++] = encodingTable[(buffer[0] & 0xFC) >> 2];
> characters[length++] = encodingTable[((buffer[0] & 0x03) << 4)
> | ((buffer[1] & 0xF0) >> 4)];
> if (bufferLength > 1)
>characters[length++] = encodingTable[((buffer[1] & 
> 0x0F) << 

[twitter-dev] Re: iPhone::Incorrect oauth_signature for xAuth?

[Nikolay Klimchuk]

Still no luck

With your code I'm gettings exactly the same result
MUYmiobRdoK6s0ZVqo4xQNNO17w=

Something really strange in example here http://dev.twitter.com/pages/xauth

Nikolay Klimchuk

On Sep 13, 7:19 am, Tom van der Woerdt  wrote:
> Oh, hehe, good point. That's because my Base String has one extra
> urlencoded '&' on the end, and that shouldn't be there.
>
> Tom
>
> On Mon, 13 Sep 2010 04:18:06 -0700 (PDT), Nikolay Klimchuk
>
>
>
>  wrote:
> > Thank you Tom
>
> > I will try your algorithm and compare results.
> > Quick question: why you do this [str substringToIndex:[str
> > length]-3] ?
>
> > Nikolay Klimchuk
>
> > On Sep 13, 2:46 am, Tom van der Woerdt  wrote:
> >> Hi Nikolay,
>
> >> The first part of your code looks fine. You may, however, like to do
> >> some debugging on the HMAC part - it looks a bit too simple to me.
>
> >> This works :
> >>         NSString *compKey = [NSString 
> >> stringWithFormat:@"%@&%@",secret,userSecret];
> >>         const char *cKey = [compKey 
> >> cStringUsingEncoding:NSUTF8StringEncoding];
> >>         const char *cData = [[str substringToIndex:[str length]-3]
> >> cStringUsingEncoding:NSUTF8StringEncoding];
> >>         unsigned char cHMAC[CC_SHA1_DIGEST_LENGTH];
> >>         CCHmac(kCCHmacAlgSHA1, cKey, strlen(cKey), cData, strlen(cData), 
> >> cHMAC);
> >>         NSData *HMAC = [[NSData alloc] initWithBytes:cHMAC 
> >> length:sizeof(cHMAC)];
> >> (str being the Base String)
>
> >> Hope it helps :-)
>
> >> Tom
>
> >> On 9/13/10 3:02 AM, Nikolay Klimchuk wrote:
>
> >> > I'm trying to understand why algorithm for calculation of
> >> > oauth_signature does not give me the same result as shown here:
> >> >http://dev.twitter.com/pages/xauth
>
> >> > In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
>
> >> > If I URL encode such result it's still very different from
> >> > yUDBrcMMm6ghqBEKCFKVoJPIacU%3D
>
> >> > I've tried different implementations, all of them give the same
> >> > result. After few hours of exercises with all this stuff I completely
> >> > run out of ideas, please help
>
> >> > // Test with input data taken from Twitter page
>
> >> > NSString *s= @"POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> >> > %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> >> > %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> >> > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> >> > %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> >> > %26x_auth_password%3D%2525%2526123%2521aZ%252B
> >> > %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant";
>
> >> > NSString *k = @"5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&";
>
> >> > NSString *signedSK = [NetworkManager base64forData:[NetworkManager
> >> > HMACSHA1withKey:k forString:s]];
>
> >> > // Source code
>
> >> > + (NSData *)HMACSHA1withKey:(NSString *)key forString:(NSString
> >> > *)string
> >> > {
> >> >    NSData *clearTextData = [string
> >> > dataUsingEncoding:NSUTF8StringEncoding];
> >> >    NSData *keyData = [key dataUsingEncoding:NSUTF8StringEncoding];
>
> >> >    uint8_t digest[CC_SHA1_DIGEST_LENGTH] = {0};
>
> >> >    CCHmacContext hmacContext;
> >> >    CCHmacInit(&hmacContext, kCCHmacAlgSHA1, keyData.bytes,
> >> > keyData.length);
> >> >    CCHmacUpdate(&hmacContext, clearTextData.bytes,
> >> > clearTextData.length);
> >> >    CCHmacFinal(&hmacContext, digest);
>
> >> >    return [NSData dataWithBytes:digest length:CC_SHA1_DIGEST_LENGTH];
> >> > }
>
> >> > //Sourcehttp://www.cocoadev.com/index.pl?BaseSixtyFour
>
> >> > + (NSString *)base64forData:(NSData *)data
> >> > {
> >> >     static const char encodingTable[] =
> >> > "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
>
> >> >     if ([data length] == 0)
> >> >         return @"";
>
> >> >     char *characters = malloc((([data length] + 2) / 3) * 4);
> >> >     if (characters == NULL)
> >> >         return nil;
> >> >     NSUInteger length = 0;
>
> >> >     NSUInteger i = 0;
> >> >     while (i < [data length])
> >> >     {
> >> >         char buffer[3] = {0,0,0};
> >> >         short bufferLength = 0;
> >> >         while (bufferLength < 3 && i < [data length])
> >> >                    buffer[bufferLength++] = ((char *)[data bytes])[i++];
>
> >> >         //  Encode the bytes in the buffer to four characters,
> >> > including padding "=" characters if necessary.
> >> >         characters[length++] = encodingTable[(buffer[0] & 0xFC) >> 2];
> >> >         characters[length++] = encodingTable[((buffer[0] & 0x03) << 4)
> >> > | ((buffer[1] & 0xF0) >> 4)];
> >> >         if (bufferLength > 1)
> >> >                    characters[length++] = encodingTable[((buffer[1] & 
> >> > 0x0F) << 2) |
> >> > ((buffer[2] & 0xC0) >> 6)];
> >> >         else characters[length++] = '=';
> >> >         if (bufferLength > 2)
> >> >                    characters[length++] = encodingTable[buffer[2] & 
> >> > 0x3F];
> >> >         else characters[length++] = '=';
> >> >     }
>
> >> >     return [[[

[twitter-dev] Re: Why is Basic Auth still enabled on some sources?

[Jeff Gladnick]

There was a very easy solution, IMHO, to the basic auth issue that I
am surprised twitter didn't consider.

1) Add a new field to user profile settings that is "Allow basic
authentication for API."  Set this to be false by default for all
users.  You can even set a scary message here discouraging its use.
2) If you try to post to this account with basic auth, it just wont
work, and will return a "basic auth is disabled" error.
3) Even basic users would be capable to switching this to true so
their app would work.

Its not too late twitter.

On Sep 13, 10:07 am, isaiah  wrote:
> The bonus is that it's a way to still use plain old curl for testing.
> Awesome!
>
> On Sep 13, 9:21 am, Dewald Pretorius  wrote:
>
> > They must have known that this was going to be discovered. We're
> > developers. We like building, testing, and breaking stuff.
>
> > Unequal applications of the rules. Happens all the time. Months after
> > you've disabled something at the request of Twitter, you find well-
> > known services that do exactly the same thing with apparent impunity
> > in a much worse form than you did.
>
> > On Sep 13, 10:40 am, funkatron  wrote:
>
> > > Read on this post:http://blog.nelhage.com/2010/09/dear-twitter/
>
> > > Tested just now:http://gist.github.com/577273
>
> > > If I pass "source=twitterandroid", it appears to work on all API
> > > methods.
>
> > > In light of basic auth being "disabled," why does this work?
>
> > > --
> > > Ed Finklerhttp://funkatron.com
> > > @funkatron
> > > AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com

-- 
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] Re: Why is Basic Auth still enabled on some sources?

[isaiah]

The bonus is that it's a way to still use plain old curl for testing.
Awesome!

On Sep 13, 9:21 am, Dewald Pretorius  wrote:
> They must have known that this was going to be discovered. We're
> developers. We like building, testing, and breaking stuff.
>
> Unequal applications of the rules. Happens all the time. Months after
> you've disabled something at the request of Twitter, you find well-
> known services that do exactly the same thing with apparent impunity
> in a much worse form than you did.
>
> On Sep 13, 10:40 am, funkatron  wrote:
>
>
>
> > Read on this post:http://blog.nelhage.com/2010/09/dear-twitter/
>
> > Tested just now:http://gist.github.com/577273
>
> > If I pass "source=twitterandroid", it appears to work on all API
> > methods.
>
> > In light of basic auth being "disabled," why does this work?
>
> > --
> > Ed Finklerhttp://funkatron.com
> > @funkatron
> > AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com

-- 
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] Re: Why is Basic Auth still enabled on some sources?

[Dewald Pretorius]

They must have known that this was going to be discovered. We're
developers. We like building, testing, and breaking stuff.

Unequal applications of the rules. Happens all the time. Months after
you've disabled something at the request of Twitter, you find well-
known services that do exactly the same thing with apparent impunity
in a much worse form than you did.

On Sep 13, 10:40 am, funkatron  wrote:
> Read on this post:http://blog.nelhage.com/2010/09/dear-twitter/
>
> Tested just now:http://gist.github.com/577273
>
> If I pass "source=twitterandroid", it appears to work on all API
> methods.
>
> In light of basic auth being "disabled," why does this work?
>
> --
> Ed Finklerhttp://funkatron.com
> @funkatron
> AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com

-- 
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] Is gardenhose being ramped up?

[John Kalucki]

We increased the Gardenhose on August 30, as announced here:
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/12ee7750a5255990
.

We haven't changed the proportion since. A Streaming API application should
always be prepared for accept spikes of at least three, if not four times as
large as daily peak traffic.

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




On Mon, Sep 13, 2010 at 8:43 AM, Sanjay  wrote:

> I just took a look at my bandwidth usage from last night to see the
> effect of the VMAs (dramatic BTW), and thought I'd check it out over
> the last week.  It looks like gardenhose has been ramping up since
> late Sept 10th/early Sept 11th.  Is this intentional?  Any idea where
> we're ending.  My DB isn't keeping up with this so I need to
> reorganize if we're going to keep at this level.  Help?  Thoughts?
>
> http://twitpic.com/2o3ewf
>
> Sanjay
>
> --
> 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] Is gardenhose being ramped up?

[Sanjay]

I just took a look at my bandwidth usage from last night to see the
effect of the VMAs (dramatic BTW), and thought I'd check it out over
the last week.  It looks like gardenhose has been ramping up since
late Sept 10th/early Sept 11th.  Is this intentional?  Any idea where
we're ending.  My DB isn't keeping up with this so I need to
reorganize if we're going to keep at this level.  Help?  Thoughts?

http://twitpic.com/2o3ewf

Sanjay

-- 
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] Re: Entities display_url and expanded_url

[Rich]

Hi Taylor

Thanks for the responds, thats great news.  I pass the tweet through
an automated linker and so I want to use expanded_url instead.

When you visit the link it substitutes it back to the original url
before it loads.  So for the end user they don't see anything
different at all.

So if the intention is for expanded_url to always accompany a url
(even if it might occasionally break) then my logic will work fine.

Richard

On Sep 13, 4:04 pm, Taylor Singletary 
wrote:
> Hi Rich,
>
> You can't be guaranteed to always have a display_url (there will be many
> historical tweets without it, or perhaps the service that negotiates
> display_urls will be down), so you should code defensively, making use of
> them when they are present but choosing an alternate display method when it
> is absent.
>
> display_url, as you've noted, is also a misnomer since the string contained
> within the field is technically not a URL, but just a string to display
> instead of the URL. expanded_url should always be safe to assume as actually
> being a URL.
>
> While it should be safe to assume that all t.co links will have an
> expanded_url as well as a display_url, I'd still code defensively in the
> event that something goes wrong.
>
> Thanks,
> Taylor
>
> On Sat, Sep 11, 2010 at 5:28 AM, Rich  wrote:
> > Hi
>
> > I have a question for the API team.  I notice that display_url doesn't
> > contain the protocol e.g. http:// or https:// yet expanded_url does.
>
> > Would I be safe to assume that a http://t.co/xx would
> > always contain an expanded_url as well as a display_url?
>
> > Richard
>
> > --
> > 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] XML hashtags missing

[Taylor Singletary]

Hi James,

We still have some intermittent issues with entities returning
consistently across tweets. We are working to fix this.

I would also recommend using include_entities=true, even though =1 should
work.

Thanks,
Taylor

On Mon, Sep 13, 2010 at 8:20 AM, james.eats.wo...@gmail.com <
james.eats.wo...@gmail.com> wrote:

> Has twitter changed there output for xml ?  below is one of the status
> that are returned through the request
>
> http://api.twitter.com/1/statuses/user_timeline.xml?include_entities=1&screen_name=superbreaker
> which does have entities; hash tags specifically returned on several
> status. however none as of the 9th of September like the one bellow
> anyone got any ideas on this would be greatly appreciated!
> I am developing in c# asp.net however this shouldn't be an issue as it
> appears to be the XML that is causing the issue...
>
>
> 
>  Wed Sep 08 15:27:44 + 2010
>  23923594634
>  iOS4 to be released today? http://bit.ly/b1Du5e I saw this at
> the weekend too... Bring on HDR photos! #apple #iphone
>   rel="nofollow">TweetDeck
>  false
>  
>  
>  false
>  
>  
>  false
>  
>6595462
>Tim Harper
>superbreaker
>East Central and Sarf London
>Creative Director of TheTin Ideas Activation Agency description>
>http://a3.twimg.com/profile_images/1115764091/
> SuperbreakerCrop_normal.png
> 
>http://www.thetin.net
>false
>101
>352726
>3E4415
>D02B55
>99CC33
>829D5E profile_sidebar_border_color>
>182
>Tue Jun 05 14:40:25 + 2007
>1
>0
>London
>http://s.twimg.com/a/1283564528/
> images/themes/theme5/bg.gif
> 
>false
>true
>false
>false
>false
>false
>317
>en
>false
>false
>4
>false
>  
>  
>  
>  
>  
> 
>
> --
> 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] XML hashtags missing

[james.eats.wo...@gmail.com]

Has twitter changed there output for xml ?  below is one of the status
that are returned through the request
http://api.twitter.com/1/statuses/user_timeline.xml?include_entities=1&screen_name=superbreaker
which does have entities; hash tags specifically returned on several
status. however none as of the 9th of September like the one bellow
anyone got any ideas on this would be greatly appreciated!
I am developing in c# asp.net however this shouldn't be an issue as it
appears to be the XML that is causing the issue...



  Wed Sep 08 15:27:44 + 2010
  23923594634
  iOS4 to be released today? http://bit.ly/b1Du5e I saw this at
the weekend too... Bring on HDR photos! #apple #iphone
  TweetDeck
  false
  
  
  false
  
  
  false
  
6595462
Tim Harper
superbreaker
East Central and Sarf London
Creative Director of TheTin Ideas Activation Agency
http://a3.twimg.com/profile_images/1115764091/
SuperbreakerCrop_normal.png
http://www.thetin.net
false
101
352726
3E4415
D02B55
99CC33
829D5E
182
Tue Jun 05 14:40:25 + 2007
1
0
London
http://s.twimg.com/a/1283564528/
images/themes/theme5/bg.gif
false
true
false
false
false
false
317
en
false
false
4
false
  
  
  
  
  


-- 
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] xAuth returning 401 error.

[Tom van der Woerdt]

On 9/13/10 1:16 PM, Josh Knowles wrote:
> Hm. Still having troubles with my iPhone app -- when I try to post
> using xAuth, I get a 401 error. Twitter claims the app has xAuth
> access on their end. Not sure what to do...
> 
> Anyone else experiencing this issue?
> 
> Thanks!
> 
> Josh Knowles
> http://auscillate.com

xAuth is part of OAuth, it simply exchanges usernames/passwords for
credentials. Posting tweets using xAuth is impossible. ;-)

401 usually means a signature error. What is the Base String you use?
(Most errors are in the Base String)

Tom

-- 
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] What is the status of profile image changes via API?

[Taylor Singletary]

Hi Raghu,

One thing I recommend checking is that you're using the supported URL scheme
for API-based profile image uploads,
http://api.twitter.com/1/account/update_profile_image.json

If you're using that end point and still having trouble, it might be helpful
to post the code you're using or a HTTP trace of the request cycle.

Thanks,
Taylor

On Mon, Sep 13, 2010 at 8:03 AM, CWorster  wrote:

> Hi Raghu,
>
> the profile image upload via API works fine. The new image is returned
> immediately. No caching issues.
>
> I'm using the PHP library from Matt Harris.
> http://github.com/themattharris/tmhOAuth
>
> --
> 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] XAuth signature error

[Tom van der Woerdt]

On 9/13/10 7:01 AM, Double K wrote:
> hi, my name is Kim.
> I will make XAuth module. So i need developer help.
> i make signature base string
> for example
> 
> POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> %26x_auth_password%3D%2525%2526123%2521aZ%252B
> %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant
> 
> this is dev.twitter.com example
> i saw it that oauth_signature is signature base string's hmac-sha1
> encoding and base64 encoding's result
> oauth_signature="yUDBrcMMm6ghqBEKCFKVoJPIacU%3D"
> is it right?
> i can't do this.
> somebody help me. T.T
> 
> Q1. i want to know signature base string's hmac-sha1 encoding result.
> Q2. oauth-signature="yUDBrcMMm6ghqBEKCFKVoJPIacU%3D" is it correct?
> 

Yes, that signature is correct, if you are using the sample keys.

Tom

-- 
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] Entities display_url and expanded_url

[Taylor Singletary]

Hi Rich,

You can't be guaranteed to always have a display_url (there will be many
historical tweets without it, or perhaps the service that negotiates
display_urls will be down), so you should code defensively, making use of
them when they are present but choosing an alternate display method when it
is absent.

display_url, as you've noted, is also a misnomer since the string contained
within the field is technically not a URL, but just a string to display
instead of the URL. expanded_url should always be safe to assume as actually
being a URL.

While it should be safe to assume that all t.co links will have an
expanded_url as well as a display_url, I'd still code defensively in the
event that something goes wrong.

Thanks,
Taylor


On Sat, Sep 11, 2010 at 5:28 AM, Rich  wrote:

> Hi
>
> I have a question for the API team.  I notice that display_url doesn't
> contain the protocol e.g. http:// or https:// yet expanded_url does.
>
> Would I be safe to assume that a http://t.co/xx would
> always contain an expanded_url as well as a display_url?
>
> Richard
>
> --
> 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] What is the status of profile image changes via API?

[CWorster]

Hi Raghu,

the profile image upload via API works fine. The new image is returned
immediately. No caching issues.

I'm using the PHP library from Matt Harris.
http://github.com/themattharris/tmhOAuth

-- 
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] Why is Basic Auth still enabled on some sources?

[funkatron]

Read on this post: http://blog.nelhage.com/2010/09/dear-twitter/

Tested just now: http://gist.github.com/577273

If I pass "source=twitterandroid", it appears to work on all API
methods.

In light of basic auth being "disabled," why does this work?

--
Ed Finkler
http://funkatron.com
@funkatron
AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com


-- 
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] xAuth returning 401 error.

[Josh Knowles]

Hm. Still having troubles with my iPhone app -- when I try to post
using xAuth, I get a 401 error. Twitter claims the app has xAuth
access on their end. Not sure what to do...

Anyone else experiencing this issue?

Thanks!

Josh Knowles
http://auscillate.com

-- 
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] xAuth token and secret not working for POST methods

[nattu]

Hi,

I am using Twitter xAuth to get tokens (my application is approved for
using xAuth). However the tokens do not have any write permissions, so
I cannot use any API that requires POST. I am getting '401
Unauthorized' error when accessing the APIs which requires POST. Note
that there are no issues when I am using oAuth.

Much appreciate your help on this. Thanks in advance.

Regards,
Nataraj

-- 
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] Using Tweetbox on authorized callback domains not working

[Kat]

I have placed a tweetbox onto a site here: http://www.ivaluethearts.org.uk/

I have also authorized 'http://ivaluethearts.org.uk/' as a Registered
Callback URL. But attempting to use the tweetbox from this url results
in a

"The provided callback url http://ivaluethearts.org.uk/ is not
authorized for the client registered to 'http://
www.ivaluethearts.org.uk'."

error.

Any help or advice on this issue would be very much appreciated.


Many thanks,
Kat

-- 
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] The new login operation with oAuth

[meni]

Hello
Since we worked till now with swx http://apiwiki.twitter.com/SWX+Twitter+API
we can't login any more from our application.
we are working with AS2 what the quick change we have to do to set it
back to work.
This is urgent for us
Thanks
Menachem
Flash Team Leder
at Unisfair.com
menac...@unisfair.com

-- 
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] Re: Opción para mostrar twitters

[arturogarrido]

Puedes usar listas, no tienes que seguir a las personas que esten en
la lista.

Saludos,

Arturo Garrido
Twitea.me

-- 
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] XAuth signature error

[Double K]

hi, my name is Kim.
I will make XAuth module. So i need developer help.
i make signature base string
for example

POST&https%3A%2F%2Fapi.twitter.com%2Foauth
%2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
%26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
%26x_auth_password%3D%2525%2526123%2521aZ%252B
%2528%2529456242134%26x_auth_username%3DtpFriendlyGiant

this is dev.twitter.com example
i saw it that oauth_signature is signature base string's hmac-sha1
encoding and base64 encoding's result
oauth_signature="yUDBrcMMm6ghqBEKCFKVoJPIacU%3D"
is it right?
i can't do this.
somebody help me. T.T

Q1. i want to know signature base string's hmac-sha1 encoding result.
Q2. oauth-signature="yUDBrcMMm6ghqBEKCFKVoJPIacU%3D" is it correct?

-- 
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] twurl error… I think

[Tom van der Woerdt]

Sounds like a firewall error. You should check your firewalls etc to
allow api.twitter.com.

Tom


On Mon, 13 Sep 2010 08:04:37 -0400, TJ Luoma  wrote:
> Can anyone explain what this output from twurl is trying to tell me?
> 
> $ twurl -t "/1/statuses/user_timeline/amazondeals.rss"
> 
> opening connection to api.twitter.com...
> opened
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:586:in
> `connect': SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read
> finished A (OpenSSL::SSL::SSLError)
>from
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:586:in
> `connect'
>from
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:553:in
> `do_start'
>from
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:542:in
> `start'
>from
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:1035:in
> `request'
>from
> /Library/Ruby/Gems/1.8/gems/oauth-0.4.2/lib/oauth/consumer.rb:164:in
> `request'
>from
> /Library/Ruby/Gems/1.8/gems/oauth-0.4.2/lib/oauth/tokens/consumer_token.rb:25:in
> `request'
>from
> /Library/Ruby/Gems/1.8/gems/oauth-0.4.2/lib/oauth/tokens/access_token.rb:11:in
> `request'
>from
> /Library/Ruby/Gems/1.8/gems/oauth-0.4.2/lib/oauth/tokens/access_token.rb:24:in
> `get'
>from
> /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/oauth_client.rb:68:in
> `get'
>from
> /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/oauth_client.rb:75:in
> `send'
>from
> /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/oauth_client.rb:75:in
> `perform_request_from_options'
>from
> /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/request_controller.rb:13:in
> `perform_request'
>from
> /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/request_controller.rb:9:in
> `dispatch'
>from
> /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/abstract_command_controller.rb:7:in
> `dispatch'
>from
> /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/cli.rb:31:in
> `dispatch'
>from
> /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/cli.rb:14:in
> `run'
>from /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/twurl:4
>from /usr/bin/twurl:19:in `load'
>from /usr/bin/twurl:19
> 
> That was it.

-- 
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] twurl error… I think

[TJ Luoma]

Can anyone explain what this output from twurl is trying to tell me?

$ twurl -t "/1/statuses/user_timeline/amazondeals.rss"

opening connection to api.twitter.com...
opened
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:586:in
`connect': SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read
finished A (OpenSSL::SSL::SSLError)
   from 
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:586:in
`connect'
   from 
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:553:in
`do_start'
   from 
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:542:in
`start'
   from 
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:1035:in
`request'
   from /Library/Ruby/Gems/1.8/gems/oauth-0.4.2/lib/oauth/consumer.rb:164:in
`request'
   from 
/Library/Ruby/Gems/1.8/gems/oauth-0.4.2/lib/oauth/tokens/consumer_token.rb:25:in
`request'
   from 
/Library/Ruby/Gems/1.8/gems/oauth-0.4.2/lib/oauth/tokens/access_token.rb:11:in
`request'
   from 
/Library/Ruby/Gems/1.8/gems/oauth-0.4.2/lib/oauth/tokens/access_token.rb:24:in
`get'
   from 
/Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/oauth_client.rb:68:in
`get'
   from 
/Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/oauth_client.rb:75:in
`send'
   from 
/Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/oauth_client.rb:75:in
`perform_request_from_options'
   from 
/Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/request_controller.rb:13:in
`perform_request'
   from 
/Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/request_controller.rb:9:in
`dispatch'
   from 
/Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/abstract_command_controller.rb:7:in
`dispatch'
   from 
/Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/cli.rb:31:in
`dispatch'
   from 
/Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/../lib/twurl/cli.rb:14:in
`run'
   from /Library/Ruby/Gems/1.8/gems/twurl-0.6.1/bin/twurl:4
   from /usr/bin/twurl:19:in `load'
   from /usr/bin/twurl:19

That was it.

-- 
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] Re: Is there stats for API clients usage?

[rhysmeister]

Try this... http://twittersource.info/

On Sep 12, 7:56 pm, "D. Smith"  wrote:
> Hello! I know Twitter published some statistics on how users generally
> use Twitter. I am looking for per-app stats, at least for the top 100
> or so apps.
>
> Is there a stat like this available anywhere? I am just researching
> the popularity of various API based Twitter clients, very interested
> to know top 10 in Web, top 10 in Mobile.
>
> I hope someone has this stat, I am sure Twitter dev team has access to
> stats like this, please share it with the rest of us.
>
> 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?hl=en

Re: [twitter-dev] Re: iPhone::Incorrect oauth_signature for xAuth?

[Tom van der Woerdt]

Oh, hehe, good point. That's because my Base String has one extra
urlencoded '&' on the end, and that shouldn't be there.

Tom


On Mon, 13 Sep 2010 04:18:06 -0700 (PDT), Nikolay Klimchuk
 wrote:
> Thank you Tom
> 
> I will try your algorithm and compare results.
> Quick question: why you do this [str substringToIndex:[str
> length]-3] ?
> 
> Nikolay Klimchuk
> 
> On Sep 13, 2:46 am, Tom van der Woerdt  wrote:
>> Hi Nikolay,
>>
>> The first part of your code looks fine. You may, however, like to do
>> some debugging on the HMAC part - it looks a bit too simple to me.
>>
>> This works :
>>         NSString *compKey = [NSString 
>> stringWithFormat:@"%@&%@",secret,userSecret];
>>         const char *cKey = [compKey 
>> cStringUsingEncoding:NSUTF8StringEncoding];
>>         const char *cData = [[str substringToIndex:[str length]-3]
>> cStringUsingEncoding:NSUTF8StringEncoding];
>>         unsigned char cHMAC[CC_SHA1_DIGEST_LENGTH];
>>         CCHmac(kCCHmacAlgSHA1, cKey, strlen(cKey), cData, strlen(cData), 
>> cHMAC);
>>         NSData *HMAC = [[NSData alloc] initWithBytes:cHMAC 
>> length:sizeof(cHMAC)];
>> (str being the Base String)
>>
>> Hope it helps :-)
>>
>> Tom
>>
>> On 9/13/10 3:02 AM, Nikolay Klimchuk wrote:
>>
>>
>>
>> > I'm trying to understand why algorithm for calculation of
>> > oauth_signature does not give me the same result as shown here:
>> >http://dev.twitter.com/pages/xauth
>>
>> > In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
>>
>> > If I URL encode such result it's still very different from
>> > yUDBrcMMm6ghqBEKCFKVoJPIacU%3D
>>
>> > I've tried different implementations, all of them give the same
>> > result. After few hours of exercises with all this stuff I completely
>> > run out of ideas, please help
>>
>> > // Test with input data taken from Twitter page
>>
>> > NSString *s= @"POST&https%3A%2F%2Fapi.twitter.com%2Foauth
>> > %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
>> > %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
>> > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
>> > %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
>> > %26x_auth_password%3D%2525%2526123%2521aZ%252B
>> > %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant";
>>
>> > NSString *k = @"5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&";
>>
>> > NSString *signedSK = [NetworkManager base64forData:[NetworkManager
>> > HMACSHA1withKey:k forString:s]];
>>
>> > // Source code
>>
>> > + (NSData *)HMACSHA1withKey:(NSString *)key forString:(NSString
>> > *)string
>> > {
>> >    NSData *clearTextData = [string
>> > dataUsingEncoding:NSUTF8StringEncoding];
>> >    NSData *keyData = [key dataUsingEncoding:NSUTF8StringEncoding];
>>
>> >    uint8_t digest[CC_SHA1_DIGEST_LENGTH] = {0};
>>
>> >    CCHmacContext hmacContext;
>> >    CCHmacInit(&hmacContext, kCCHmacAlgSHA1, keyData.bytes,
>> > keyData.length);
>> >    CCHmacUpdate(&hmacContext, clearTextData.bytes,
>> > clearTextData.length);
>> >    CCHmacFinal(&hmacContext, digest);
>>
>> >    return [NSData dataWithBytes:digest length:CC_SHA1_DIGEST_LENGTH];
>> > }
>>
>> > //Sourcehttp://www.cocoadev.com/index.pl?BaseSixtyFour
>>
>> > + (NSString *)base64forData:(NSData *)data
>> > {
>> >     static const char encodingTable[] =
>> > "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
>>
>> >     if ([data length] == 0)
>> >         return @"";
>>
>> >     char *characters = malloc((([data length] + 2) / 3) * 4);
>> >     if (characters == NULL)
>> >         return nil;
>> >     NSUInteger length = 0;
>>
>> >     NSUInteger i = 0;
>> >     while (i < [data length])
>> >     {
>> >         char buffer[3] = {0,0,0};
>> >         short bufferLength = 0;
>> >         while (bufferLength < 3 && i < [data length])
>> >                    buffer[bufferLength++] = ((char *)[data bytes])[i++];
>>
>> >         //  Encode the bytes in the buffer to four characters,
>> > including padding "=" characters if necessary.
>> >         characters[length++] = encodingTable[(buffer[0] & 0xFC) >> 2];
>> >         characters[length++] = encodingTable[((buffer[0] & 0x03) << 4)
>> > | ((buffer[1] & 0xF0) >> 4)];
>> >         if (bufferLength > 1)
>> >                    characters[length++] = encodingTable[((buffer[1] & 
>> > 0x0F) << 2) |
>> > ((buffer[2] & 0xC0) >> 6)];
>> >         else characters[length++] = '=';
>> >         if (bufferLength > 2)
>> >                    characters[length++] = encodingTable[buffer[2] & 0x3F];
>> >         else characters[length++] = '=';
>> >     }
>>
>> >     return [[[NSString alloc] initWithBytesNoCopy:characters
>> > length:length encoding:NSASCIIStringEncoding freeWhenDone:YES]
>> > autorelease];
>> > }

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

[twitter-dev] Re: iPhone::Incorrect oauth_signature for xAuth?

[Nikolay Klimchuk]

Thank you Tom

I will try your algorithm and compare results.
Quick question: why you do this [str substringToIndex:[str
length]-3] ?

Nikolay Klimchuk

On Sep 13, 2:46 am, Tom van der Woerdt  wrote:
> Hi Nikolay,
>
> The first part of your code looks fine. You may, however, like to do
> some debugging on the HMAC part - it looks a bit too simple to me.
>
> This works :
>         NSString *compKey = [NSString 
> stringWithFormat:@"%@&%@",secret,userSecret];
>         const char *cKey = [compKey 
> cStringUsingEncoding:NSUTF8StringEncoding];
>         const char *cData = [[str substringToIndex:[str length]-3]
> cStringUsingEncoding:NSUTF8StringEncoding];
>         unsigned char cHMAC[CC_SHA1_DIGEST_LENGTH];
>         CCHmac(kCCHmacAlgSHA1, cKey, strlen(cKey), cData, strlen(cData), 
> cHMAC);
>         NSData *HMAC = [[NSData alloc] initWithBytes:cHMAC 
> length:sizeof(cHMAC)];
> (str being the Base String)
>
> Hope it helps :-)
>
> Tom
>
> On 9/13/10 3:02 AM, Nikolay Klimchuk wrote:
>
>
>
> > I'm trying to understand why algorithm for calculation of
> > oauth_signature does not give me the same result as shown here:
> >http://dev.twitter.com/pages/xauth
>
> > In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
>
> > If I URL encode such result it's still very different from
> > yUDBrcMMm6ghqBEKCFKVoJPIacU%3D
>
> > I've tried different implementations, all of them give the same
> > result. After few hours of exercises with all this stuff I completely
> > run out of ideas, please help
>
> > // Test with input data taken from Twitter page
>
> > NSString *s= @"POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> > %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> > %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> > %26x_auth_password%3D%2525%2526123%2521aZ%252B
> > %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant";
>
> > NSString *k = @"5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&";
>
> > NSString *signedSK = [NetworkManager base64forData:[NetworkManager
> > HMACSHA1withKey:k forString:s]];
>
> > // Source code
>
> > + (NSData *)HMACSHA1withKey:(NSString *)key forString:(NSString
> > *)string
> > {
> >    NSData *clearTextData = [string
> > dataUsingEncoding:NSUTF8StringEncoding];
> >    NSData *keyData = [key dataUsingEncoding:NSUTF8StringEncoding];
>
> >    uint8_t digest[CC_SHA1_DIGEST_LENGTH] = {0};
>
> >    CCHmacContext hmacContext;
> >    CCHmacInit(&hmacContext, kCCHmacAlgSHA1, keyData.bytes,
> > keyData.length);
> >    CCHmacUpdate(&hmacContext, clearTextData.bytes,
> > clearTextData.length);
> >    CCHmacFinal(&hmacContext, digest);
>
> >    return [NSData dataWithBytes:digest length:CC_SHA1_DIGEST_LENGTH];
> > }
>
> > //Sourcehttp://www.cocoadev.com/index.pl?BaseSixtyFour
>
> > + (NSString *)base64forData:(NSData *)data
> > {
> >     static const char encodingTable[] =
> > "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
>
> >     if ([data length] == 0)
> >         return @"";
>
> >     char *characters = malloc((([data length] + 2) / 3) * 4);
> >     if (characters == NULL)
> >         return nil;
> >     NSUInteger length = 0;
>
> >     NSUInteger i = 0;
> >     while (i < [data length])
> >     {
> >         char buffer[3] = {0,0,0};
> >         short bufferLength = 0;
> >         while (bufferLength < 3 && i < [data length])
> >                    buffer[bufferLength++] = ((char *)[data bytes])[i++];
>
> >         //  Encode the bytes in the buffer to four characters,
> > including padding "=" characters if necessary.
> >         characters[length++] = encodingTable[(buffer[0] & 0xFC) >> 2];
> >         characters[length++] = encodingTable[((buffer[0] & 0x03) << 4)
> > | ((buffer[1] & 0xF0) >> 4)];
> >         if (bufferLength > 1)
> >                    characters[length++] = encodingTable[((buffer[1] & 0x0F) 
> > << 2) |
> > ((buffer[2] & 0xC0) >> 6)];
> >         else characters[length++] = '=';
> >         if (bufferLength > 2)
> >                    characters[length++] = encodingTable[buffer[2] & 0x3F];
> >         else characters[length++] = '=';
> >     }
>
> >     return [[[NSString alloc] initWithBytesNoCopy:characters
> > length:length encoding:NSASCIIStringEncoding freeWhenDone:YES]
> > autorelease];
> > }

-- 
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] What is the status of profile image changes via API?

[Raghu Prasad]

Hi! Twitter Devs,

The profile image update via API is still not working in my test environment.
Is there any end date planned to fix this bug?

Can anyone confirm that they are able to update their profile image via
API using OAuth? BTW, up to a couple of months back, my code for doing
this was working perfectly. Then I was told that as part of streamlining
the image update scheme, there had been some major code changes.
Since then this functionality is found to be broken.

Apparently Twitter is remembering the old profile images. They are
stacked somewhere. If I click on the delete image link (even if no
image is being shown currently) on profile page, the earlier profile
image pops up.

Thanks.
Raghu

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