09:41 |
asciilifeform |
$ticker btc usd |
09:41 |
btcinfobot |
Current BTC price in USD: $56133.31 |
09:41 |
asciilifeform |
!w poll |
09:41 |
watchglass |
Polling 15 nodes... |
09:41 |
watchglass |
185.85.38.54:8333 : Could not connect! |
09:41 |
watchglass |
185.163.46.29:8333 : Could not connect! |
09:41 |
watchglass |
205.134.172.26:8333 : Alive: (0.142s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=681945 |
09:41 |
watchglass |
108.31.170.100:8333 : (pool-108-31-170-100.washdc.fios.verizon.net) Alive: (0.099s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=682067 (Operator: asciilifeform) |
09:41 |
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.) Blocks=682067 |
09:41 |
watchglass |
205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.135s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=682067 |
09:41 |
watchglass |
54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.139s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=682067 |
09:41 |
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=682067 (Operator: whaack) |
09:41 |
watchglass |
208.94.240.42:8333 : Alive: (0.166s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=682067 |
09:41 |
watchglass |
143.202.160.10:8333 : Alive: (0.300s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=682067 |
09:41 |
watchglass |
176.9.59.199:8333 : (static.199.59.9.176.clients.your-server.de) Alive: (0.319s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=412042 (Operator: jurov) |
09:42 |
watchglass |
84.16.46.130:8333 : (182518.pk.3pp.slovanet.sk) Alive: (0.033s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=479228 |
09:42 |
watchglass |
103.36.92.112:8333 : Violated BTC Protocol: Bad header length! |
| |
~ 1 hours 38 minutes ~ |
11:21 |
thimbronion |
verisimilitude: I like some features it has, such as backlinks, comments, and server side text selection. |
| |
~ 42 minutes ~ |
12:04 |
thimbronion |
Additionally billymg has done some work trimming down the source, removing unneeded garbage. |
12:05 |
thimbronion |
I, like many, wrote my own blog, but to get it to the same point os mp-wp would be too much effort. |
| |
~ 1 hours 38 minutes ~ |
13:43 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-05-04#1035590 << the x64 and arm64 gentoos are as similar as i was able to make'em, but with portage snapshot taken at slightly different points in time |
13:43 |
snsabot |
Logged on 2021-05-04 18:15:31 billymg: thimbronion: i got the full mp-wp stack working on BingoBoingo's old rockchips, which i believe were running something very close to that (asciilifeform would likely know the differences) |
13:44 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-05-04#1035589 << i know of several folx who used php on the rk variant (e.g. dpb) but none on the x64 one ( maybe whaack ? ) |
13:44 |
snsabot |
Logged on 2021-05-04 18:07:13 thimbronion: Anyone gotten php/mysql working on a gentoo created using http://www.loper-os.org/pub/dulap_construction_kit_r4.txt? |
13:44 |
* |
asciilifeform personally iirc does not have php on any of his gentoo systems |
13:45 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-05-04#1035616 << billymg if you got this going, plz consider writing crib sheet for the next fella |
| |
↖ |
13:45 |
snsabot |
Logged on 2021-05-04 19:24:14 billymg: thimbronion: fwiw that php emerge just finished successfully |
13:46 |
thimbronion |
asciilifeform: I was able to build php5 using billymg's tarballs. Still working on mysql. |
13:47 |
asciilifeform |
thimbronion: (iirc) i dun have any boxes w/ mysql. but as i understand various things (that i dun use) call for it, so consider to publish, will be handy for'em |
13:48 |
thimbronion |
Perhaps asciilifeform could add what was missing to his mirror? |
13:48 |
asciilifeform |
thimbronion: upload the tarballs to your www, i'ma mirror of course |
13:49 |
asciilifeform |
(assuming they have corresponding hashes in my portage snapshot. not much use if not) |
13:49 |
thimbronion |
asciilifeform: ok - I'll share links for everything once I get mysql working |
13:49 |
asciilifeform |
a++ |
13:49 |
whaack |
asciilifeform: nope I don't have any php on my box |
13:49 |
asciilifeform |
whaack: aa. |
13:50 |
asciilifeform |
then not sure whether anyone has previously tried phpism on my x64 gentoo. |
13:52 |
thimbronion |
I don't even like mysql. Would be happy to use a modified version of mp-wp that uses postgres. |
| |
↖ |
13:53 |
asciilifeform |
thimbronion: i'm prolly the last one to ask re: what, if anything, in that wp is tailored to mysql in particular |
13:53 |
asciilifeform |
possibly -- nothing |
14:00 |
billymg |
http://logs.nosuchlabs.com/log/asciilifeform/2021-05-05#1035654 << this wasn't even on my mp-wp todo list but since using postgres for the crawler it's now jumped near the top |
14:00 |
snsabot |
Logged on 2021-05-05 13:52:26 thimbronion: I don't even like mysql. Would be happy to use a modified version of mp-wp that uses postgres. |
14:02 |
thimbronion |
billymg: yeah it would be nice for any bots to have access to blog posts and logs all using postgres. |
14:02 |
billymg |
yeah, one less dependency to worry about |
14:03 |
billymg |
http://logs.nosuchlabs.com/log/asciilifeform/2021-05-05#1035642 << will get to this eventually, i do want to write some guides |
14:03 |
snsabot |
Logged on 2021-05-05 13:45:24 asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-05-04#1035616 << billymg if you got this going, plz consider writing crib sheet for the next fella |
| |
~ 2 hours 22 minutes ~ |
16:26 |
billymg |
asciilifeform: based on the version msg spec are the addr_me, addr_you values in watchglass encoded in the right order? |
16:27 |
billymg |
i can't tell if they should be flipped or if i'm interpreting the spec wrong in terms of the "receiving/emitting" perspective |
16:33 |
billymg |
going by how the spec describes the 'start_height' as the height of the emitting node and what the watchglass code does there i'm inclined to think the addr values should be flipped |
| |
~ 27 minutes ~ |
17:01 |
verisimilitude |
I'm not being impatient, but let me know when that article of mine is read, asciilifeform, so we may continue our earlier discussion; I mention this purely so it's not forgotten. |
| |
~ 49 minutes ~ |
17:51 |
asciilifeform |
billymg: look at the wg outputs (e.g. today's). if the fields were swapped as you describe, either the addrs or the heights, how would the correct values appear there? (they -- in fact do) |
17:51 |
asciilifeform |
'proof of the pudding' etc. |
17:51 |
asciilifeform |
billymg: comment on www approved. |
17:52 |
asciilifeform |
verisimilitude: will do. |
17:52 |
asciilifeform |
verisimilitude: not forgotten. |
17:52 |
* |
asciilifeform bbl, hands still mostly full |
18:01 |
billymg |
asciilifeform: height field is in the correct position, addrs are in the correct order when you unpack the response payload too http://paste.deedbot.org/?id=R3w- (which is why the results in the output are correct) |
18:02 |
billymg |
it's only where you create the payload for the outgoing message that i think they are flipped http://paste.deedbot.org/?id=5BTe |
18:03 |
billymg |
to me it looks like the order is at least inconsistent in those pack and unpack calls |
18:15 |
billymg |
asciilifeform: i just tested with the values flipped to what i believe to be the correct order and it worked exactly the same as before. so i don't think this has any effect, just something i noticed |
| |
~ 2 hours 6 minutes ~ |
20:21 |
asciilifeform |
ah hm billymg , this kind of thing ? |
20:23 |
* |
asciilifeform will take a closer look when gets the chance |
| |
~ 39 minutes ~ |
21:02 |
billymg |
asciilifeform: more likely it just doesn't make a difference in this particular case. for completeness i tried sending some random ips and the nodes i tried probing still returned valid/correct version messages |
21:04 |
billymg |
tried on both a trb and a prb |
| |
~ 1 hours 22 minutes ~ |
22:26 |
asciilifeform |
billymg: i'm having difficulty picturing how it could make 0 difference -- either they're in the correct order, or they aint..? |
| |
~ 26 minutes ~ |
22:52 |
verisimilitude |
Perhaps the machinery performs reordering by heuristic. |
22:53 |
asciilifeform |
verisimilitude: this aint intercal, lol |
22:54 |
verisimilitude |
This is a guess. |
23:06 |
billymg |
asciilifeform: i'm just reporting back my observations. i tried with bogus IPs ("0.0.0.0" and "8.8.8.8" fwiw) for both the 'addr_recv' and 'addr_from' fields. the nodes i pinged simply did not care what IPs were in these fields and responded with correct/valid version messages of their own |
23:09 |
billymg |
which is funny considering how sensitive they seem to be to the extra 'relay' field at the end and a 99999 value for the version |