localsend/protocol

BitTorrent features in localsend?

Opened this issue · 0 comments

Hello.

I would like to add certain features of the BitTorrent protocol to localsend. Is it possible to add certain features of the BitTorrent protocol to localsend?

1. what is BitTorrent?

  • BitTorrent is a communication protocol for peer-to-peer file sharing (P2P), which enables users to distribute data and electronic files over the Internet.

2. why BitTorrent in localsend?

"Technically, there is no limitation in the protocol. But I have seen someone transferring multiple GBs. But some users have issues with large files though localsend/localsend#36"

  • So, BitTorrent protocol can be used to reduce the server and network impact of distributing large files.
  • Rather than downloading a file from a single source server, the BitTorrent protocol allows users to join a "swarm" of hosts to upload and download from each other simultaneously.
  • localsend+BitTorrent allows you to send and receive p2p files locally.

3. what are the problems of BitTorrent?

  • BitTorrent may transmit or include illegal or copyrighted content. Court decisions in various jurisdictions have ruled some BitTorrent files illegal. Complicating the legal analysis are jurisdictional issues that are common when nation states attempt to regulate any activity.
  • Your internet service provider (ISP) and copyright trolls monitoring the BitTorrent network can take action if they catch you illegally torrenting. This can range from a warning letter and throttling (slowing down) of your internet connection speeds to legal action – although the latter is increasingly rare.
  • Remember that your BitTorrent downloads are public, even if no personal information is immediately linked to your download, your IP will still be linked to it.
  • The term leech also refers to a peer (or peers) that has a negative effect on the swarm by having a very poor share ratio, downloading much more than they upload. Leeches may be on asymmetric Internet connections or do not leave their BitTorrent client open to seed the file after their download has completed.
  • Leecher is someone who has downloaded a file but is not sharing it back to P2P network. Hence, overall availablity of file decreases.

4. How can we resolve the network protocol issues: localsend and torrent?

  1. As you get more devices using localsend, you split the file between different parts. This allows downloading, sending files to be faster and safer between different types of cell phones, computers.

    • At the same time, it forces users autonomously to collaborate with sending and receiving p2p files. What wouldn't happen originally in "BitTorrent", because users don't always send complete p2p files.
    • So, this solves the problem I mentioned earlier, the problem of sending very large files in localsend.
    • At the same time, it solves the problem of seeds in the torrent I mentioned.
  2. Responsibility for transferring, sharing or sending files does not lie with the application: localsend and the localsend network protocol, but with the users who used the application and protocol: localsend.

    • We can specify this in terms of use to avoid any legal process.
    • Things like "BitTorrent" or "torrent" generally don't state this in legal terms, and are subject to legal enforcement.
    • I'm not a judge, prosecutor or lawyer - in that sense, you need to assess situations and implications.

5. what is the difference between the protocol: "localsend-bitTorrent", "localsend", "bitTorrent"?

  • localsend-bitTorrent: Works on a local p2p network, is encrypted, has terms of use to avoid legal proceedings. You don't need a proxy or vpn, because localsend is sent offline, locally.
  • localsend: does not work on p2p network.
  • bitTorrent: Works on a p2p network. But its use has legal problems, there is usually a seed problem that I mentioned, it is not anonymous - in this sense, a proxy or vpn is usually used.

Context: