TIL Torrent Networking

Greetings feeble TCP or QUIC or UDP or even IRC or XMPP packets encapsulating you humans! I'm glad that you've decided to grab the text I have to share with you now here and return it to your interfaces!

It's been a while since I blogged anything, and well, I have something might be useful to you. Ever wonder how the fuck torrent's work? Have you ever used QBittorrent torrent application? This is my favorite Torrent program, which is kind necessary for using torrents.

So my questions were of a few notable ones and here they are:
<code>
<ul>
<li>🕒 i) <big>What does a tracker do?</big> ❓🧨 🧨🧨</li>
<li>🕕 ii) <big>What the heck is DHT?</big> ❓❔🧨 🧨🧨🧨</li>
<li>🕘 iii) <big>Why are my files in little bits and pieces?</big> 🧨 ⁉️🧨🧨</li>
</ul>
</code>

This accompanied with some other curiosities like such as how is it that many people end up sharing bits and pieces of these files with seemingly no order or rhyme or reason? Well the order is like this:

Tracker (torrent file info and original file(s)) ... .. ... I suppose it's a network and/or web location of the actual WHOLE file. Containing also obviously the Torrent File and it acts as the mothership, for say. Now the:
DHT (Decentralized Hashing Table)

.. .... ... is a really cool piece of technology that stashes MASSIVE key:value pairs and an association of all the peers that are connected (to I assume the tracker and DHT). I read maybe that a torrent need not have required to have a tracker file and that in fact in the torrent DHT peers attached to associated torrent info hashes can actually be, in all the amazement of decentralization, automatically discovered without a tracker because a peer alone with just fragments of the file can still be in the DHT. Imagine that eh? Think about that a second or two ..........
Yea so the DHT is like a master database in torrent network that will keep knowledge and route of distance understanding from all peers related to .... files torrented, or, tracker info hashes.
I hope that I am making sense here, and not rambling on, cuz for me I am attempting to hold forefront in my mind the many and somewhat deep things I want to make sure I cover here uwu

Peer (obviously any connected user/network connection to this central interest, being the torrent file(s))

The peer is the user connection but it contains a few things of interest, namely our third question above ^ up there. So how come the files come in randomly as bits and pieces? And in Qbittorrent app you can see a large, say, movie file is got lines of partially completed slices of data. Well reason is because when the torrent was created it was created selecting a certain chunk size, in say 5kb, 1mb, 4096k, 1g, whatever and each chunk is found it's unique hash. Remember the original file will compute it's own LEGIT authentic hash of itself, that should not be deterred from, otherwise the file downloaded corrupt or wrong. So each chunk now has a hash for itself too that will coincide with the master full file hash too. So then when a peer downloads a chunk it will be able to verify the hash sum of that chunk, say is it good then keep it, not good then discard and try again. I don't exactly know but I imagine this is more stuff the DHT (like chronic database of all the things for a torrent) is handling, as key:value pairs including hash sums and such and yea.



Here's some links to some thick and juicy infos about this to help reinforce, or even correct, me in this post as well as give you much much more insight:

<ul>
<li>🧨 Distributed Hash Table (DHT)</li>
<li>🧨 Mainline DHT</li>
<li>🧨 Hash Buckets</li>
<li>👻 Bittorrent Over i2p</li>
<li>🎧 Dubbacle -x- Jah Fire(reason unknown) ..</li>
</ul>


LASTLY SOME NEWS GUYS:
-- News For The8Woodcutter's Webmaster Endeavours --
I am planning on very very soon making the big swing into working on pyblog here as the way I see it now, bash blog, which this blog is based on and uses to operate itself, is extremely non-readable (bash is ugly as fuck) and janky as fuck too to say the least. I think it would be a majorly big bonus to this blog here, and to many others in spaaaaaaaaace, if I got off my lazy ass and made pyblog functional. It's job is simple really, it's job is basically at first to do exactly what this blog does when running the bb.sh script. It will allow text input using your bash $EDITOR to make a post in either ` -html` or markdown format (which is 100% nonfunctional with this exact blog lmao), it will allow posting that post to the post feed, associating the tags u added to the tags list and thus also all posts with similar tags to the tags as posts of tags, ofc... As well as a `bash bb.sh rebuild` which will, say in the event that yuour posts are ordered out of date, and some elements that the bb.sh script assembles (html blocks) are misaligned, it will rebuild like a top to bottom run of MAKE THIS SITE. Also it can `bash bb.sh reset` your blog to original. These are the pretty much functions, oh and to delete a post too, that the bash blog single script to run a blog does. PyBlog will do these things too. BUTMORERERERE!@@@@@@@@@

Yea so I want to get the fuck on that, asap. Then completely TOTALLY redo my blog. Looking forward to that fellows! Hopefully maybe so are you!!!

Tags: networking, protocols, TIL, teaching, learning, researching, themoreyouknow