Hyperblow - A torrent client that throws real left blow

Currently this project is in a complete rewrite

Tired of seeing boring TUI based Bittorent Clients? Here comes hyperblow, a modern Bittorent Client that uses Bittorent Protocol V1. A rich TUI, with modern features in TUI.

Screenshots of TUI

Dummy Details Tab Screenshot

It's gonna take time, good things do take time

Debug logging

Hyperblow writes opt-in diagnostic logs to stdout when HYPERBLOW_LOG is set:

HYPERBLOW_LOG=debug cargo run -p hyperblow-cli -- --help

For focused torrent diagnostics, use:

HYPERBLOW_LOG=hyperblow_cli=debug,hyperblow=debug cargo run -p hyperblow-cli

This includes tracker announce results, peer connection failures, piece requests, and completed pieces.

For a running TUI, stdout logs are useful for debugging but can mix with the alternate-screen UI.

✅ Denotes work is fully done ☑️ Means work is partially done ☐ Means the work is far from done

Features checklist :

• ✅ Accepts torrent file as input
• ✅ Accepts magnet uri as input
• ☑️ Support for partial download, that is checking the items we want to download
• ✅ Support for UDP Trackers
• ☐ Support for HTTP Trackers
• ☐ Has rare piece first algorithm
• ☐ Implements Choking and Unchoking Algorithm

Supported BEP's:

• ✅ BEP15 : UDP Tracker Protocol (Implements partially, except scrape req and res)
• ✅ BEP12 : MultiTracker Metadat Extension
• ✅ BEP20 : Peer ID Convention

TODO :

• ✅ Implement the ".torrent" file parser
• ✅ Implement the MagnetURI verifier and parser
• ✅ Handle redundancy of both the tracker URL's in "announce" and "announce-list" field, used BEP12
• ☐ Upload Architecture and working methods of both Tracker and Peer
• ☐ Make use of Crossbeam crate's Concurrency Primitives
• ☐ Add both Unit and Integration testing for the parsing library
• ☐ Re architect the entire CLI application's system design