#asciilifeform | 2020-08-30

!w poll

16:50

Polling 12 nodes...

16:50

205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.082s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=646032

16:50

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

16:50

108.31.170.3:8333 : (pool-108-31-170-3.washdc.fios.verizon.net) Alive: (0.099s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=646032 (Operator: asciilifeform)

16:50

205.134.172.27:8333 : Alive: (0.095s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=646032 (Operator: asciilifeform)

16:50

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

16:50

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

16:50

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

16:50

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

16:50

213.109.238.156:8333 : Alive: (0.394s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=646030

16:50

188.121.168.69:8333 : (rev-188-121-168-69.radiolan.sk) Alive: (0.228s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=646033

16:50

176.9.59.199:8333 : Busy? (No answer in 20 sec.) (Operator: jurov)

16:50

103.36.92.112:8333 : Busy? (No answer in 20 sec.)

~ 3 hours 16 minutes ~

20:07

http://logs.nosuchlabs.com/log/asciilifeform/2020-08-30#1020790 That was an interesting article.

20:07

Logged on 2020-08-30 09:40:44 feedbot: http://thetarpit.org/2020/adding-a-new-socket-option-to-sbcl-or-common-lisp-is-the-death-of-me << The Tar Pit -- Adding a new socket option to SBCL; or, Common Lisp is the death of me

20:08

I've experienced similar frustrations, so I focus on other things. My EASY-PEASY-TCP may be of some interest; if so, I may resume work on it.

↖

~ 1 hours 31 minutes ~

21:40

feedbot

http://mvdstandard.net/2020/08/germany-people-against-continued-lockdown-rush-reichstag-during-protest/ << The Montevideo Standard -- Germany: People Against Continued "Lockdown" Rush Reichstag During Protest

~ 44 minutes ~

22:24

http://logs.nosuchlabs.com/log/asciilifeform/2020-08-30#1020807 << not that it's in any way a catastrophically-unusable item, but near as i can tell it's simply a wrapper around sb-bsd-sockets . which in turn is simply wrapper around the idjit unix ip stack. to which ~all of the problems of various implementations of sockets in whatever lang, ultimately come back to.

22:24

Logged on 2020-08-30 20:08:47 verisimilitude: I've experienced similar frustrations, so I focus on other things. My EASY-PEASY-TCP may be of some interest; if so, I may resume work on it.

22:32

verisimilitude: tcp per se is a mindbogglingly-braindamaged abstraction that never has been and probably never could be implemented even half-sanely . which limits, to asciilifeform's pov, the appeal of the very idea of 'fixing' it.

↖

22:32

(trilema) 2019-08-01 asciilifeform: reason why 3 decade of 'apache' is same as why erryone (incl. microshit) is using that SAME tcp stack from berkeley '80s. cuz protocol was deliberately made so braindamaged, with literally 10,000+ moving parts, that ~impossible to correctly reimplement if demanding compat with 'everyone'

22:32

(trilema) 2019-08-01 asciilifeform: reason why 3 decade of 'apache' is same as why erryone (incl. microshit) is using that SAME tcp stack from berkeley '80s. cuz protocol was deliberately made so braindamaged, with literally 10,000+ moving parts, that ~impossible to correctly reimplement if demanding compat with 'everyone'

22:33

grr 1st link was supposed to be this

22:33

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 )

22:33

while we're at it, linux's ip stack per se has some overt issues .

22:36

so i'ma say that spyked's complaint is 100% factual, yet misdirected. you CAN'T turn the shitsandwich of tcp-on-linux into a tasty meal by slathering on spackle. of whatever kind.

22:36

Logged on 2020-08-30 09:40:44 feedbot: http://thetarpit.org/2020/adding-a-new-socket-option-to-sbcl-or-common-lisp-is-the-death-of-me << The Tar Pit -- Adding a new socket option to SBCL; or, Common Lisp is the death of me

22:36

(trilema) 2018-10-25 asciilifeform: when you add compatibility spackle, serious reader is not saved from reading the thing you spackled over -- on the contrary nao he has to read the ~original~ rubbish ~plus~ your spackle, however much it weighs.

22:38

to imho no possible surprise, shit dun go away! when you spackle over it. instead you get shit+spackle, which is simply a greater mass of shit.

22:38

!q seen-anywhere spyked

22:38

spyked last seen in #asciilifeform on 2020-06-18 10:08:47: asciilifeform, danke. fixed and answered: http://thetarpit.org/2020/a-cursory-look-at-the-infamous-trb-wedge-bug#comment-353

22:39

eh he aint even tuned in, apparently.

22:40

I've not finished it, but the library experiment is intended to be an interface for TCP, across several implementations. That's all. Rather than be strangled by new #define garbage, it would aim for a ``one-size-fits-all-or-go-away'' approach.

22:42

verisimilitude: how do you intend to implement 'tcp spackle for sbcl + buncha others' w/out ifdefism ?

~ 17 minutes ~

23:00

I just have #+ for the supported implementations.

23:00