2015 is notable in the number of sites that have been compromised by hackers, and the outlook continues to look grim. Companies have been rushing headlong into putting services online, prioritizing functionality above all. Up-time and scale, which has plagued early the early internet, while still a challenge, has improved significantly; however, security failures continue to get worse. This calls for a new approach. Application Security has been focused on vulnerability prevention, and static controls. In a world of continuous delivery, security needs to be continuous. In a world where hackers act faster than companies can patch, security needs to be adaptive, and responsive. What’s missing is defending the Application in production. This is Application Security’s Last Mile, and will be the focus of this talk.
Over the last 5 years, we’ve helped hundreds of companies create rich and engaging applications with OpenTok powered live video and voice. Now, we’re bringing broadcasters and brands (who are now broadcasters too) unprecedented audience engagement with the launch of our new Interactive Broadcast Solution.
Until now live broadcasting applications have focused on one-way streaming. This works well for conferences or events. But now, Interactive Broadcast is the first solution to enable multi-party panels, video-based audience participation, and an on-brand experience for website and application owners. The Interactive Broadcast Solution gives broadcasters the tools they need to bring user-generated content and viewer-participation content to both online and TV audiences.
Early December saw the roll-out of Chrome 47. When doing anything with WebRTC, this is always an interesting time. A release brings new features or may break things, like removing the getUserMedia functionality for insecure origins.
Our metrics clearly track such roll outs as seen below:
The rise of mobile, open sourced software and social networks has democratized content in every field from journalism to photography and video production. However, the last remaining battleground is the television, and Apple, with the new Apple TV, is blurring the lines between online and television, opening up all new possibilities for content creation and engagement. This marks not just another endpoint supported by TokBox, but the start of a new era of content creation that happens in the living room, which is why we’re prioritizing TV together with the web and mobile.
// < ![CDATA[
// ]]>GUEST POST: WebRTC.ventures is a custom design & development agency focused on building WebRTC applications. They are part of AgilityFeat, which is one of our development partners at TokBox. Jean Lescure from their team wanted to share their experiences using our new API for detecting call quality.
Back in August TokBox announced their new Pre-Call API, for testing out bandwidth conditions, and posted a repository on github with a proof of concept. At WebRTC.ventures we saw a great opportunity to build upon that project and got working on creating a demo app out of it, including a server implementation in NodeJS which is compatible with Heroku.
Just when we thought we were done with the video codec wars in WebRTC – we found out we’re only just beginning. Tsahi was here to talk us through some important questions – how is this WebRTC codec war going to play out? Where do the alliances lie? And where are we headed?
Watch the full video here:
Embedded communications is so powerful because of one very important factor – context. Whether that’s a web page, presentation, LMS, medical scan, (the list goes on), context enhances the conversation. Better still? When collaboration features are layered on top.
Using the OpenTok platform, our aim is to make it super simple for you to add rich collaboration functionality to your apps. Today we’re happy to introduce the Annotation widget for the OpenTok platform in beta – a pre-built UI component that can be quickly added to your application. The widget adds annotation and frame grab capabilities to the OpenTok web, iOS and Android SDKs and is completely customizable.
UPDATE 9/16/15: After we published this post Google announced that they are pushing back the release date of the HTTPS security change. They’re estimating that it will now be released to production in December 2015.
Google recently announced a security policy change that will impact future versions of the Chrome browser. Any website which has integrated geolocation technology, screen-sharing, WebRTC and more, will now be required to be served from a secure (HTTPS) site.
We at TokBox are supportive of this update as we believe operating your WebRTC-based applications through HTTPS is a best practice and offers enhanced security. In addition, it has the added bonus of improving your end-user experience by remembering their hardware settings, and even allowing screen-sharing (if you choose to implement it).
Fast data analysis requires using the right schema design for your data and taking advantage of the performance features in modern data warehouses like Redshift.
Join us at this month’s TechTok, where Tom O’Neill from Periscope Data will discuss how Redshift uses distributed data and columnar storage to speed up query execution, as well as how to leverage these optimizations in your schema design. You can find out more about the event and register to attend here.
At November’s TechTok, Tom O’Neill, CTO of Periscope Data , gave us some ideas about how to design data warehouses. Tom focused on how Redshift uses distributed data and columnar storage to speed up query execution, as well as how to leverage these optimizations in your schema design.
Watch the full video here: