Google » History » Revision 21
Revision 20 (Adrian Georgescu, 04/09/2013 03:46 PM) → Revision 21/24 (Adrian Georgescu, 04/09/2013 03:47 PM)
h1. Blink SIP client Since 2010, Blink is the best real-time communications open-source client using SIP protocol. The software is cross platform available for Linux, Windows and Mac users and is packaged under the name blink for Debian and Ubuntu Linux systems. users. The Session Initiation Protocol (SIP) is an IETF-defined signaling protocol widely used for *controlling communication sessions such as voice and video calls over Internet Protocol (IP)* h2. Home page Blink is available for download at http://icanblink.com h1. Google fork of webkit called Blink h2. Press release http://blog.chromium.org/2013/04/blink-rendering-engine-for-chromium.html h2. Project home page http://www.chromium.org/blink h2. Unfair competition With the launch of Google Blink web engine on April 3rd, 2013, both projects Google Blink and AG Projects Blink from http://icanblink.com overlap massively in scope, nature and purpose. While the webkit fork can be used for more purposes than Blink SIP client, the explicit adoption of RTCWEB standards into blink fork of webkit, Google library competes direct with the purpose and addresses the same market of Blink SIP client using the same name. Quote from http://tools.ietf.org/html/draft-ietf-rtcweb-overview-06: The goal of the RTCWEB protocol specification is to specify a set of protocols that, if all are implemented, will allow *an implementation to communicate with another implementation using audio, video and data sent along the most direct possible path between the participants* Since the launch of Google fork search results about Blink SIP client have been flushed away, only google relevant results appear. h3. Similarities * Both projects have the same name * Both projects implement real time communications features (text chat, audio and video sessions) * Both projects are in the open source domain h2. Blink community feedback Blink users community is providing relevant feedback about this massive and explicit overlap here: https://plus.google.com/113757927151929258451/posts/NCB2kc8sehi