Re: [twitter-dev] Problem sending tweets with nbsp chars
URL Encoding? On 4 March 2010 02:13, Roy Leban r...@royleban.com wrote: Twitter is rejecting tweets as too long when the nbsp character is used. Here is an example tweet in plain text Clue 5 of 15: R _ C __ _ N _N _ _ E __ _ T E R__ _ _ N E E R_ N_ _ R _ C U L T U R E http://www.puzzazz.com/s348 [140 chars] And, as I'm sending it with the nbsp characters: Clue 5 of 15: Rnbsp;_nbsp;Cnbsp;_nbsp;nbsp; nbsp;_nbsp;_nbsp;Nnbsp;_nbsp;nbsp; nbsp;Nnbsp;_nbsp;_nbsp;Enbsp;_nbsp;nbsp; nbsp;_nbsp;_nbsp;Tnbsp;Enbsp;Rnbsp;nbsp; nbsp;_nbsp;nbsp; nbsp;_nbsp;_nbsp;_nbsp;Nnbsp;Enbsp;Enbsp;Rnbsp;nbsp; nbsp;_nbsp;Nnbsp;nbsp; nbsp;_nbsp;_nbsp;Rnbsp;_nbsp;Cnbsp;Unbsp;Lnbsp;Tnbsp;Unbsp;Rnbsp;E http://www.puzzazz.com/s348 If the nbsp's are each counted as 6 characters, this would be 400 chars, but Twitter accepts tweets like this. For example, this tweet: http://twitter.com/Puzzazz/status/9781320047 is 114 chars but I send 304 chars with the nbsp's. I have a guess that this only happens when the resulting tweet is exactly 140 chars. To test this theory, I just modified the site to shorten that tweet below 140. Sure enough, it works: http://twitter.com/Puzzazz/status/9963348931 -- Charles A. Lopez charlesalo...@gmail.com What's your vision for your organization? What's your biggest challenge? Let's talk. (IBM Partner)
Re: [twitter-dev] Search API rate limit IP address question
On 2 March 2010 14:05, eys eddiey...@yahoo.com wrote: Hello there! I have two questions: First, I received an approval for whitelisting for my server's IP address (as in, the IP number that I see when I log onto my webhosting account). I'm currently building my application in Flash using AS3 and after I've tested my project a few times, I'll get this error: Error #2032: Stream Error...[my search request] I assume this is rate limiting in action? If this were true then sometimes your request works and other times it doesn't. Is that the case? I read on this discussion board that whitelisting doesn't affect Search API. Does this mean I will always be limited to some arbitrary (unpublished) search limit? Then, I noticed the IP address used for the GET request is the IP address of the computer I'm using, NOT the IP address of my web server. How is this happening even though I'm using a proxy installed on my web server? Shouldn't the call be made from the server, not the computer? There are multiple requests happening here. I assume the following, which may or may not be correct: - From your browser you call your app - Your app runs some call through the twitter API - Twitter servers process the call and send it back to your app - Your app returns processed code back to your browser From the above processes your IP address is passed through by the Twitter API to the twitter service. I'd suggest try running your request from a completely different network and see what happens. Thank you. I'm pretty new at developing applications, so any help or advice is greatly appreciated! -- Charles A. Lopez charlesalo...@gmail.com What's your vision for your organization? What's your biggest challenge? Let's talk. (IBM Partner)
Re: [twitter-dev] Twitter Application Suspended
you might be doing something perceived as offensive. In the past on projects i have worked on, I had over utilized the processing resources of a remote server. Are you doing anything like that? 2010/1/26 Proxdeveloper prox.develo...@gmail.com Hello folks, This is the 3rd time I get my application suspended from twitter, the 2 different names I've tried are : Twhit,TwhitClient, and both have been suspended; Twhit has been suspended for 2 times already, I deleted the app and then registered it again. My experience of developing with twitter has been awful, it's one problem after another. Could anyone help me on why I'm getting my app suspended. --
[twitter-dev] Re: What is 140 characters?
2009/9/9 Matt Sanford m...@twitter.com Hi There, I'm sorry this never got updated. Some changes have been made and are waiting to go out now. When I switched from working on the Platform (formerly API) team to my focus on international I took over this issue. Once this current fix is deployed (probably in a week or so since I'm traveling at the moment) the definition of a character will be consistent throughout our API. The new change will always compute length based on the Unicode NFC [1] version of the string. Using the NFC form makes the 140 character limit based on the length as displayed rather than some under-the-cover byte arithmetic. I more than agree with the above statement that a character is a character and Twitter shouldn't care. Data should be data. The main issue with that is that some clients compose characters and some don't. My common example of this is é. Depending on your client Twitter could get: é - 1 byte - URL Encoded UTF-8: %C3%A9 - http://www.fileformat.info/info/unicode/char/00e9/index.htm isn't that 2 bytes? -- or -- é - 2 bytes - URL Encoded UTF-8: %65%CC%81 - http://www.fileformat.info/info/unicode/char/0065/index.htm + plus: http://www.fileformat.info/info/unicode/char/0301/index.htm and this three bytes? So, my fix will make it so that no matter the client if the user sees é it counts as a single character. I'll announce something in the change log once my fix is deployed. Thanks; — Matt Sanford / @mzsanford [1] - http://www.unicode.org/reports/tr15/ On Sep 9, 6:05 am, TjL luo...@gmail.com wrote: It's been nearly 6 months. Has this question been answered? If so I missed it. On Tue, Mar 24, 2009 at 9:36 PM, Alex Paynea...@twitter.com wrote: Unfortunately, nothing definitive. We're still looking into this. On Tue, Mar 24, 2009 at 07:56, Craig Hockenberry craig.hockenbe...@gmail.com wrote: Any news from the Service Team? I'd really like to get the counters right in an upcoming release... -ch On Mar 6, 12:18 pm, Alex Payne a...@twitter.com wrote: I'm taking this email to our Service Team, the folks who work on the back-end of the service. The whole message body changing as it moves from cache to backing store thing is totally unacceptable. Answers soon. On Fri, Mar 6, 2009 at 09:43, Craig Hockenberry craig.hockenbe...@gmail.com wrote: Some discussion about this thread popped up on Twitter yesterday: http://groups.google.com/group/twitter-development-talk/browse_thread/ thread/44be91d5ec5850fa Alex states that it's 140 bytes per tweet. So, of course, Loren Brichter and I tried to prove that. With the following results: 1) 140 characters that including ones that include HTML entities: http://twitter.com/gnitset/status/1286202252 At the time of posting, this tweet showed up on the site and in feeds with all 140 characters. After a few hours, the was converted to lt;, increasing the count per character from one to four bytes and decreasing the tweet length from 140 characters to 69. (You can see this truncation at the end of the tweet: the is from lt;) Presumably, this happens as tweets in the memcache are written though to the backing store. I also see a lot of Twitter clients that don't realize how special the lt; and gt; entities are. It took me a LONG time to figure out what was going on here. 2) 140 Unicode _multi-byte_ characters: http://twitter.com/atebits/ status/1286199010 What's curious is that Loren's example with 140 characters uses the Unicode 27A1 glyph. It uses 3 bytes in UTF-8. Why didn't it get truncated? This seems to contradict Alex's statement in the thread mentioned above. As people start to use things like Emoji, tinyarro.ws and generally figure out that Unicode (UTF-8) is a valid type of data on Twitter, our clients should adapt and display more accurate characters remaining counts. I can count bytes instead of characters, but I'm not sure if I should or not. No one likes a truncated tweet: we need an explicit statement on how to count and submit multi-byte characters and entities. -ch -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Can't view/retrieve full text message with length greater than 140 and = 160 characters?
It's not a flaw but a feature. On Fri, Dec 19, 2008 at 9:44 PM, Scott Carter scarter28m-goo...@yahoo.comwrote: Hi Alex, Please refer to a related thread at: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/d11a31c7ecf033b/130ed44d6b502e6c?lnk=gstq=160#130ed44d6b502e6c I am trying to send an update via the API that is greater than 140 characters, but = 160. When I try to view the whole message on the Web by clicking on the elipsis ... I do not see the full message. I tried the following two calls: http://twitter.com/statuses/user_timeline.json http://twitter.com/statuses/user_timeline.xml In both cases, I see truncated set to true, and the value of text is the same as what I see on the Web - not the full message. Is it no longer possible to see/retrieve an update where 140 length = 160 ? If this is the case, why does the documentation at http://apiwiki.twitter.com/REST+API+Documentation say Must not be more than 160 characters under the update function? An example with 155 characters is: http://twitter.com/blueskies2/status/1068333279 Almost a foot of snow was predicted for parts of central Michigan, CNN affiliate WNEM-TV in Saginaw reported. Classes were canceled in hundreds of schools. This is a protected update (my developer account) - please feel free to view it for debug as needed. Thanks in advance for a clarification. Scott