[twitter-dev] Re: How to count to 140: or, characters vs. bytes vs. entities, third strike
I'd be interested to see a document that details the standards for this as well. On May 15, 12:01 pm, leoboiko leobo...@gmail.com wrote: On May 15, 2:03 pm, leoboiko leobo...@gmail.com wrote: while one with 71 UTF-8 bytes might not (if they’re all non-GSM, say, ‘ç’ repeated 71 times). Sorry, that was a bad example: 71 ‘ç’s take up 142 bytes in UTF-8, not 71. Consider instead 71 ‘^’ (or ‘\’, ‘[’ c.). These take one byte in UTF-8, but their shortest encoding in SMS is two-byte (in GSM). So the 71-byte UTF-8 string would take more than 140 bytes as SMS and not fit an SMS. Why that matters? Consider a twitter update like this: @d00d: in the console, type cat ~/file.sql | tr [:upper:] [:lower:] | less. then you cand read the sql commands without the annoying caps That looks like a perfectly reasonable 140-character UTF-8 string, so Twitter won't truncate it or warn about sending a short version. But its SMS encoding would take some 147 bytes, so the last words would be truncated. -- Leonardo Boikohttp://namakajiri.net
[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline
Doug, I think using the same URL would work, but it might be nice to have an extra (or different) param added in order to determine the reason. For example, if a user revokes access from the web and Twitter notifies the URL, the app may just be updating values in a DB, not displaying anything. Whereas if the user clicks Deny and is sent to the URL, not only will DB updates be made, but a message provided to the user. Just a thought ;) On May 5, 10:36 am, Doug Williams d...@twitter.com wrote: I'm trying to decide if this could easily be part of [1]? Any objections for these to be one in the same? 1.http://code.google.com/p/twitter-api/issues/detail?id=545 Thanks, Doug -- Doug Williams Twitter Platform Supporthttp://twitter.com/dougw On Tue, May 5, 2009 at 8:27 AM, jmathai jmat...@gmail.com wrote: When the user clicks decline the flow is abruptly disrupted. I didn't see anything in the OAuth spec that specifies how a decline is handled. It would be nice if there was a decline url that the application could specify which the user is redirected to.
[twitter-dev] Re: public_timeline, invalid profile_image?
Alex - seems to still be an issue. Any updates on when we might see a fix? On Mar 30, 12:49 pm, Alex Payne a...@twitter.com wrote: We're on this. Thanks for the reports. On Sun, Mar 29, 2009 at 18:27, Gary Zhao garyz...@gmail.com wrote: I'm seeing it too. 2009/3/29 Günter Grodotzki guen...@grodotzki.ph since some days I am always getting: http://static.twitter.com/images/default_profile_normal.png as profile-image from the user via public-timeline (Data-mining-feed). I checked the announcement-google-group + twitter.com/twitterapi (subscribed to feed anyway ;) ) but could not see any change. The site affected:www.geoheartbeat.com -- Gary http://twitter.com/garyzhao -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
