Guess what? A decision was made, and it is rather what I've been doing lately - I'll try to keep up with my scheduling of posts, which means 3-5 posts a week.

Nokia is now asserting its position against VP8. What are its motives? What does it stand to gain, and does it have anything sabstantial to do with WebRTC at all?

Node.js is one of these frameworks that fits WebRTC like a glove, and many developers are adopting it for their service. In his post, Chris Matthieu explains why.

There's a question about the status of VoIP OTT players. They want to avoid being defined as telcos due to regulation, but what they offer is a service that competes with telcos. How does that work?

Enterprise Connect took place this week, and with it came a slew of announcements related to WebRTC. Here's a few weekend reads for you from that event.

What reasoning is there behind optional codecs in WebRTC? None if you ask me.

Google Reader is closing down, and with it my personal analytics platform. Time to move on and search for another one :-(

Open sourcing and throwing so much resources and money on a project isn't trivial. Not even for Google. What was behind its move to do just that for WebRTC? What does it stand to gain anyway?

This week in WebRTC on other blogs: it is all about challenges and progress being made.

VoIP and WebRTC has ways to go until it can be called a valid replacement for our current mobile telephony solutions. The reason? Battery life.