1. Investigate Twitter’s search API and
Google’s translation API and if
needed, get keys.
2. Get the results from Twitter for a
3. Loop over the results, see which
ones are not in English, and then
translate them with the Google
The solution is very
similar to the other
Not fun with JS:
1. Asynchronous lookups with
generated script nodes are a pain to
get right - what if one breaks?
2. Depending on how many Tweets are
not in English, you have to hammer
Google’s translation API which slows
down your overall app.
Write your schema,
put it on the web
and use, err... USE
to, err... use it.
SELECT * FROM distance
WHERE place1=”london” and
as an API
- in JS!
Use YQL instead of wasting time
reading API docs for a simple task
Filter data in the service and get the
info back in formats you need.
Use the fast YQL server instead of
doing lots of requests.
Write your own JS APIs using
Use local storage and don’t break
Go and use the web.