Making the (partial) Rust BitTorrent client more reasonable

nice thumbnail

🥤🍿

Your videos are invaluable to the intermediate Rust community, Jon!

The thumbnail lol

A sequel to the famed classic!

self.offset in DownloadedIter equals to 0 and still unchanged or I missed something?

One architecture optimization (dont really know what to call this) i would make is to have a function called download block range and have that be where you deal with all the complex logic that you dealt with in downloaded. Then download all would just call the entire range and for any specific set of files you would figure out what blocks you need. Now, becuase of the possible overlap of pieces across blocks, it is possible that you download a block multiple times in a download all.

Edit: or maybe I am misunderstanding how files/pieces/blocks work.

How would you go about testing this implementation in a robust manner? Seems difficult to create all the edge cases of disconnections, retransmissions, etc.

I'd love to see what a 'from scratch' impl would look like as opposed to using (mostly) just the crates from the Codecrafters challenges. One example I could think of is using nom for bencode instead

Just wanted to say thanks for having made my Rust learning experience in the past really enjoyable. Totally unrelated question, but what kind of zip neck sweater are you wearing?

Your colorscheme/theme is really niceeeeeeeeeeeeeeee!!!!! what is it, (it's not gruvbox) i checked your config files but cannot implement the same in mine, how can i get a theme like yours....

What did you mean by referring to async_channel as smoll-rs based one? It doesn't depend on smoll-rs runtime.

Although I don't code in Rust this is really fascinating!

could you make a video on implementing the Bittorrent DHT Protocol ? I would really love to see that on your channel :)

really fascinating stuff, hoping to see more like this

Thank god we replaced all those nasty single digit "8"s with a scoped constant and two nested casts