|
1 | | -# codebase |
| 1 | +# PeerViewer codebase |
2 | 2 | PeerViewer codebase for the free peer-to-peer TeamViewer solution.
|
| 3 | + |
| 4 | +Under the hood, it uses direct (peer-to-peer) connections between the participants. |
| 5 | + |
| 6 | +This was recently made possible by the advanced holepunching techniques, made by the HolePunch company. |
| 7 | + |
| 8 | +# Why peer-to-peer? |
| 9 | +Traditionally, when you use network apps such as TeamViewer, place audio and video calls or share files, your data is going through intermediate servers which are expensive to host, can harm your privacy, increase latency and consume additional bandwidth. |
| 10 | + |
| 11 | +Peer-to-peer solutions such as PeerViewer have the advantage of: |
| 12 | + |
| 13 | +- Being the highest bandwidth AND lowest latency way of establishing a network connection. |
| 14 | +- Ensuring maximum privacy for all participants. |
| 15 | +- Being low cost, making it possible to survive on a pay-what-you-can/voluntary/donation basis. |
| 16 | +- Minimizing time-to-market and allowing for quick MVP's without a lot of server-side datacenter setup work. |
| 17 | +- Building blocks |
| 18 | + |
| 19 | +We're lucky to be standing on the shoulders of giants to pull this off. |
| 20 | + |
| 21 | +Here's a list of some key, free and open-source technologies that make this possible: |
| 22 | + |
| 23 | +- HolePunch, for establishing direct peer-to-peer connections. |
| 24 | +- LNBits, for quickly building reusable payment QR codes using the LNURLp standard. |
| 25 | +- Electron, for building standalone applications using open web standards. |
| 26 | +- Bitcoin and Lightning, for accepting payments without needing anyone's permission or approval. |
0 commit comments