This is the main purpose of this application.
This has to be easy to use and safe to work with. But it has to be a lot more secure then already established ways.
At first, the dht can be published through magnet links. With this, the consumer gets all information about the torrent and correspnding data. This magnet links and corresponding torrentfile will be created by the publisher, when he wants to publish his data in the application.
The magnet link can be published through public channels like websites or group chats or private channels like private channels and email. Another way to exchange this link, the publisher can create a qr code with the magnet link and the consumer can scan it with his own camera device.
Though there is no way to disable crawl the dht, i need a way to encrypt the data or to authorize and authenticate the user against a torrent to get the seeds and torrent files.
Are there any use cases, where there is no explicit publisher and consumer?
Maybe, this can be realize with an authorization backend? This backend does not need to be centralize, because the publisher is a dht itself, so he can manipulate the respond, when he should send the files, but the consumer cannot authenticate or is not valid against the torrent.
This is the use case for private trackers.
This is the main purpose of this application. This has to be easy to use and safe to work with. But it has to be a lot more secure then already established ways.
At first, the dht can be published through magnet links. With this, the consumer gets all information about the torrent and correspnding data. This magnet links and corresponding torrentfile will be created by the publisher, when he wants to publish his data in the application.
The magnet link can be published through public channels like websites or group chats or private channels like private channels and email. Another way to exchange this link, the publisher can create a qr code with the magnet link and the consumer can scan it with his own camera device.
Though there is no way to disable crawl the dht, i need a way to encrypt the data or to authorize and authenticate the user against a torrent to get the seeds and torrent files.
Are there any use cases, where there is no explicit publisher and consumer? Maybe, this can be realize with an authorization backend? This backend does not need to be centralize, because the publisher is a dht itself, so he can manipulate the respond, when he should send the files, but the consumer cannot authenticate or is not valid against the torrent. This is the use case for private trackers.