Re: default messaging/VoIP client for Debian 8/Jessie
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 30/03/14 20:53, Jonas Smedegaard wrote:
> Quoting Tzafrir Cohen (2014-03-30 19:15:04)
>> On Sun, Mar 30, 2014 at 07:24:15PM +0200, Daniel Pocock wrote:
>>> On 30/03/14 16:54, Jonas Smedegaard wrote:
>>>> Quoting Daniel Pocock (2014-03-30 16:31:18)
>>>>> Jitsi does IM/chat too, I just didn't emphasize that so
>>>>> mcuh.
>>>>
>>>> Please add "T" in the relevant "TAV" fields at
>>>> https://wiki.debian.org/UnifiedCommunications/ClientSoftwareComparison
>>>>
>>>>
- - and while at it please also add info about JSCommunicator :-)
>>>>
>>>
>>> That is a trick question - many of the features of
>>> JSCommunicator are provided by the media stack in the browser
>>> or by JsSIP
>>>
>>> E.g. if a browser supports Opus, JSCommunicator will use it.
>>> If not, it doesn't actually know or care.
>>
>> So this page needs some entries for browsers?
>
> Please don't: Let's keep it a two-dimensional matrix.
>
> Track browser features in a separate wiki page if you find that
> relevant (and, for comparison, one on how well desktop environments
> integrates a volume control as part of their GUI, and one on which
> integrated computers has graphics drivers with XVIDEO supported X11
> drivers, etc.).
>
To maintain the correct focus here, it is probably more relevant to
track browser features from the WebRTC specs rather than all browser
features in general.
Some things are standard as per the spec and all browsers implement
them (e.g. the G.711 codec, AVPF, ICE)
There has been variation in the SRTP style and the video codecs but
that will hopefully converge.
All of this could be summarised by a line in the table for "WebRTC
spec" rather than one line per browser.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJTOGl6AAoJEOm1uwJp1aqDWKsP/3K3FiS01/1ibU0DTSLeNxVk
/6HW/pFmnykQlWwg25Q3TBPaEBlhTqjiidpMTQ1zev50UzbNZt1nmWTlmwWb0Eg2
crOvjErfm4of+pdQeqq7r+bAVOk8lX80QYxUveTzPDOuyB7QJgmRw5PzI7JaoUxc
rLKDaqJLnhgj16UJJfdg7ECgLGxFVYxudb82oQIXHfDAoiWY0QpzABge/uvO9r10
8Y/IgPkrBEcTmZO6Gfdu1P0cE2P7+UZ01CnV10MTJyqv1txgPQeKpkLwxMwK8NVw
O03jLiVNLjfyKCr5HHbtPyXjZSYWlrBSUpwxEXefwjF+mCErGnolQjuIjaP7puJa
mSOjlS5DwUPSmNkinydwCY3/0Ho6HPf5BE0esG1iddcN1b4yDnsKm7s//NJUviad
sVCS9uDUiw+mx53LxSowWtwoIfcpEbWR7lMaBnnubdbBuFHdfr3oGKaC+uHuwbb7
4amXJUy+i7Ch18RoKR3zrO6SAuYwmjjIx1/Xzk7czZqAXVr3ZqyPUe2+1cxJl1My
7hfUuvXgJkG3A6BgDMwMkRRnIm1jCCi3R0VAH2jUQyd6aG6npO0ODOFvTGTl+zx1
KSgvcfIuaL4lQjXzrWutpPPwP2golnknuX2LkaCZG4TghZJ22epwq3z6qY9uC2Bv
G3Q13Ae9pG/UlYwvw0qP
=aG2+
-----END PGP SIGNATURE-----
Reply to: