Chirp 2010: Twitter International
by Matt Sanford on Apr 16, 2010
- 1,900 views
Talk on Twitter International from the Twitter Chirp conference. Presented on 2010-04-15.
Talk on Twitter International from the Twitter Chirp conference. Presented on 2010-04-15.
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 4
- Downloads
- 43
- Comments
- 1
- Embed Views
- Views on SlideShare
- 1,851
- Total Views
- 1,900
1–1 of 1 previous next
• “let’s get to it”
• Some business-y talk for the entrepreneurs in the group
• Notes on how we’ve gone about translation
• Engineering challenges for the coders in the group
• Search, platform (might remember API Group)
• Original OAuth (sorry)
• International (translation, char counting, twitter-text)
• the main reason: Users
• Passed 50% not long after the team formed
• In large part: Japan, translation
• Due to a slew of factors dev is mainly US (Twitter, EN, etc) but that does not mean it’s not looking outward
• Translating alone was not a big jump
• But we had set the stage. When the need for faster information arose we were there
• What’s great isn’t the users, but the utility [click]
• This tweet for example.
• It’s not what someone had for breakfast, but solving a real communication problem.
• What’s great isn’t the users, but the utility [click]
• This tweet for example.
• It’s not what someone had for breakfast, but solving a real communication problem.
• We’ve been dedicating resources and working on more local features
- We’ve been working as much on adding people as increasing the utility to those people
- Done this via a new mobile site matching Japanese expectations, along with email/photoposting
• The red dot here is the ‘follow me’ feature on the mobile site. It’s not the sole cause of the uptake but it’s helped.
• I’d like to take a moment and explain that … [next]
• This is something that people can learn from: We took advantage of existing user behavior, even though it’s not a behavior in the US. We use the QR-code.
• QR-codes are big in Japan [click] … like this one on a sign. Goes to the store site
• People are so used to this they use it for context like [click] these real estate listings
• We used this existing behavior [click] to let people share their ‘contact info’ in the form of their twitter profile.
- Like ‘Bump’ on the iPhone but it works on all handsets in Japan and is immediately evident to users.
• This is something that people can learn from: We took advantage of existing user behavior, even though it’s not a behavior in the US. We use the QR-code.
• QR-codes are big in Japan [click] … like this one on a sign. Goes to the store site
• People are so used to this they use it for context like [click] these real estate listings
• We used this existing behavior [click] to let people share their ‘contact info’ in the form of their twitter profile.
- Like ‘Bump’ on the iPhone but it works on all handsets in Japan and is immediately evident to users.
• This is something that people can learn from: We took advantage of existing user behavior, even though it’s not a behavior in the US. We use the QR-code.
• QR-codes are big in Japan [click] … like this one on a sign. Goes to the store site
• People are so used to this they use it for context like [click] these real estate listings
• We used this existing behavior [click] to let people share their ‘contact info’ in the form of their twitter profile.
- Like ‘Bump’ on the iPhone but it works on all handsets in Japan and is immediately evident to users.
• This is something that people can learn from: We took advantage of existing user behavior, even though it’s not a behavior in the US. We use the QR-code.
• QR-codes are big in Japan [click] … like this one on a sign. Goes to the store site
• People are so used to this they use it for context like [click] these real estate listings
• We used this existing behavior [click] to let people share their ‘contact info’ in the form of their twitter profile.
- Like ‘Bump’ on the iPhone but it works on all handsets in Japan and is immediately evident to users.
• This is something that people can learn from: We took advantage of existing user behavior, even though it’s not a behavior in the US. We use the QR-code.
• QR-codes are big in Japan [click] … like this one on a sign. Goes to the store site
• People are so used to this they use it for context like [click] these real estate listings
• We used this existing behavior [click] to let people share their ‘contact info’ in the form of their twitter profile.
- Like ‘Bump’ on the iPhone but it works on all handsets in Japan and is immediately evident to users.
• Like all features we turn to users for feedback. Could have paid, would have been cheaper, but would not have had community feedback
• Crowd-source, like open source for data. We had a great group … [next]
- Soon to send out more invites. Planning to make it open to anyone later this year.
[click] and more features every day.
[click] and more features every day.
• Built the tool into twitter.com, provides context (see pointer) for quality, social game dynamic in jump-around prompt (see counter)
• DB backed with cache, no-deploy launching.
• Multi-level voting
- Extract, autolink
- Open Source Ruby and Java. Also following community ports to Python and PHP (though PHP could use some love). Look forward to more.
- Conformance data: Unicode, YAML, assurance, non-EN test cases
• A good example of the 1% issues we handle in the libs are Japanese Tweets …[next]
• No spaces between words. Turns out, we assume a lot [click]
- http://S+ does not work.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• [click] Don’t count bytes. You knew that.
• [click] Don’t count code points. That’s news to many people.
• We try to count what a person would call a char, where possible. So, we [click] use the shortest.
• On Purpose: BOM (not utf-16), reserved, dir change (security, layout is not at home in a Tweet)
• Limitations of MySQL (<v6) prevent some chars. (small set of Kanji, musical symbols, ancient scripts)