chr15m / bugout

Back end web app services over WebRTC.
https://chr15m.github.io/bugout
MIT License
607 stars 59 forks source link

Compare with simple-peer? #12

Closed pwFoo closed 5 years ago

pwFoo commented 5 years ago

Hi @chr15m,

looked into bugout and https://github.com/feross/simple-peer and try to understand the difference and additional features of bugout.

Bugout works nice without a server (because it uses webtorrent signaling, right?) and is more secure (NaCl???). Bugout transfer text and could be used for chat massages seen in the demos. Simple-peer supports audio / video, it's smaller and isn't dependent on NaCl and webtorrent.

Just to unterstand what the advantages of bugout. Could you please explain? Obviously to me bugout do the signaling / offer / answer part for me and with simple-peer I have to do it myself (for example with a backend server to exchange offer and answer)? But I think it's more than just that bugout is doing?

chr15m commented 5 years ago

@pwFoo that's correct. The main features Bugout brings which are not already present in WebTorrent and simple-peer:

The purpose is to provide a communications channel (like simple-peer) but with 1. a deterministic way of finding peers based on their pubkeys and 2. the ability to publish and execute RPC calls.

It enables communications apps like dirc with few lines of code.