loveisgrief / dht-bittorrent-index Goto Github PK
View Code? Open in Web Editor NEWA distributed index of torrents.
A distributed index of torrents.
Nodes should be able to create big indexes. Certain websites have databases of torrents that are a few GB big. A simple getTorrentIndex
command on our nodes will non-descriminantly return all infohash-'torrent name' key-value pairs.
We should improve our getTorrentIndex
to have the form
getTorrentIndex [--limit <number> [--page <number>]]
_Syntax:_ []
- Optional argument
An infohash could have multiple names. What will we do in case that happens? Store a list of names? Never update the name?
At the moment we can add DNS and IP entries to the node index. This can lead to duplicates in our node index e.g
sometorrentsite.org can have and IPv4 address and an IPv6 address. What should we save?
Maybe the questions is: is redudancy a good or bad for us?
Callbacks in the args? Ugh! Let's use promises. That'll help us create multiple nodes for testing as well.
We need to see how multi-node networks work. For that we should create a network of nodes with different network topologies and see how information is propagated and found.
One of the things that come to mind are the seeds of each node. Depending on the topology each node might have a different seed. For example in a ring network we can test what happens when each created node is the seed of the next node.
How fast will we reach a state of entropy? How fast will the search speed be? How big can the indexes get?
Right now it's an application that cannot be easily integrated with others. A better way to do this and make it more usable would be to add more layers:
Application Layer <-- to be written by an app calling us
|
Protocol Layer <-- maybe the API: a set of method that an application server like
| ExpressJS can call
|
Db Layer <-- maybe Waterline ORM or an a custom adapter that calls a DB
With multiple layers it should be easier for dev to integrate the functionality without reimplementing everything.
Move towards read-only nodes (as described in the readme).
Read-only nodes
Each node would either:
- respond to requests from other nodes to read certain information like:
- map of infohashes to torrent names
- list of nodes known to the node
- send such requests to other nodes
This approach could reduce the load on single nodes. It would be up to a node to build its index of torrents and nodes. Any searches would then be done on the local db.
This should make development easier as we don't need to think about searching and would basically be an access point to a db.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.