00:00 |
billymg |
regarding my own logotron mirror, i still haven't gotten around to implementing a fix for the postgres timeouts because i was hoping i could avoid it once it's up on new hardware |
00:00 |
dulapbot |
Logged on 2021-10-15 22:48:27 asciilifeform: ( and to billymg's item if he's still interested ) |
00:02 |
billymg |
once it's back up, either on a more powerful box or with a fix, i'll backfill all the lines missed since http://logs.nosuchlabs.com/log/asciilifeform/2021-09-01#1055943 |
00:02 |
dulapbot |
Logged on 2021-09-01 22:35:49 bitbot: billymg: time since my last reconnect : 0d 0h 0m |
| |
~ 6 hours 3 minutes ~ |
06:05 |
verisimilitude |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-21#1061624 There's no reason to adhere to that stupid convention, cgra. I use one hundred columns as my limit, and it's just as reasonable as eighty, I'd argue more, since I avoid being so constrained for space. |
06:05 |
dulapbot |
Logged on 2021-10-21 13:17:46 cgra: noob question inbound...: why should a software author adhere to 80 columns? |
| |
~ 7 hours 24 minutes ~ |
13:29 |
signpost |
it's just a relic of old terminal widths. |
13:32 |
signpost |
it's one of those things where most people require a rule to stay sane, where others can use their judgment. |
13:33 |
signpost |
there are plenty of cases where breaking a line to obey the rule makes the code harder to grok. |
13:48 |
signpost |
asciilifeform: I'm finally cramming ada into my head over here. given the amount of time I spent with pl/pgsql in a past life, the pascal-like syntax isn't even weird. |
| |
↖ ↖ |
13:51 |
* |
signpost notes that it's a little over year and a half since #t was shuttered, and he's shifting life to focus on bitcoin and related work. |
13:52 |
signpost |
on the timescale of republics, I don't think that's such a bad score. |
13:53 |
signpost |
pity the bottle swallowed the old man, then the sea swallowed the bottle, but it doesn't change anything for me. |
13:54 |
* |
signpost will get back to publishing interesting items before long. |
13:56 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061867 << indeed pascalesque, was 1 of the initial appeals for asciilifeform |
13:56 |
dulapbot |
Logged on 2021-10-26 09:48:01 signpost: asciilifeform: I'm finally cramming ada into my head over here. given the amount of time I spent with pl/pgsql in a past life, the pascal-like syntax isn't even weird. |
13:57 |
signpost |
way less cognitive load than "what's this fucking bracket paired with again?" |
14:01 |
asciilifeform |
signpost: the design objectives were baked around 'coad must be readable or we might lose a space battleship' and it shows imho |
14:04 |
signpost |
indeed, clarity to reader as well as compiler |
14:04 |
signpost |
I will probably take some time before being useful in this language, but seems worth the time. |
14:10 |
asciilifeform |
signpost: imho ffa is the closest thing existing atm to a clean ada intro course |
14:10 |
* |
asciilifeform recommends, lol |
14:13 |
signpost |
major reason I want to grok ada. |
14:23 |
asciilifeform |
signpost: must note though that ffa doesn't cover the 'gnarly'/cppesque features of the language, deliberately avoids. (and they aint entirely useless, e.g. nqb makes use of some, chiefly streams) |
14:26 |
* |
signpost probably wants streams for the xor-a-tron too, but makes sense to stay simple for ffa. |
14:27 |
asciilifeform |
streams in nqb on account of the gnarly tcpism of the bitcoin wire protocol, with its various 'variable-length' turds |
14:28 |
asciilifeform |
(and in general they're the correct abstraction when a format contains variably-long crapola and no one has any idea what before parser eats it) |
14:28 |
asciilifeform |
imho one oughtn't perpetrate these tho, when has a choice. |
14:30 |
* |
signpost will have to sink into it to have a good opinion on whether to use. |
14:31 |
* |
asciilifeform as noted in 'trbi' threads, would've made e.g. fixed 1024byte tx, and 1024 of'em per block, or somesuch. but in trad bitcoin we have what we have. |
14:32 |
asciilifeform |
'nqb' was actually about this -- attempt to represent traditional tx/blox in a maximally, as possible, 'trbi'-like form, for O(1) storage/retrieval. |
| |
↖ |
14:32 |
signpost |
in the case of onlinecodes, counterparty hucks you udp packets representing check blocks, and you know how much stuff you should receive before the original message is solvable. |
14:33 |
asciilifeform |
right |
14:33 |
asciilifeform |
imho doesn't require a stream abstraction. but i expect will be clearer once you bake prototype |
14:34 |
* |
signpost has thought ring buffers might be appropriate. |
14:35 |
signpost |
oughta be able to alloc a suitable size right at the beginning, pop check blocks into it, then either write the solved message to a second array, or disk |
14:35 |
asciilifeform |
signpost: i'd expect the initial 'here's a warez' packet will have the final size & hash in it |
14:36 |
asciilifeform |
so can preallocate. |
14:36 |
signpost |
yep indeed |
14:36 |
asciilifeform |
( preallocate with 'cryostat', naturally ) |
| |
↖ |
14:37 |
asciilifeform |
really does take ~100% of the headache outta 'need megaturd in memory, for possible save to disk' etc |
14:37 |
signpost |
oooh yes, had forgotten. |
14:37 |
* |
asciilifeform wrote it chiefly for use w/ 'nqb' |
14:37 |
* |
signpost will review 100% of asciilifeform's ada material before setting off. |
14:38 |
asciilifeform |
'cryostat' is simply a clean (imho) bolting of mmapism to gnat. |
14:38 |
asciilifeform |
is enabled by the a++ lang feature where can 'for Item'Address use GetAddress(Map);' |
14:40 |
asciilifeform |
in c world, this kinda thing is inevitably an ocean of pointerisms and pestilential typecasts errywhere |
14:41 |
asciilifeform |
whereas here, can avoid, and then use the map 100% as if it were an ordinary stack variable. |
14:41 |
asciilifeform |
saves to disk when goes outta scope, too. |
14:42 |
asciilifeform |
so in principle can take any ada proggy and make its state persistent, with coupla ln added. |
14:43 |
asciilifeform |
given as ada gives you full control over allocator, could even make the entire stack persist. |
14:45 |
* |
asciilifeform sadly not had chance to weld 'cryostat' to 'nqb', got into an unspeakably arduous commercial contract soon after publishing the former, and still mired in liquishit |
| |
↖ |
14:51 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-25#1061855 << will take a look. thx billymg ! |
14:51 |
dulapbot |
Logged on 2021-10-25 19:50:06 billymg: asciilifeform: my fix for one bug created another. search results use span.highlight, which the div.highlight no longer targets. it should have both, like this |
14:58 |
asciilifeform |
!q uptime |
14:58 |
dulapbot |
asciilifeform: time since my last reconnect : 132d 11h 55m |
14:58 |
asciilifeform |
$ticker btc usd |
14:58 |
busybot |
Current BTC price in USD: $62021.95 |
14:58 |
asciilifeform |
!w poll |
14:58 |
watchglass |
Polling 17 nodes... |
14:58 |
watchglass |
84.16.46.130:8333 : Could not connect! |
14:58 |
watchglass |
185.85.38.54:8333 : Could not connect! |
14:58 |
watchglass |
185.163.46.29:8333 : Could not connect! |
14:58 |
watchglass |
205.134.172.27:8333 : Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 (Operator: asciilifeform) |
14:58 |
watchglass |
205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.081s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=706802 |
14:58 |
watchglass |
71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.118s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 (Operator: asciilifeform) |
14:58 |
watchglass |
54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.111s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 |
14:58 |
watchglass |
205.134.172.26:8333 : Alive: (0.129s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=706802 |
14:58 |
watchglass |
205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.143s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 |
14:58 |
watchglass |
208.94.240.42:8333 : Alive: (0.225s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 |
14:58 |
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=706773 (Operator: whaack) |
14:58 |
watchglass |
213.109.238.156:8333 : Alive: (0.332s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 |
14:58 |
signpost |
cryostat seems like exactly the thing, looking forward. |
14:58 |
watchglass |
143.202.160.10:8333 : Alive: (0.520s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 |
14:59 |
watchglass |
103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.594s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706802 |
14:59 |
watchglass |
176.9.59.199:8333 : (static.199.59.9.176.clients.your-server.de) Alive: (0.638s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=483140 (Operator: jurov) |
14:59 |
watchglass |
54.38.94.63:8333 : Violated BTC Protocol: Bad header length! |
15:00 |
watchglass |
192.151.158.26:8333 : Busy? (No answer in 100 sec.) |
| |
~ 1 hours 34 minutes ~ |
16:34 |
cgra |
thanks asciilifeform, verisimilitude and signpost for 80 col comments. personally had already also developed a general feel of around 100-120 col being "most comfortable". now summarized in my own head that need 80-90 col only mostly if want to unconditionally support code on paper. |
| |
↖ |
16:44 |
cgra |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061867 << i remember as a teen/kid (forgot year exactly) to prefer learning pascal over c/c++, and kept sticking to pascal and thinking why is c++ so damn weird, like 'std::out << "printed text"' |
| |
↖ |
16:44 |
dulapbot |
Logged on 2021-10-26 09:48:01 signpost: asciilifeform: I'm finally cramming ada into my head over here. given the amount of time I spent with pl/pgsql in a past life, the pascal-like syntax isn't even weird. |
16:46 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061936 << i do the paper thing for just about any nontrivial item (i.e. that takes >1d of thought) so muchly prefer 80. |
| |
↖ |
16:46 |
dulapbot |
Logged on 2021-10-26 12:34:24 cgra: thanks asciilifeform, verisimilitude and signpost for 80 col comments. personally had already also developed a general feel of around 100-120 col being "most comfortable". now summarized in my own head that need 80-90 col only mostly if want to unconditionally support code on paper. |
16:47 |
asciilifeform |
(and fits on vertical display in reasonably large letters w/out horiz. scrolling or wrap) |
| |
↖ |
16:47 |
asciilifeform |
wrapping fucks up indentation |
16:48 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061937 << 'syntactic sugar causes cancer of the semicolon'(tm)(r) |
16:48 |
dulapbot |
Logged on 2021-10-26 12:44:23 cgra: http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061867 << i remember as a teen/kid (forgot year exactly) to prefer learning pascal over c/c++, and kept sticking to pascal and thinking why is c++ so damn weird, like 'std::out << "printed text"' |
16:49 |
* |
asciilifeform working w/ commercial client who doesn't do 80col (or any limit at all) and the coad looks like shit on paper |
| |
↖ |
| |
~ 15 minutes ~ |
17:05 |
cgra |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-26#1061941 << how many columns (in reasonably large letter size) does your typical vertical display have? |
17:05 |
dulapbot |
Logged on 2021-10-26 12:47:09 asciilifeform: (and fits on vertical display in reasonably large letters w/out horiz. scrolling or wrap) |
| |
~ 48 minutes ~ |
17:53 |
asciilifeform |
cgra: 80, lol |
| |
↖ ↖ |