/b/ - random

and nothing of value was lost


New Reply
Sage
×
Message
Files Max 5 files1000MB total
Tegaki
Password
[New Reply]


✞
Psalm 94


hqdefault.webp
[Hide] (20KB, 480x360) Reverse
Eat some Chinese food
I'm good I just had chicken kiev
Replies: >>8691
https://youtu.be/THH7P08zuhU
Replies: >>8692 >>8693
>>8682
Okay
Replies: >>8695
>>8690
What's this?
Replies: >>8695
>>8690
You forgot the english version, right?
Replies: >>8695 >>8700
>>8691
>>8692
>>8693
be quiet
FUCKING MAGNETS, HOW DO THEY WORK?
Replies: >>8697
>>8696
Hi IHM,

A BitTorrent magnet link identifies a torrent using1 a SHA-1 or truncated SHA-256 hash value known as the "infohash". This is the same value that peers (clients) use to identify torrents when communicating with trackers or other peers. A traditional .torrent file contains a data structure with two top-level keys: announce, identifying the tracker(s) to use for the download, and info, containing the filenames and hashes for the torrent. The "infohash" is the hash of the encoded info data.

Some magnet links include trackers or web seeds, but they often don't. Your client may know nothing about the torrent except for its infohash. The first thing it needs to is find other peers who are downloading the torrent. It does this using a separate peer-to-peer network2 operating a "distributed hash table" (DHT). A DHT is a big distributed index which maps torrents (identified by infohashes) to lists of peers (identified by IP address and ports) who are participating in a swarm for that torrent (uploading/downloading data or metadata).

The first time a client joins the DHT network it generates a random 160-bit ID from the same space as infohashes. It then bootstraps its connection to the DHT network using either hard-coded addresses of clients controlled by the client developer, or DHT-supporting clients previously encountered in a torrent swarm. When it wants to participate in a swarm for a given torrent, it searches the DHT network for several other clients whose IDs are as close3 as possible to the infohash. It notifies these clients that it would like to participate in the swarm, and asks them for the connection information of any peers they already know of who are participating in the swarm.

When peers are uploading/downloading a particular torrent, they try to tell each other about all of the other peers they know of that are participating in the same torrent swarm. This lets peers know of each other quickly, without subjecting a tracker or DHT to constant requests. Once you've learned of a few peers from the DHT, your client will be able to ask those peers for the connection information of yet more peers in the torrent swarm, until you have all of the peers you need.

Finally, we can ask these peers for the torrent's info metadata, containing the filenames and hash list. Once we've downloaded this information and verified that it's correct using the known infohash, we're in practically the same position as a client that started with a regular .torrent file and got a list of peers from the included tracker.

The download may begin.

Hope this helps!!1!
Replies: >>8698 >>8699
Screenshot_20231228_054437_Finder.jpg
[Hide] (728KB, 1080x2400) Reverse
>>8697
orly
>>8697
Enjoy your captcha, sand nigger
>>8693
Nice report faggot
Replies: >>8701
>>8700
Kys
Replies: >>8703
>>8701
>cyber attacking

wow you're actually serious arent you
Replies: >>8704
>>8703
Yea
Replies: >>8705
>>8704
I mean it!
Replies: >>8708
>>8705
I really don't know what to make of you
Replies: >>8709
>>8708
Same

USER WAS BANNED FOR THIS POST Fly away, Sky UK

[New Reply]
Connecting...
Show Post Actions

Actions:

Captcha:

- news - rules - faq -
- irc - telegram -
jschan v. [ARBITRARY NUMBER]