Search the Community

Showing results for tags 'friend'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • BitTorrent Client
    • Common Errors and Solutions
    • Announcements
    • General Discussion
    • Troubleshooting
    • Feature Requests
    • BitTorrent Pro Support
  • BitTorrent Mobile
    • BitTorrent Android
    • BitTorrent Remote Apps
    • BitTorrent Remote Web
  • Developers
    • Announcements
    • General Discussion
  • BitTorrent Bleep
  • Project Maelstrom
    • Developer Discussion
  • BitTorrent Web
    • BitTorrent Web Client

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hi, I want to suggest a kind of basic thing, i want to be able to add a peer that when added will try to connect to it and if that peer becomes available it will never choke that peer. In both directions, basically the highest priority peer. Why, well, me and a friend of mine want to send stuff between each other, maybe a cool "linux distro" or similar, and, well we have a very high speed link between us so why not prioritize that link over everything else, but i have so many times had either one or both sides choke the other or similar and it is super annoying since we might be getting a fraction of the possible speed from the internet compared to the max speed between us. Additionally, an ability to add such a "friend peer" in a list somewhere so he gets queried for every torrent i add, so that if he has the same info hash, i will try him first of all peers.
  2. Hi, With some friends we would like to do the following things: - Share photos - Family videos - Share private torrents This would be done over a private network using tinc (Virtual Private Network daemon). Torrents shared over this network must not be accessed from other networks. No connection tentatives must be done towards external networks. Every machine knows what files are available on the other machines of the network. When a machine is asked to download a file, it should download it from a set of other machines owning the file to maximise transfer rate (in comparison to direct transfer). A------------B | C----' If A wants a file, if the file is in B and C, then A will download chunks from B and C at the same time. The index of what files are available should not be put in a central place. We would like the system to still work if any machine is disconnected from the network. The indexer and sharing daemon should run on a headless machine. This solution looks like trackerless (via DHT) torrent, but we couldn't find any good implementation. The only tool that we found doing all of that is tribler. Yet, before digging into more details about this tool, we would like to know all the possibilities we have. We have tried to set up trackers on each host sharing files. Yet we have to synchronize the trackers and we couldn't figure an obvious way to do this. Moreover it is not easy to have a unified view of the totality of the available shared content on the network. We are aiming at a trackerless architecture which would allow us to list and share files in a decentralised fashion. We think the DHT will be a key component of our architecture. Are there any existing tools which could allow us to set up all these requirements in place? Thanks in advance for any of your ideas and suggestions. Best regards.