Here’s some homework for you folks for the weekend.
You might have noticed that I’ve moved from posting 2 times a week to 3 times a week in most weeks. Apparently this isn’t enough either – I already have a pipeline of two months of topics I want to write about – and that’s just my stuff.
My solution for now would be to add a fourth post in some of these weeks which will send you elsewhere – to interesting things I’ve read and think are important for you. The name for it? Weekend Reads.
This time, it is all around WebRTC, as this week was packed full with information that I haven’t written…
To make things simple, here are a few posts I found really interesting this week:
- News of the week? Microsoft shows they are serious about WebRTC – or should we say CU-WebRTC? This is a very interesting development – coming with a solution that is interoperable between CU-WebRTC and WebRTC gives them leverage moving forward if they get the mindshare around this. It probably also deserves a posts of its own…
- Dean Bubley has a great write up on browser and non-browser support of WebRTC
- Alan Quayle covers the AT&T Developer Summit. The most interesting part there is the news that AT&T is now offering WebRTC APIs to developers. This is done through its collaboration with Ericsson and Voxeo
- Dave Michels and Chris Vitek wrote about the impact WebRTC will have on unified communications. The piece is top notch with some interesting use cases for those thinking what can be done with WebRTC
- Andy Abramson started looking into WebRTC closer – mainly due to the chatter going on on twitter. Having Alan in the conversation is a great thing
- Tech Crunch had two news items this week regarding WebRTC, which notes how far we’ve gone with WebRTC
- I’ve posted last week on NoJitter about the need (or non-need) for a WebRTC version of Google Hangout
- Unrelated to WebRTC, but still in the telecom area, here’s a post I published this week on Amdocs Voices about 3 stories you might have missed because of CES 2013
Hope you will like this additional “bombardment” from my side – the idea came after a polite complain in the WebRTC group of Facebook that others should post as well and that people shouldn’t be posting only their own content. So I thought – “if I can share other’s content there, why not on my own blog as well?”
Have a great weekend.