#asciilifeform | 2021-02-26

verisimilitude: I'm slowly working on writing a torrent client; I've already finished implementations of SHA-1.

btcinfobot: Current BTC price in USD: $46213.67

watchglass: Polling 15 nodes...

watchglass: 185.85.38.54:8333 : Could not connect!

watchglass: 185.163.46.29:8333 : Could not connect!

watchglass: 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.023s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=672305

watchglass: 205.134.172.26:8333 : Alive: (0.082s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=672305

watchglass: 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.142s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=671841

watchglass: 54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.137s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=672222

watchglass: 205.134.172.28:8333 : Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=672274 (Operator: whaack)

watchglass: 108.31.170.100:8333 : (pool-108-31-170-100.washdc.fios.verizon.net) Alive: (0.147s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=672305 (Operator: asciilifeform)

watchglass: 192.151.158.26:8333 : Alive: (0.093s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=672305

watchglass: 208.94.240.42:8333 : Alive: (0.101s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=672305

watchglass: 143.202.160.10:8333 : Alive: (0.254s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=672305

watchglass: 84.16.46.130:8333 : Violated BTC Protocol: Bad header length!

asciilifeform: verisimilitude: torrent is 1 of those garbage protocols where it's astonishing that the thing worx at all.

shinohai: asciilifeform: re: torrent I did finally get rtorrent to eat larger files, but now refuses to open it, logs show nothing helpful so will spelunk further when I have a bit of extra time.

asciilifeform: shinohai: i've nfi; i tested w/ cli version of 'transmission', worx

asciilifeform: someone (maybe dpb?) is downloading on an uncommonly slow pipe (dialup?)

asciilifeform: plenty of bw in the cage to spare. as before, can get 1-2MB/s from desk, from lulazon, etc

shinohai: magnet:?xt=urn:btih:SUA4AWPBH6EOF6RYVHKOVBNPOVAYTAAK&dn=trbdb&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce <<< shows 1 peer, 1 seeder indeed.

asciilifeform: shinohai: hm, i'm seeding from 2 separate boxen. but possibly above is consistent w/ this

shinohai: And at risk of getting booted off net, I decided to try w/ local copy of rtorrent, and it works just fine. O.o

shinohai: (But this is Gentoo box with hand-built copy)

asciilifeform: shinohai: worx in what sense ? i still see '1 leech' (and on strictly 1 box, other shows 0..)

asciilifeform wonders whether torrentism even works reliably with fingers-of-one-hand # of seeders

shinohai: oh well, loads up it appears then drops connection. Scratch that.

shinohai: Gonna try net-p2p/transmission and see what happens.

verisimilitude: I've had success seeding a file to but one other individual, asciilifeform.

verisimilitude: We were the only two torrentors for it, as well.

asciilifeform: verisimilitude: sounds like rather inefficient way to move 1file.. i attempted torrentism strictly because already have the thing on 2 boxen in 2 separate locations, and dpb was suspecting pipe shenanigans

verisimilitude: In my case, it was the only way to do it, because I typically have such a slow Internet connection, but there were other constraints I won't list.

asciilifeform: aite

shinohai: rsync far more reliable than torrenting

verisimilitude: It makes sense the original torrent client was written in Python. This allowed the author to simply toss whatever he wanted in without regard for implementing it.

feedbot: http://thetarpit.org/2021/diablo-iii << The Tar Pit -- Diablo III

verisimilitude: Speak of the devil.

asciilifeform: lol

dpb: yes i am leeching, and i'm only getting it from one peer/seed -- am i configured wrongly?

asciilifeform: dpb: does your client permit manual adding of peer ?

asciilifeform: dpb: try adding ip of my 2nd mirror into yer client

snsabot: Logged on 2021-02-26 12:50:21 watchglass: 108.31.170.100:8333 : (pool-108-31-170-100.washdc.fios.verizon.net) Alive: (0.147s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=672305 (Operator: asciilifeform)

verisimilitude: What's wrong with torrenting in principle, asciilifeform? It's a decent example of a P2P, random access, file-sharing protocol. The primary issue I recall is torrents being unable to share seeders for identical data.

asciilifeform: verisimilitude: tcp.

asciilifeform: ... e.g.

snsabot: Logged on 2020-07-07 18:15:34 asciilifeform: megatonne of discussion in ye olde logs re braindamage of tcp (where e.g. any idjit can RST yer connection, or SYN flood, or make educated guesses re payloads via the plaintext sequence #s, etc )

dpb: asciilifeform, you have transmission in your public distfiles but i don't have the ebuild and other files for those versions

asciilifeform: dpb: lemme guess, this is on rk ?

asciilifeform not attempted torrentism on rk

dpb: no not a rk

asciilifeform: in standard dulap gentoo, net-p2p/transmission

dpb: yes

asciilifeform: all boxen baked via my recipe, have a working ebuild. 2.92-r2.

asciilifeform: or, dpb , do i misunderstand? what's missing on yours ?

dpb: that ebuild tries to download transmission-2.92 from not-dulap and i already manually downloaded transmission-2.84 from your public distfiles

asciilifeform: dpb: plz try again, i uploaded 2.92 from local collection

dpb: that works. ty

asciilifeform: dpb: np

verisimilitude: Torrents can work over UDP.

asciilifeform: verisimilitude: afaik only carries dht peer tracking via udp. (and even this, optional)

asciilifeform at one pt did not know this, thought that bt actually goes via udp.

asciilifeform: ( and see also e.g. )

snsabot: (trilema) 2019-05-29 asciilifeform: the protocol is 'fractally retarded' -- i.e. broken on absolutely erry possible level. starting from where it takes exactly 1 trivially forged packet to close someone's connection, to where 'allcomers' get a substantial chunk of memory allocated , and make ddos trivial , to where it forces 9000x moar complicated design of routing gear, to... could continue but why.

snsabot: (trilema) 2019-05-29 asciilifeform: tcp shows erry possible sign of having been designed, from the start, to extend the ease of snoopage from traditional circuit-switched telco grid, to the packet world. consider e.g. the 'helpfully' plaintext sequence numbers.

asciilifeform: dpb et al : for testlulz i set up a seed on lulazon; currently pulling ~1MB/s

asciilifeform: for some unknown reason -- only from dulap

asciilifeform: i suspect the trackers i used when setting the thing up, are broken

asciilifeform: ... loox like propagated eventually.

asciilifeform: dpb i gotta ask, are you on a sat dish, or wat

dpb: yes

asciilifeform: ( seems like yer pipe peaks at ~200kB/s -- and even that for only 10-20sec / min )

asciilifeform: aaa

dpb: this is the worst time of day to be testsing it

dpb: but i am simultaneously streaming video from youtube so it is not a matter of the satelite dish not having enough bandwidth

asciilifeform: a

asciilifeform: anyways the lulazon box is eating at ~10M/s, i expect will sync tomorrow. i'ma leave it up for a while, along w/ the 2 others, until moar folx seed.

asciilifeform: dpb: reason for this experiment, is that you piqued my curiosity re a possible choke b/w you and dulap

asciilifeform: wanted to rule out this hypothesis.

asciilifeform still thinks this is a lame method for propagating trb blox; but imho oughta be avail. to folx who desperately want noad asap

asciilifeform: dpb: ftr i suspect that it aint yer dish, per se, that has insufficient bw -- but the upstream link. among the sadder isp in usa there is a trend of let's cache youtube et al, it's 98% of usage anyway, while leave pittance for actual net traffic

asciilifeform: iirc the dc that once housed piz, ended up as a netflix cache, of exactly this variety

shinohai: Left mine running for a while to see if it would eventually connect, so far 0

asciilifeform: shinohai: the 1 on lulazon took almost 30m to find the peers

shinohai: jeez

asciilifeform bbl

verisimilitude: Criticizing TCP for ``plaintext sequence numbers'' is unreasonable; the entirety of it is unencrypted; an old extension even has packet security levels such as ``top secret'', for controlling transmission in ``high-security'' networks.

verisimilitude: I've made a mistake; I was thinking of IP, not TCP.

trinque: that it is unencrypted is the critique.

trinque: at least of that aspect.

verisimilitude: UDP is also unencrypted.

verisimilitude: It's not an invalid critique, just unreasonable in context.