Man, these hackers in Hollywood sure know a good API when they see one (*cough*, OpenTok, *cough*). I’m kidding, but I am genuinely thrilled about the uptake of OpenTok at this weekend’s Hollywood Hack Day.
I arrived Saturday Morning at Ashton Kutcher’s office in West Hollywood for day one of the hackathon. I was pleased to see that there were lots of developers and chocolate chip muffins. I spent the first couple hours getting acquainted with both.
I had come to the event thinking I was going to hack on a jeopardy game. Janine Yoong, who was attending Music Hack Day in Boston, was conspiring with me to build a jeopardy game that would mash up APIs from both events, and that way we could submit the same app for two different hackathons, and win all sorts of prizes. It was a genius evil plot.
Presenters at Thinc Iowa 2011
Returning home to the midwest after spending a few years in the cultural bubble of San Francisco is a strange experience. As John Travolta’s character says in Pulp Fiction regarding Europe: “It’s the little differences. I mean, they got the same shit over there that we got here, but it’s just… there it’s just a little different.” You’re confronted with of all the superficial differences in dress, decor and culture, and you start to remember that in Iowa it isn’t about wearing expensive clothes, or having a hip club to check out every night. It’s about sincerity, genuine friendliness, working hard, and desire to help other people. “And that,” I imagine the people presenting at Thinc Iowa would probably say, “is exactly the point.”
If I had a nickel every time someone pitched me an app idea, I might have enough to buy an Amazon Kindle Fire.
Unfortunately for me, nobody has given me a nickel. But you, however, are in luck.
We’re running a contest to find the best idea for an application that uses the OpenTok API, and were giving away a spankin’ new Amazon Kindle Fire.
It’s been an exciting few weeks for video quality. In the world of the wild, wild web (www), a stranger riding into town could be good, bad, or something else…
That’s what we thought here at TokBox when Adobe Flash Player 11 galloped into the land of OpenTok last week. From a distance, the stranger looked like a bandit, triggering an old hardware acquisition bug that threatened to break the OpenTok API. But we squashed that bug right quick. After the dust settled, we realized that Flash 11 was actually one of the good guys. There was a new sheriff in town—and Flash 11 was gonna use his H.264 revolver to bring justice and a new dawn for OpenTok video quality. Thanks to Flash 11, the OpenTok API now offers beautiful images that are clearer, crisper, and sharper than ever before.
Last weekend I and ~50 other developers, businesspeople and designers attended the SF Startup Weekend EDU hackathon at Grockit HQ, located right around the corner from TokBox here in SoMa. The event marked the first in a series of events in a new Startup Weekend track (EDU) focused on learning and education.
This was the second Startup Weekend I’ve attended since starting here as a Developer Evangelist, and it was noticeably different from the first one I attended which was Startup Weekend MEGA, at Microsoft HQ in Mountain View. Even though SW Mega is generally regarded as a sexier Startup Weekend event due to its visibility, prizes and the three startup tracks it features, this smaller event was more fun for me because it was more focused and seemed to be a more cohesive and intimate.
Here at TokBox we’re always trying to find ways to improve the quality of your video experience. We’ve pushed out H.264 support with the new Flash Player 11 plugin. We’re learning how to pump more bits down the same bandwidth pipe to make sure your video is clear and crisp. And now, we are excited to enable Peer to Peer video for two party video chats.
What exactly is Peer to Peer (P2P)?
Traditional OpenTok sessions stream video via our servers. With P2P, participants stream video directly to each other, resulting in better video quality!
I used to think that localization meant translation. As someone who has lived in the US my entire life and has no experience with international business, I didn’t know any better. I assumed that to enter a foreign market, all a company had to do was slap up translations, register a local domain, hire a US celeb to pimp the brand, then boom—10 million new users.
I wasn’t that naive of course, but I never knew what localization really meant. I never knew until I learned how unsuccessful US consumer internet companies have been at entering China. Google, Amazon, eBay, Facebook, Yahoo, Twitter—all the giants. They all tried and failed.
Many years ago, I came to Silicon Valley to work as an engineer at Apple and got my start in video with QuickTime 1.0 and QuickTime VR.
Apple was where I found out that design and technology can not only co-exist, they can multiply together in a marvelous kind of fusion. Even though I worked at Apple in the wilderness years – when Steve wasn’t with the company – that vision and focus on user experience was already deeply embedded in the DNA of the company.
Of all the things I learned at Apple, the fusion of design and technology, and the creative process that drives that fusion, were the most fundamental. For me, working at Apple created a deep-seated belief in the transcendent impact of a beautifully integrated user experience. That belief is why when I talk about my time at Apple, I often say: “You can take the engineer out of Apple, but you can’t take Apple out of the engineer.”
Last Saturday at TokBox HQ in San Francisco, 40 awesome and friendly hackers (and 1 mascot) came together to create 13 video apps built with a variety of video APIs. Six out of 13 projects incorporated OpenTok, including:
You Got Served: Two videos went head-to-head to compete for votes to see which one is the crowd pleaser. One of the hackers presenting deftly showed off his dance skillz vs a football game; dance was the winner there.
8sec.tv: App that integrated OpenTok video archiving and RottenTomatoes to let users record video reviews.
A few weeks ago we sent out an email regarding changes to our session IDs (they are now longer, up to 255 characters). If you are storing session IDs for re-use, make sure that your database field supports this (we recommend a length of 512 just to be safe).