Welcome!  I’m Dan Burnett, and I’ve been involved in the WebRTC community since before its standardization began in 2011.  The excitement was incredible.  Finally (!), we would be able to go beyond the paradigm of the phone call, a world in which audio (and sometimes video) communications were the end goal rather than merely an enabler for humans and/or their software agents to accomplish a goal.  We fully expected to see applications that none of us could then imagine, because finally we had a set of APIs that truly used the Web paradigm, a simple set of JavaScript APIs that finally removed the reliance on a server to route traffic.  Moreover, the ability to transmit arbitrary data the same way offered up options for game programmers, remote health monitoring, and more using the same APIs.  But there were several problems:  unstable technology, unstable standards, and no central source for community and information.  Two of the biggest questions I heard were “but how do I get started?” and “where should I go if I need help?”  Gradually some great sites developed, many of which continue to this day:  webrtchacks.com and bloggeek.com are two good examples.  Gradually conferences formed: webrtcworld.com and krankygeek.com, to name some well-known ones.  And Alan Johnston and I wrote a book, as did others.

Fast forward to today (May 2017).  The early WebRTC startups have all been acquired, the standard is close to wrapping up (for version 1.0 at least), WebRTC Live Q&A Session #15, WebRTC support in some form is in every existing telecom platform, and the technology has made its way into well-known consumer products such as Amazon Mayday and FaceBook Video and Voice Chat.  But while conference attendance has been dwindling, I still hear the same questions:  “but how do I get started?” and “where should I go if I need help?”.  Moreover, I now consistently hear one other comment:  “I like the many blog sites, and there seem to be people who know stuff, but it takes so long to sift through the sales pitches to get to the real info I need”.

And thus AllThingsRTC.org is born.  We want to help people get the help they need.

So who is “we”?  It’s me, some partners who know web design and community building, plus some partners outside the US who want to see this be a global initiative.
Are we “a news site”?  No.  Are we “a conference site”?  No.  Are we “a telephony site”?  Not exclusively.  Are we “a WebRTC site”?  Not exclusively.  This site is the beginning of a broader project dedicated to those who are excited by the thought of what can be accomplished using real-time communications technologies such as WebRTC, to those who have the beginnings of a dream but no idea where to start or where to go for more help.  This is not a personal side project or a mouthpiece for a single vendor.  We have the background to help the community come together, and we have the motivation to remain unbiased and independent.

Do we intend to replace any/all of the existing related sites?  Not at all.  In fact, we are happy to point you, our reader, to whatever resource you need.  That’s why we seek out articles by and interviews of those in this industry who are the experts, those who consult, those who provide products that might meet your needs.  But always, always, always with a focus on explaining in detail why what they offer matters.
So, to those of you in this industry that know me, and those that don’t yet, if I haven’t already contacted you about providing an article or guest post, please reach out to me.  I am happy to have your opinion, your information, and a pointer to your work.  That’s what this is all about.  Let me help you tell your story.

Dr. Daniel Burnett has a history of almost 2 decades of experience with Web and Internet standards dealing with communications, having co-authored VoiceXML, MRCPv2, WebRTC, and many other standards. In creating AllThingsRTC, Dan aims to provide the innovators in the real-time communications space a forum for explaining the topics that really matter.