| [ 0 trackbacks ] | permalink | related link
Great time at startup weekend! I joined the CinchTool.com team, sharp group coded backend service, front end, marketing and e-commerce within 2 days! Company started and will continue to run, new round of features coming soon. Over 10k Cinch'd pages within the first week.
| [ 0 trackbacks ] | permalink | related link
Awesome ECT Results from trentmeisenheimer on Vimeo.
Scary backcountry conditions this year. Nice video Craig, love the slow'mo'audio!
Good weekend to write code. I am pitching PredicTag at Salt Lake City StartupWeekend
| [ 0 trackbacks ] | permalink | related link
Cool graphical video of how Watson answers Jeopardy questions. Here is also a TED talk about Watson's win.
| [ 0 trackbacks ] | permalink | related link
Wondering what Japan is saying about Fusion-io?
Tweets can be hard enough to decipher let alone translated tweets...
Here are some tips on translating Tweets with Refine and Google Translate REST api.
- Imported data into Google-Refine remember to specify utf-8 character encoding on import.
- You need to get a Google Translate API key
- Tweet text column drop down select Edit column - Add column by fetching URLs...
"https://www.googleapis.com/language/translate/v2?key=<access-key...goes here>&target=en&q=" + escape(value.substring(0,140),"url")
- The above creates a new column with the Translation json, now to parse, Use the add column based on this column command.
- below gets the text
value.parseJson()["data"]["translations"][0]["translatedText"]
- below get the predicted Language code
value.parseJson()["data"]["translations"][0]["detectedSourceLanguage"]
Some very wildly different results when comparing Twitter User Language, DataSift Prediction, Google Translation Prediction... check out the Google-refine text facets below:
| [ 0 trackbacks ] | permalink | related link
Back Next
Most Recent Entries
