fsuk-manchester
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fsuk-manchester] interesting view on skype replacement


From: Dan MacDonald
Subject: Re: [Fsuk-manchester] interesting view on skype replacement
Date: Mon, 4 Mar 2013 00:25:20 +0000

Whats the crack with webrtc and conferencing? Can it or will it handle more than one to one? Multi client video conferencing? How many will it handle for audio conferencing? Can we do this already, in Chromium too or just Chrome?

On Sun, Mar 3, 2013 at 10:36 PM, m3shrom <address@hidden> wrote:
Chrome is Free Software right? Surely I've got that right?
(only joking not trolling)

...//
http://danielpocock.com/understanding-webrtc-architecture-free-software-perspective

WebRTC is here, now.

Google launched Chrome 25 with built-in WebRTC support on Monday, 25
February. Within 24 hours, /DruCall/ <http://www.drucall.org>, an
easy-to-use WebRTC module for Drupal was available Free as a shiny new
GPL project.

While this technology offers a level of convenience for end-users that
is unprecedented, just what is involved for the keen server
administrator who wants to deploy this today?

With 20-30% of web users expected to be running WebRTC browsers within 3
months (due to automatic updates), and 60-70% by Christmas, will the
free software community be able to seize this opportunity to redefine
the way real-time communications is deployed?

I've whipped together a brief architecture diagram to answer those
questions, demonstrating how all core components can be built with free
software, today. All but one of these components is conveniently
packaged in stable Linux distributions like Debian
<http://www.debian.org> and Ubuntu <http://www.ubuntu.com>. The full
diagram is taken from the /DruCall/ web site
<http://www.drucall.org/architecture> where you can find more details:



_______________________________________________
Fsuk-manchester mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/fsuk-manchester


reply via email to

[Prev in Thread] Current Thread [Next in Thread]