[twitter-dev] Re: Update status "d" returns success response but doesn't show up on web

thanks Matt... I can now stop chasing a ghost On Jun 24, 5:28 pm, Matt Harris wrote: > Hi, > > This is expected behavior and is caused by the SMS commands. You can find a > complete list of the commands and their aliases on our help site: >    https://support.twitter.com/entries/14020-official-tw

Re: [twitter-dev] Re: Update status "d" returns success response but doesn't show up on web

Hi, This is expected behavior and is caused by the SMS commands. You can find a complete list of the commands and their aliases on our help site: https://support.twitter.com/entries/14020-official-twitter-text-commands Best, @themattharris

[twitter-dev] Re: Update status "d" returns success response but doesn't show up on web

'w' is another On May 13, 10:34 am, "e.p.c." wrote: > On May 13, 6:29 am, SN Testing wrote: > > > when update status with one character "d" returns success response but > > the new status doesn't show up on web; when update status with "a" or > > "b" or "c" or "e", it shows up on web, so the cha

[twitter-dev] Re: Update status "d" returns success response but doesn't show up on web

On May 13, 6:29 am, SN Testing wrote: > when update status with one character "d" returns success response but > the new status doesn't show up on web; when update status with "a" or > "b" or "c" or "e", it shows up on web, so the character "d" is black > listed? "d' as the first non-blank byte i

[twitter-dev] Re: Update on Whitelisting

It may sound foolish, but some of us coded our apps a couple years ago, improved them up to production readiness and then released and moved on to something else. Each of these mayor changes would in theory make one reread all this old code and find where one uses whatever you plan to change this t

[twitter-dev] Re: Update on Whitelisting

This is the message I received yesterday from Twitter Support: sutorius, Feb-11 10:40 am (PST): Hey Brian, In the short amount of time since you've written in, our director of Platform, Ryan Sarver, has posted an update on whitelisting and that we will no longer be approving such requests: http:/

Re: [twitter-dev] Re: Update on Whitelisting

"Whitelisting does not remove the daily update and follower limits associated with POST requests; these limits are managed on a per user basis." Elevated DM limits are separate from the REST API whitelisting. It is possible that Twitter is no longer providing access to elevated DM limits as well b

[twitter-dev] Re: Update on Whitelisting

I disagree, Abraham. I requested whitelisting for my app because I needed more than 250 DMs per day. Twitter granted my request and my limit was increased considerably. This may be that Twitter did not increase DMs as a default. But at one time, if requested and justified, they would. This is why

Re: [twitter-dev] Re: Update on Whitelisting

Whitelisting never impacted DM limits or Search API limits. Niether of those are affected by @rsarver's announcement. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask

[twitter-dev] Re: Update on Whitelisting

I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean wrote: > Hey Taylor, what does this mean for DM limits and what’s the new path towards > getting those limit increased for new accounts? > > Trevor Dean | Director > big time design & communication Inc. > 647 234 8198 > > V

[twitter-dev] Re: Update on Whitelisting

The one thing I am missing in this announcement is how this affects the rate limit of a non-authenticated request to the REST search API? Thanks, Ben -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhance

Re: [twitter-dev] Re: Update on Whitelisting

Hi Ian, One step at at time. The server is experimental, which is why it isn't documented anywhere. I should have made that clear. Your feedback will let us know how it's performing. Because the server is hosting a cached version of the trends data you shouldn't find any issues with the rate limi

[twitter-dev] Re: Update on Whitelisting

Hey Ed! I hope you can use Twendr! Yes this is on the five-minute cycle like the main Trending Topics feed. send me money and I'll create a "Promoted" trends just for you :) (hu...) Ian On Feb 10, 8:48 pm, "M. Edward (Ed) Borasky" wrote: >  On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris

[twitter-dev] Re: Update on Whitelisting

Thanks Matt! the trends.api.twitter.com server is working great. Question : what are the Rate Limit restrictions against that server? I am being very careful to respect the "as_of" time stamp for last request against a specific WOEID, but give 42 locations (the world plus 41 counties and cities)

Re: [twitter-dev] Re: Update on Whitelisting

I have been reading through the documentation for the stream api and the user stream api and I'm not sure why everyone is getting so upset about. It looks like this is going to benefit developers and allow Twitter to maintain a more stable environment which is a good thing for us. I understand th

Re: [twitter-dev] Re: Update on Whitelisting

Yup that certainly clarifies and thanks for the #newtwitter stats, it's something I've been very curious about (and I'm sure others as well)! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tr

Re: [twitter-dev] Re: Update on Whitelisting

On Thu, 10 Feb 2011 18:46:46 -0800, Ryan Sarver wrote: Orian, You should definitely plan on working within 350/hr for the forseeable future. FWIW, we have watched #newtwitter usage and an average session uses between 80-120 rq/hr. Interesting - I had an incident last week where I was running

Re: [twitter-dev] Re: Update on Whitelisting

Orian, You should definitely plan on working within 350/hr for the forseeable future. FWIW, we have watched #newtwitter usage and an average session uses between 80-120 rq/hr. Hope that helps clarify. Best, Ryan -- Ryan Sarver @rsarver On Thu, Feb 10, 2011 at 6:17

[twitter-dev] Re: Update on Whitelisting

Yes, Do tell. I have a whitelisted app, but came to the realization that I needed to switch to IP based so that all users of the application would have a higher DM limit--critical as my app is a social learning tool for mobile users. Now it looks like my project is dead in the water. Having each pe

[twitter-dev] Re: Update on Whitelisting

Ryan et al, thanks for the update on this. Shall we also take this to mean 350 is the definitive cap on rate limits for the foreseeable future? This certainly seems to be implied but since the spirit of this update seems to be to remove ambiguity, I think a clear statement that Twitter is no lon

Re: [twitter-dev] Re: Update on Whitelisting

Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design & communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information On 2011-02-10, at 8:48 PM, "M. Edward (

Re: [twitter-dev] Re: Update on Whitelisting

On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any

Re: [twitter-dev] Re: Update on Whitelisting

Hi Ian, For trends you might like to try our trends.api.twitter.com server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. To use it just

Re: [twitter-dev] Re: Update on Whitelisting

EXACTLY, i posted my opinion, result? Luckily we dont use this shit matt/tayor: an app suspended. On Feb 10, 2011, at 7:19 PM, Fishst1k wrote: > Quick question, are the whitelists IP based? It's been a couple years > since we requested the whitelisting, which was granted, but I am > curious ho

[twitter-dev] Re: Update on Whitelisting

Quick question, are the whitelists IP based? It's been a couple years since we requested the whitelisting, which was granted, but I am curious how that will affect us if we add more IP ranges to our servers? Thanks, Ben -- Twitter developer documentation and resources: http://dev.twitter.com/do

[twitter-dev] Re: Update on Whitelisting

Well this is disappointing. 350 is not 20,000. I have one little twitter app (using the trends api) and I need around 800 requests per hour to get the data. This and a few other ideas I had just died. These are all small side projects with limited opportunities for monetization or funding. The

[twitter-dev] Re: Update

@Sheikh145: seriously...? -- 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.c

Re: [twitter-dev] Re: Update on Twifficiency

its not my reply dear i want the complete api and code to share my website images to my twitter account thanking you On Thu, Aug 19, 2010 at 3:16 AM, Daniel Ribeiro wrote: > It would be nice to have something that make things clearer to the > user that the requesting app is requesting write

Re: [twitter-dev] Re: Update on Twifficiency

My opinion is that twitter is trying to keep it intentionally simple for the benefit of apps. for Joe Regular, more options than allow / deny is going to create confusion and apps will suffer. Its pretty clear that if you tweet on behalf of users without consent there will be confusion/anger and

[twitter-dev] Re: Update on Twifficiency

What I'd actually like to see is some granularity in the oAuth permissions that go beyond binary "has complete access: DENY|ALLOW", and this would also solve this problem. Surprising users when an app auto-tweets is one thing, but I'm more concerned about a given app reading my DM's, for example (

Re: [twitter-dev] Re: Update on Twifficiency

+1 ... see previous email ... although I don't think Twitter necessarily needs to do that - it's really the app developer's responsibility to document what it's supposed to do and how to tell when it's misbehaving. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znme

[twitter-dev] Re: Update on Twifficiency

It would be nice to have something that make things clearer to the user that the requesting app is requesting write rights. Like a big red warning on the Deny/allow page. On Aug 18, 6:17 pm, Tom van der Woerdt wrote: > +1 > > On 8/18/10 10:55 PM, Eric Marden - API Hacker wrote: > > > On behalf o

Re: [twitter-dev] Re: Update on Missing tweets from Profile page issue

Hrm. Can you open a ticket at twitter.com/help, and let me know the ID? Is anybody else seeing this? ---Mark http://twitter.com/mccv On Thu, Apr 15, 2010 at 6:39 PM, Adriano wrote: > Sorry, but I'm still with that issue. > > Can anyone check that? > > Greetings! > > On Apr 4, 11:30 pm, "A

[twitter-dev] Re: Update on Missing tweets from Profile page issue

Sorry, but I'm still with that issue. Can anyone check that? Greetings! On Apr 4, 11:30 pm, "Adriano R." wrote: > Hello, > > Anyone know what might be happening in this issue? > > Greetings! > > 2010/3/31 Adriano R. > > > > > Mark, > > > My twitter is @adrossetto > > > I have some tweets betwe

[twitter-dev] Re: UPDATE: Social Graph API Deprecation

Our application requires full social graph dump. One thing that I am not clear from the http://groups.google.com/group/twitter-api-announce/browse_thread/thread/a0ba66db0e86941d - is only pagination is depreciated or the use of cursors is made mandatory? Suppose if I want full social graph of fol

Re: [twitter-dev] Re: Update profile image API using OAuth

On Mon, Jan 18, 2010 at 10:54 AM, Raffi Krikorian wrote: > >> if using OS X, and don't want to deal with raw tcpdump, then i can also > recommend "packet peeper" (http://sourceforge.net/projects/packetpeeper/). > > I use wireshark for the same. tip: you may need to chmod/chown your /dev/bpf devic

[twitter-dev] Re: Update profile image API using OAuth

Ok people. Finally managed to crack it. Thanks to Raffi for sharing the raw text of the request. While working this API i figured out there are very less resources available on Internet with regards to the usage of multipart with OAuth and there is lot of confusion and misleading data. I will shar

[twitter-dev] Re: Update profile image API using OAuth

Please someone at least share the raw text of a successful request to this API via OAuth. I will compare my request and see what I need to do

[twitter-dev] Re: UPDATE: Social Graph API Deprecation

I have two use cases: 1. Generating a list of all friends and followers. 2. Downloading the most recent 200 tweets of all friends and followers. The existing API functionality is adequate for the first. The second depends more on the rate limiting than the functionality. Right now, I have about 5

[twitter-dev] Re: UPDATE: Social Graph API Deprecation

My use cases for the Social Graph API: * Figure out mutual followers vs one-way followers, namely for my Tweepsect application: http://tweepsect.com/ This requires a full graph dump, unless you include a parameter in the statuses/{friends,followers} API calls that indicate whether said friend is

[twitter-dev] Re: Update Profile Background using oauth

It does not seems to be OATH problem since user gets logged-in fine but there is some issue while setting/uploading background.. If its OATH problem, it gave 'Invalid OATH signature Error' On Nov 17, 6:16 am, jmathai wrote: > Which library are you using?  Looking at this line: > $args = array('

[twitter-dev] Re: Update Profile Background using oauth

Which library are you using? Looking at this line: $args = array('@image' => '@'.$temp_img); it appears you might be using twitter-async. On Nov 15, 9:51 pm, stevie wrote: > Hi All, >           Update profile background using twitter api is working fine > with username and password but on oaut

[twitter-dev] Re: Update Profile Background using oauth

You can use this to debug your signing process and find out where it's going awry: http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ On Nov 15, 9:51 pm, stevie wrote: > Hi All, >           Update profile background using twitter api is working fine > with username

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

John, thanx for your comment over at groovyconsole.appspot.com - http://groovyconsole.appspot.com/view.groovy?id=19003 In case you do not get updates on comments there, let me ask my main question again. This would make my (our) lives a lot easier when it comes to retweet tracking, still it woul

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

I'll update the Wiki to reflect the new reality. Retweets will begin to flow through all /1/statuses/* resources soon -- in advance of the full retweet launch. This will give developers time to test and deploy features in advance. Also, the retweet volume is very low now, so exceptions should be

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

John, I assume the method to use would then be http://stream.twitter.com/1/statuses/filter.format It does not mention that it includes retweets, but it will once the API is live? Cheers Sven On Sep 23, 9:38 pm, hansamann wrote: > Thanx, I'll give that a try. > > On Sep 23, 8:11 pm, John Kaluc

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

Thanx, I'll give that a try. On Sep 23, 8:11 pm, John Kalucki wrote: > Retweets will be searched by the follow parameter on the filter > resource. The intention is that you get all statuses (including > retweets) where any user_id field matches your predicate list. So, > tweets, replies and both

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

Retweets will be searched by the follow parameter on the filter resource. The intention is that you get all statuses (including retweets) where any user_id field matches your predicate list. So, tweets, replies and both ends of retweets. If GAE cuts you off after 30 seconds, then you shouldn't op

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

Is there a way to connect to the streaming api and only get my friends retweets? Or would I get *everyones* retweets and have to filter millions of unwanted messages out? On Sep 22, 9:49 pm, John Kalucki wrote: > Retweetaggregators should use the Streaming API /1/statuses/sample > method to gath

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

One reason for example is being on Google App Engine and having a 30 second limit. I cannot keep the connection open. Another reason is I am not interested in everyones retweets, just the retweets (and in this case all, not just a sample) of that twitter user's friends. What do you think? Cheer

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

I think the new RT API is an attempt to turn related tweets into a computer-parseable conversation. Humans can fairly easily determine what it part of an existing conversation by reading the different tweets and using contextual clues, but computers cannot. The small benefit to us humans is that

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

> As a regular twitter user, I'm less thrilled. Once this is in place, > is it going to fundamentally what/how I see my public timeline? If the > mockups are anything to go by, it looks less useful. If someone I'm > following retweets something from SarahKSilverman, I don't want to see > SarahKSil

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

Maybe this isn't the right place, but... >From a developer perspective I love the retweet API and it's potential uses. As a regular twitter user, I'm less thrilled. Once this is in place, is it going to fundamentally what/how I see my public timeline? If the mockups are anything to go by, it loo

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

I'm seeing retweet_details information appearing in the payload of the statuses/show call. Is this normal behavior? Try this curl http://twitter.com/statuses/show/4297637412.xml Thanks - Martin On Sep 18, 4:57 pm, Marcel Molina wrote: > The Retweet API launch is close at hand. You might have a

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

Retweet aggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the full Retweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my ca

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

Marcel Molina wrote: > To give you some ideas of how you can use the API to display retweets, > here is a recent mock up of one of the potential UIs for the retweets > timeline on twitter.com: > http://a1.twimg.com/example-retweet-ui-18-sep-09.png In this example, how did you retrieve the number

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that t

[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)

On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina wrote: > > > Asking developers to collapse retweets in timelines is onerous, > complicated and confusing. We're not going to do it that way. We are > going to add a resource that gives you all retweets for a given tweet. > In timelines you will get o

[twitter-dev] Re: Update multiple users at once

You can use curl_multi_* to make multiple requests in parallel. http://us3.php.net/manual/en/function.curl-multi-exec.php On Thu, Jul 23, 2009 at 06:30, DavidH wrote: > > Cheers for that: it's what I thought but just wanted to check. Guess > I'll have to queue separate cron jobs if things start

[twitter-dev] Re: Update multiple users at once

Cheers for that: it's what I thought but just wanted to check. Guess I'll have to queue separate cron jobs if things start to get too big. On Jul 23, 1:31 pm, Cameron Kaiser wrote: > > If I want to update multiple Twitter user accounts at once (with a > > different message for each), is there an

[twitter-dev] Re: Update multiple users at once

> If I want to update multiple Twitter user accounts at once (with a > different message for each), is there anyway to do it other than > making multiple posts to update.xml? Nope. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Sys

[twitter-dev] Re: update profile image and profile image url

I never got any response on this, but a small update: it's now down to about an hour for this to update correctly. Often I'll hit /users/show/.json and it will return the correct value, however if I go and update the avatar a 2nd time (to the 3rd image, counting the first, original), the json file

[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help

On Fri, Jul 3, 2009 at 5:27 PM, Stuart wrote: > > 2009/7/3 goodtest : >> >> ah I cant believe I was missing such basic point.  Thanks again >> (especially for responding on a long weekend), it works now! > > Ahh, the good old attitude that the whole world is American. The rest > of us are out here

[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help

2009/7/3 goodtest : > > ah I cant believe I was missing such basic point.  Thanks again > (especially for responding on a long weekend), it works now! Ahh, the good old attitude that the whole world is American. The rest of us are out here ya know - we have our own timezones and everything!! -St

[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help

ah I cant believe I was missing such basic point. Thanks again (especially for responding on a long weekend), it works now! On Jul 3, 1:06 pm, Stuart wrote: > 2009/7/3 goodtest : > > > > > > > > > thanks for the quick reply.   I tried not encoding the url part of it, > > but still twitter only

[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help

2009/7/3 goodtest : > > thanks for the quick reply.   I tried not encoding the url part of it, > but still twitter only recognizes the first word :( > > http://twitter.com/statuses/update.json?oauth_consumer_key%3DXz2BKOKObTzpLrMXxJo2ww%26oauth_nonce%3Di3TKQ5uESfn%26oauth_signature_method%3DHMAC-S

[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help

thanks for the quick reply. I tried not encoding the url part of it, but still twitter only recognizes the first word :( http://twitter.com/statuses/update.json?oauth_consumer_key%3DXz2BKOKObTzpLrMXxJo2ww%26oauth_nonce%3Di3TKQ5uESfn%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D12466

[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help

2009/7/3 goodtest : > > I thought everything was working until i just sent a tweet with 4 > words, but only the first word is being posted for some reason. Please > help . > I think i have done all the url encoding stuffs, but somehow twitter > is only recognizing first word. What am i missing? >

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

Hi Alon, The main issue we've seen with extended UTF-8 is incorrect URL encoding of the values. We discussed this in depth in issue 433 [1], which I see you commented on. Without a little more information I can't really help. The information that would be most helpful is: 1. You menti

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

can someone assist with the php library? what todo? On Apr 16, 6:18 pm, Mario Menti wrote: > On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti wrote: > > > Thanks Guan - perhaps it's an issue with the signature base string not > > being encoded correctly at my end... let me dig into Net::OAuth a lit

[twitter-dev] Re: Update on product category

As Nick said this does not sound like a good reason to create multiple accounts. Though Twitter currently has no official policy on this type of usage, it is expected that you will create as few accounts as possible for your application. Since all of the ad updates will be coming from the same site

[twitter-dev] Re: Update on product category

On Sun, Apr 19, 2009 at 1:14 PM, Clodoaldo Pinto Neto < clodoaldo.pi...@gmail.com> wrote: > > > Now the question: Is there a way to create different kinds of posts > for a single user (the site's bot) that can be followed individually? > Or must I create more than two thousand users? > > If this us

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti wrote: > > Thanks Guan - perhaps it's an issue with the signature base string not > being encoded correctly at my end... let me dig into Net::OAuth a little > more and see what I find. > > Quick update: yes, the issue in Net::OAuth was actually identic

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

On Wed, Apr 15, 2009 at 3:47 PM, Guan Yang wrote: > > I was able to post this here: > > http://twitter.com/guan/status/1525625497 > > The non-breaking space is right after the colon; try to save the HTML > and check in a hexdump ;-) > > Normalized query string: > > > oauth_consumer_key=rNc2JuVC6N

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

On Wed, Apr 15, 2009 at 07:35, Mario Menti wrote: > This issue [1] is marked fixed, but for some reason I still have problems > with some characters: > I have a status update that contains "\xc2\xa0" (which I believe is Unicode > representation of & nbsp;), and trying to update the status with th

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

This issue [1] is marked fixed, but for some reason I still have problems with some characters: I have a status update that contains "\xc2\xa0" (which I believe is Unicode representation of & nbsp;), and trying to update the status with this always results in error 401. If I remove the "\xc2\xa0" t

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

Hi all, Anyone having the problem please add a comment to the Google Code issue [1]. Please include the following if possible: 1. What language, library and version are you using? » For Example: Ruby oauth gem v0.2.7, or PHP oauth-php r50 2. What application is this for? » For Exampl

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

Same problem here. I can't post update too, with cyrillic characters.

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

http://code.google.com/p/twitter-api/issues/detail?id=433 <--? On Apr 13, 10:23 am, Chen Jie wrote: > I have the sample problem too, can't post update with Chinese.. > > On Apr 13, 1:56 am, Guan wrote: > > > On Apr 12, 8:08 am, Cmdr J0hn wrote: > > > > Now, I send a Unicode charactor, "あ " > >

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

I have the sample problem too, can't post update with Chinese.. On Apr 13, 1:56 am, Guan wrote: > On Apr 12, 8:08 am, Cmdr J0hn wrote: > > > Now, I send a Unicode charactor, "あ " > > (not sure displayed on your screen properly, it's Japanese) > > > Signed on a string: > > > POST&http%3A%2F%2F..

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

On Apr 12, 8:08 am, Cmdr J0hn wrote: > Now, I send a Unicode charactor, "あ " > (not sure displayed on your screen properly, it's Japanese) > > Signed on a string: > > POST&http%3A%2F%2F...(omit)...%26status%3D%25E3%2581%2582 > > And a body is: > > status=%E3%81%82 > Any suggestion anyone? I hav

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009/4/12 Cmdr J0hn : > Now, I send a Unicode charactor, "あ " > (not sure displayed on your screen properly, it's Japanese) [...] > status=%E3%81%82 > > (It's utf-8, I guess. 3 bytes needed for one Japanese charactor) I think you're not encoding this properly. You're sending one character, so you

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

On Sun, Apr 12, 2009 at 11:35 PM, Julio Biason wrote: > (I have the slight impression that it should be something like > "status=%4054" or some other very right value, but, again, just one > character, not three.) Correcting myself: status=あ http://www.danshort.com/HTMLentities/index.php?w=hir

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

> > (I have the slight impression that it should be something like > > "status=%4054" or some other very right value, but, again, just one > > character, not three.) > > Correcting myself: > > status=あ > > http://www.danshort.com/HTMLentities/index.php?w=hirag NO! The original poster is correc

[twitter-dev] Re: Update

Thanks Cameron ... I was using tweet but just wanted to confirm. I got confused because a NET library I checked had create to I think ... that's why. Thanks, Miguel On Mar 10, 12:16 am, Cameron Kaiser wrote: > > On Twitter API I see 3 actions: > > Create, Update and Destroy > > > So I can upda

[twitter-dev] Re: Update

> On Twitter API I see 3 actions: > Create, Update and Destroy > > So I can update any entry recent or old given its id? No. If you look at the update method in the API documentation, you cannot pick an ID to update. Essentially it creates a new status (and in fact there *is* no create method fo