The Wayback Machine - https://web.archive.org/web/20200825002331/https://github.com/topics/peer-to-peer
Skip to content
#

peer-to-peer

Peer-to-Peer (P2P) applications share resources and communicate in a decentralized or distributed architecture. Often application nodes communicate directly with each other or cooperate to do work which benefits other nodes or the overall P2P system. In a pure P2P system, there is no distinction between client and server.

Here are 696 public repositories matching this topic...

alexbosworth
alexbosworth commented Aug 10, 2020

Background

When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.

In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the

decentralized-video-chat
harsha20599
harsha20599 commented May 9, 2020

Since the URLs are just a gate pass for the video call, there might be a chance of getting intruders into the call with a simple brute force.

Users feel more secure if we have some passcode or approval from the creator to join into call.

koivunej
koivunej commented Jul 16, 2020

Not providing any repo locking causes difficult to debug issues as I've hit earlier myself and now others have as well, see #241.

Simplest way could be to fail at Repo::init time if a lock file exists. If the lock file doesn't exist, one must be created and again removed at exit time. Probably ok to rely on deletion at Dro

You can’t perform that action at this time.