Created on 21st March 2021
•
Existing systems work on the principal of keeping persistent TCP connection between users and server to facilitate communication between end users. Whatsapp recently claimed to have reached a capacity of one million established TCP connection on a single machine. This method is expensive and not feasible as to ensure continued growth, these systems need to be added with extra machines to handle such connections. This will increase in cost and usage of electrcity which isn’t ecofriendly. If we include redundent systems for backup’s the number just increases. Also a big concern in such centralized system architecture is security, as all the data is stored in central servers they are prone to attacks. All correspondence goes through the server of the company owning the messaging app, and the company can dictate its rules: block messages on a certain subject or prohibit the transfer of certain files. The company may also be subject to government pressures and may be asked to disclose users’ correspondence or to impose certain restrictions upon their request.
The proposed solution is free from any form of centralization and only uses a psuedo server for peer-discovery.
Bringing your own webrtc signalling servers: The WebRTCStar signalling Servers provided by IPFS organization may fail to send pubsub messages and fail to connect to other nodes this led to connection failures and hence it was highly unreliable. Since peer discovery and database synchronization happens over pubsub it was very important that we create our own randezvous server. Hence, we had to create our own webRTC rendezvous servers for peer discovery.
The signalling server can be found here.