01:19:33 <moneromooo> tevador: sech1: any of you around on a relay ?
11:20:03 <asn> 15:43 < tevador> asn: I guess the maximum queue size should be around 6000 requests, assuming 200 req/sec. bottom half throughput and 30 sec. client timeout
11:20:07 <asn> 15:43 < tevador> asn: I guess the maximum queue size should be around 6000 requests, assuming 200 req/sec. bottom half throughput and 30 sec. client timeout
11:20:11 <asn> 15:43 < tevador> asn: I guess the maximum queue size should be around 6000 requests, assuming 200 req/sec. bottom half throughput and 30 sec. client timeout
11:20:13 <asn> 15:43 < tevador> asn: I guess the maximum queue size should be around 6000 requests, assuming 200 req/sec. bottom half throughput and 30 sec. client timeout
16:19:22 <kinghat[m]> interesting little board: https://www.anandtech.com/show/15835/asrock-rack-offers-rome-matx-motherboard-with-only-6-memory-channels
21:43:51 <hyc> hey, our Azure buddy made ars technica
21:43:54 <hyc> https://arstechnica.com/information-technology/2020/06/machine-learning-clusters-in-azure-hijacked-to-mine-cryptocurrency/?utm_brand=arstechnica&utm_source=twitter&utm_social-type=owned&utm_medium=social
21:46:23 <hyc> so was he technically telling the truth that it wasn't a botnet? you decide ...
21:46:45 <hyc> Changing machine learning to machine earning ...
21:47:33 <hyc> M5M400: I suspect M$ might be interested in any contact info you have on that guy
21:49:47 <jwinterm> lol
21:50:25 <selsta> 92.158.90.151 was their IP
21:50:49 <hyc> if that was the address of a miner, it's probably just an azure address
21:50:56 <selsta> no, IRC ip
21:50:59 <hyc> ah
21:53:04 <hyc> and gotta wonder how he got away with inserting a miner into a public kubernetes binary