Now Reading
House | bitmagnet

House | bitmagnet

2023-10-05 06:44:17

A self-hosted BitTorrent indexer, DHT crawler, content material classifier and torrent search engine with net UI, GraphQL API and Servarr stack integration.

bitmagnet WebUI screenshot


This software program is at the moment in alpha. It is able to preview some fascinating and distinctive options, however there’ll probably be bugs, in addition to API and database schema modifications earlier than the (at the moment theoretical) 1.0 launch. In case you’d wish to help this undertaking and assist it acquire momentum, please give it a star on GitHub.

If you’re interested in getting involved and you’re a backend GoLang or frontend TypeScript/Angular developer, or you’re knowledgeable about BitTorrent protocols then I’d like to hear from you – let’s get this factor over the road!

DHT what now…?

The DHT crawler is bitmagnet’s killer characteristic that (at the moment) makes it distinctive. Properly, virtually distinctive, learn on…

So what’s it? You could be conscious that you would be able to allow DHT in your BitTorrent consumer, and that this enables you discover friends who’re asserting a torrent’s hash to a Distributed Hash Desk (DHT), quite than to a centralized tracker. DHT’s lesser recognized characteristic is that it permits you to crawl the data hashes it is aware of about. That is how bitmagnet’s DHT crawler works works – it crawls the DHT community, requesting metadata about every information hash it discovers. It then additional enriches this metadata by making an attempt to categorise it and affiliate it with recognized items of content material, comparable to films and TV exhibits. It then permits you to search all the things it has listed.

Because of this bitmagnet will not be reliant on any exterior trackers or torrent indexers. It’s a self-contained, self-hosted torrent indexer, linked through DHT to a world community of friends and continually discovering new content material.

See Also

The DHT crawler is not fairly distinctive to bitmagnet; one other open-source undertaking, magnetico was first (so far as I do know) to implement a usable DHT crawler, and was an important reference level for implementing this characteristic. Nonetheless this undertaking is not maintained, and doesn’t present the opposite options comparable to content material classification, and integration with different software program within the ecosystem, that tremendously enhance usability.

You can find some more technical details about bitmagnet’s DHT crawler here.

Options & Roadmap

At present applied options

Excessive precedence options not but applied

  • Classifiers for different forms of content material; enrich present classifiers and weed out incorrect classifications.
  • Ordering of search outcomes: the present alpha preview has no facility for specifying the ordering of outcomes.
  • Search efficiency optimisations: search is at the moment quick sufficient to be usable; it turns into extra sluggish as soon as hundreds of thousands of torrents have been listed – there are some low-hanging fruit by way of optimisation that will probably be a near-term precedence.
  • A monitoring API and WebUI dashboard exhibiting issues like crawler throughput, activity queue, database dimension and so on.
  • Authentication, API keys, entry ranges and so on.
  • An admin API, and usually a extra full GraphQL API
  • A extra full net UI
  • Saved searches for content material of specific curiosity, enabling customized feeds along with the next characteristic
  • Sensible deletion: there’s a whole lot of crap on the market; crawling DHT can rapidly use a number of database disk area, and search turns into slower with hundreds of thousands of listed torrents of which 90% are of no curiosity. A wise deletion characteristic would use saved searches to establish content material that you just’re not all for, together with however not restricted to CSAM, and low high quality content material (comparable to low decision films). It will routinely delete related metadata and add the data hash to a bloom filter, stopping the torrent from being re-indexed in future.
  • Bi-directional integration with the Prowlarr indexer proxy: At present bitmagnet will be added as an indexer in Prowlarr; bi-directional integration would permit bitmagnet to crawl content material from any indexer configured in Prowlarr, unlocking many new sources of content material
  • Extra documentation and extra exams!

Pipe dream options

That is the place issues begin to get a bit nebulous. For now all focus is on delivering the core options above, however a few of these concepts might be explored in future:

Source Link

What's Your Reaction?
In Love
Not Sure
View Comments (0)

Leave a Reply

Your email address will not be published.

2022 Blinking Robots.
WordPress by Doejo

Scroll To Top