[twitter-dev] Re: Posting non-English Characters using OAuth
Done! It's now updating status successfully for ascii as well as non-ascii characters.. the problem was my oAuth.. i downloaded the latest code and it's working flawlessly.. thx for ur help! On Nov 2, 4:27 pm, Kalpesh wrote: > I have tried two things to get my non-english characters status update > to work: > 1.) Using meta tag in the head as content="application/x-www-form-urlencoded; charset=UTF-8" /> > 2.) Using utf8_encode for status and posting > > None of the above works. I get "incorrect signature" trying to post > non-english characters. English characters works fine. > I am able to update non-english status with direct status posting from > cURL, problem is with oAuth.. > Can anyone provide a working example code using oAuth for this? > > On Oct 29, 12:35 am, Cameron Kaiser wrote: > > > > What encoding function to use for postingnon-englishcharacters ?? > > > i am using urlencode but it is not postingnon-englishcharacters to > > > twitter > > > Are you properly encoding the characters as UTF-8? That should occur > > before you URL-encode your payload. > > > -- > > > > personal:http://www.cameronkaiser.com/-- > > Cameron Kaiser * Floodgap Systems *www.floodgap.com*ckai...@floodgap.com > > -- The gift of death metal does not smile on the good looking. -- S.B. #141 > > ---
[twitter-dev] Re: Posting non-English Characters using OAuth
I have tried two things to get my non-english characters status update to work: 1.) Using meta tag in the head as 2.) Using utf8_encode for status and posting None of the above works. I get "incorrect signature" trying to post non-english characters. English characters works fine. I am able to update non-english status with direct status posting from cURL, problem is with oAuth.. Can anyone provide a working example code using oAuth for this? On Oct 29, 12:35 am, Cameron Kaiser wrote: > > What encoding function to use for postingnon-englishcharacters ?? > > i am using urlencode but it is not postingnon-englishcharacters to > > twitter > > Are you properly encoding the characters as UTF-8? That should occur > before you URL-encode your payload. > > -- > personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com > -- The gift of death metal does not smile on the good looking. -- S.B. #141 > ---
[twitter-dev] Re: Posting non-English Characters using OAuth
What encoding function to use for posting non-english characters ?? i am using urlencode but it is not posting non-english characters to twitter On Oct 27, 2:15 pm, Kalpesh wrote: > Hi Mageuzi, can you please shed more light what you exactly did? > I am trying to post non-ascii status through api and it shows > "incorrect signature". > ascii characters are posted successfully. > > On Sep 20, 1:55 am, Mageuzi wrote: > > > Thanks for the response, Brian :) After a bit more debugging and > > research, I found the problem. In hindsight it's obvious, but I was > > putting too much faith into how the characters were being encoded. > > That "%65E5%672C%72AC" was completely incorrect, and instead the > > individual bytes needed to be encoded and sent to twitter. Once I > > changed the oAuth code to do that, it's working flawlessly. Thanks > > again for your response! > > > On Sep 18, 2:59 pm, "Brian Smith" wrote: > > > > Mageuzi wrote: > > > > I'm sorry for posting a follow up so soon, but I spent another few > > > > hours trying to debug this again last night, and still without > > > > success. It seems to be encoding the characters properly (%65E5%672C > > > > %72AC in this case), and so I assume it is generating the signature > > > > properly. After all, it works perfectly fine with English characters. > > > > So any guidance would be much appreciated, I'm running out of things > > > > to check. > > > > > Thank you again in advance. > > > > It probably isn't generating the signature properly. Try using a > > > different library to post the same message and likely you will find that > > > they are calculating the signature differently. Calculating bad > > > signatures for non-ASCII characters is probably the most common bug in > > > OAuth libraries, because the authors often test with ASCII characters but > > > not non-ASCII characters. If the library you are using has a mechanism > > > for you to get the signature base string, use that mechanism to retrieve > > > it and post it here. > > > > Also, try using a different OAuth library. > > > > がんばってください! > > > > - Brian
[twitter-dev] Re: Posting non-English Characters using OAuth
Hi Mageuzi, can you please shed more light what you exactly did? I am trying to post non-ascii status through api and it shows "incorrect signature". ascii characters are posted successfully. On Sep 20, 1:55 am, Mageuzi wrote: > Thanks for the response, Brian :) After a bit more debugging and > research, I found the problem. In hindsight it's obvious, but I was > putting too much faith into how the characters were being encoded. > That "%65E5%672C%72AC" was completely incorrect, and instead the > individual bytes needed to be encoded and sent to twitter. Once I > changed the oAuth code to do that, it's working flawlessly. Thanks > again for your response! > > On Sep 18, 2:59 pm, "Brian Smith" wrote: > > > Mageuzi wrote: > > > I'm sorry for posting a follow up so soon, but I spent another few > > > hours trying to debug this again last night, and still without > > > success. It seems to be encoding the characters properly (%65E5%672C > > > %72AC in this case), and so I assume it is generating the signature > > > properly. After all, it works perfectly fine with English characters. > > > So any guidance would be much appreciated, I'm running out of things > > > to check. > > > > Thank you again in advance. > > > It probably isn't generating the signature properly. Try using a different > > library to post the same message and likely you will find that they are > > calculating the signature differently. Calculating bad signatures for > > non-ASCII characters is probably the most common bug in OAuth libraries, > > because the authors often test with ASCII characters but not non-ASCII > > characters. If the library you are using has a mechanism for you to get the > > signature base string, use that mechanism to retrieve it and post it here. > > > Also, try using a different OAuth library. > > > がんばってください! > > > - Brian
[twitter-dev] Re: Announcing TweetHook.com
I just had a look at it. Great! Best luck Chad! On Sep 29, 10:39 pm, Chad Etzel wrote: > ** DISCLAIMER ** - This is not officially affiliated with Twitter. I > am writing from my personal gmail account. No Twitter endorsement > implied. ** > > I have just launched TweetHook, a Twitter Search "ping" service that > will push search results to user defined webhook/callback URLs. I know > gnip provides something like this already, but I have designed > TweetHook to be a better fit for Twitter Search data. > > Please check it out:https://tweethook.com/ > > Feedback welcome. > > -Chad
[twitter-dev] Re: How many Apps can we register under one account?
Well while developing, few things are not meant to be used but when it becomes open to the world people start using them the way they like. Before initiating this thread I read the API rules and found nothing about Naming and Using the apps. Can't I start offering a free service where people can post their status using my API on my site having names which they can find useful? It could be a great experience if this is allowed as people are now restricted to only "web" or some sites API name. Just imagine! Thanks. On Sep 29, 10:17 am, Chad Etzel wrote: > Hi Kalpesh, > > While creative, the app link was not meant to be used in that manner. > We are discussing internally that OAuth app registration will > eventually have to be screened to prevent squatting and/or abuse. I'm > not sure that apps named "home" or "work" would pass that screen :) > > -Chad > > On Tue, Sep 29, 2009 at 1:09 AM, Kalpesh wrote: > > > Hi Chad, > > > I would not register hundred apps but dozen is common i think.. > > Can my account get suspended for having many applications (may be for > > 25)?? > > i am not into name-squattering or so, but i am definitely interested > > in having more apps and using different apps related to my status. > > e.g. i may post a status like "tweeting from my home" and having > > "home" app linked to it in the from field of status. I don't see any > > kind of issue in that, what do you think? > > > Thanks.
[twitter-dev] Re: How many Apps can we register under one account?
Hi Chad, I would not register hundred apps but dozen is common i think.. Can my account get suspended for having many applications (may be for 25)?? i am not into name-squattering or so, but i am definitely interested in having more apps and using different apps related to my status. e.g. i may post a status like "tweeting from my home" and having "home" app linked to it in the from field of status. I don't see any kind of issue in that, what do you think? Thanks.
[twitter-dev] How many Apps can we register under one account?
Hi. I am a developer and want to know is there any limit for registering an app per single account? I am developing apps and I want one app that can only be used by me and my friends, while others have another app for updating status, etc.. Thanks!
