25100+ entries in 0.014s
mod6: I
think my head must be broken, because
the stress of making a decision wrong is paralyzing.
mod6: I've been pondering mircea_popescu's
reponse to
the above link since
the statement was made. I'm not sure how I went wrong here, but not adding
to
the existing SHA512 vtree is what I understood my instructions
to be.
☝︎ mod6: le, could begin retroactively
testing & adding
these older submissions into
the
tree.
☟︎ a111: Logged on 2019-07-24 00:56 mod6:
http://btcbase.org/log/2019-07-19#1923606 <<
This is a neat-o vpatch
'who gave', but it came in just after
the 'NO NEW WORK IN SHA PLOX'; so
there are a few like
this
that probably will go into
TRB main Vtree once
the Lordship reviews/audits
the proposed Keccak
TRB Vtree; perhaps possibly after
TRB has a new home OS/environment.
a111: Logged on 2019-08-01 21:49 asciilifeform: !Q later
tell mod6 is something wedging your conveyor re eating patches ? plz do say. cuz e.g. detruncation is iirc >1y old nao
mod6:
http://btcbase.org/log/2019-08-01#1926112 <<
These go back
to
this, I did
test
those ones when
they came in. iirc
they did work alright when I
tested
them. I stopped adding
these items
to
the working vtree (SHA512) when mircea_popescu said, and instead started working
towards getting
the keccak vtree built &
then getting it onto cuntoo. Figured once
there & stab
☝︎☝︎ a111: Logged on 2019-08-01 12:41 lobbes: mp_en_viaje: re: lobbesbot.
The heathen VPS it is hosted on is migrating
their servers. Hopefully will be back online in 24 hours (I didn't want 100% of my stuff on Pizarro; potential central point of failure and all)
a111: Logged on 2019-08-01 21:01 dorion: I have a
trb node pressed
to asciilifeform_aggressive_pushgetblocks.vpatch plus a local modification
to add a new rpc.
This node was was fully synced for a couple days, but has failed
to verify block 588012.
dorion: it also returns
this on getbalance, listtransaction, etc.
dorion: after restarting with -caneat, bitcoind eatblock 588012.blk returns: error: {"code": -2, "message":"Safe mode: WARNING: Displayed
transactions may not be correct! You may need
to upgrade, or other node may need
to upgrade."
dorion: asciilifeform de-truncation is marked experimental on btcbase.org/patches and
thebitcoin.foundation/v/patches
dorion: when I grep 0000000000000000000ba68c82d9b620cf028f0642c833a5eda92dbf68d5a3fb debug.log it reports
to have
dorion: Given
the
truncated hashes, I pressed
to asciilifeform_whogaveblox.vpatch (which includes mod6_excise_hash_truncation.vpatch), stopped
the node and restarted with
the new binary.
dorion: because
the hash is
truncated in
the log, it only indicates
the leading b for 588012.
mp_en_viaje: is it actyually block 588012 hash 0000000000000000000ba68c82d9b620cf028f0642c833a5eda92dbf68d5a3fb ? or is it
the next, hafsize one, hash 0000000000000000001498ec3c9796a44b53b8b70186920d15a5e34afcaaa719 ?
dorion: The remainder of
that file is
the remainder of
the hour in which it attemps several reorgs.
dorion: I have a
trb node pressed
to asciilifeform_aggressive_pushgetblocks.vpatch plus a local modification
to add a new rpc.
This node was was fully synced for a couple days, but has failed
to verify block 588012.
☟︎ a111: Logged on 2019-08-01 17:20 asciilifeform: if it's 1 of
those lulzy 'faux crypto via js'
things, costs having-to-login-from-js-browser neh.
mp_en_viaje: this is basically
the discussion here, properly identify
the quantified states.
mp_en_viaje: especially seeing how nobody is forced or required
to fucking use it ; not for a while anyways. can always fall back on present c-ism if would rather.
mp_en_viaje: but now ~that
there is structure of authority~... eminently CAN
tell.
mp_en_viaje: it makes no fuckin gsense at no node in
the whole fractal
tree of stupid.
mp_en_viaje: why
the fuck would lisp webserver serve ANYTHING ELSE
mp_en_viaje: which rapidly collapses "lisp webserver" into gossipd and all
that.
mp_en_viaje: and if not wanna actually fuck,
then get out of
the night club, go home, have a
tea
mp_en_viaje: but
the stance seems
tenable
that if we're gonna go
to all
the
trouble
to make and maintain lisp webserver, might as well make a non-fucked one and make new browsers for it
mp_en_viaje: it is very evidently and most eminently
the only rught
thing.
a111: Logged on 2019-08-01 15:53 asciilifeform: ever wonder why heathens still fascinated, like
chukchas with radio found in taiga, with 'bittorrent' ? it's because warez goes at ~line rate~ over 'bittorrent'. and at maybe 2/3 line rate on
http on a good weather day. why? cuz bt , despite authored by idiot, ~let go of
tcpism~ !
mp_en_viaje: besides,
the mechanism splendidly demonstrared in
torrents, not like
this is arcana
toch
a111: Logged on 2019-08-01 15:44 asciilifeform: on
top of
this : could just as easily serve a page from cluster of boxes instead of merely 1 (there's nothing preventing
the slices from being generated wherever you want)
mp_en_viaje: irrespective of how it gets in --
the fact remains, it's STILL not lisp, even if "written in lisp". cuz it's "written in lisp*" where * = as if it were not lisp
mp_en_viaje: anyway, i'm not proposing any hangings
today ; but we also can't just completely ignore
this ridiculousness wtf.
mp_en_viaje: asciilifeform,
that might be an argument for ada. but not for lisp. lisp comes with interpreter costs etc.
mp_en_viaje: i also do not believe
that going about in ox-drawn carts with "Mercedesuzuki" spray-painted on
the sides "will aid people
to migrate
to cars later" or anything
mp_en_viaje: i don't specifically care re
the culprint ; but i do not see
the wisdom of having a lisp server if it looks like
that. for one
thing, if you just make it honest c more people can be found
to debug it.
a111: Logged on 2019-08-01 15:40 asciilifeform: spyked: imho your 'hunchentoot' vivisection illustrates important point : just how much of
the complexity of
that
thing is on acct of idjit
tcpism's shit abstractions, i.e.
the lengths
to which it goes
to pretend
that
the machines aint exchanging short packets in quasi-reliable ordering
mp_en_viaje: it's
the exact equivalent of enunciating english words with an o at
the end
to speako el mexicano, understando ?
mp_en_viaje: why
the fuck is
this hunchenback even written in lisp ? it's pure python, why not just write it in python and be happy.
mp_en_viaje: in other scandal, by
the
time i hit "[wafs] wake-acceptor-for-shutdown" in spyked 's story i'm so fucking pissed off i can't even continue reading.
mp_en_viaje: (fwiw,
trilema spits out deliberately invalid html, also)
mp_en_viaje: if it works
there it's almost certain such a subtle error in your
theme, as an uncliosed div or span or such
mp_en_viaje: shrysr, indeed, wanna
try
the select on my page on yoru browsers ?
mp_en_viaje: shrysr,
the current
theory seems
to be indeed his : your page is subtly broken somewhere else, which makes
this not work on some browsers but not others. put it
through validators see if you can find
the unclosed
tag or we/
shrysr: asciilifeform: ok, will check and revert. but damnnnnnn its working somewhere..rofl. Its such a cool
thing and I don't know why its not standard.
a111: Logged on 2018-02-02 16:23 asciilifeform:
the 'postel's law' nonsense, of silently forgiving people who send liquishit at
the dusty disused corners of
the protocol, enabling
there
to even ~be~ such a
thing as dusty corners in a protocol!, MUST die.
shrysr: mp_en_viaje: just
tried on a 'fresh' chrome installation.. still don't see it.
mp_en_viaje: shrysr, nfi why it doesn't work on your machine. indeed
the solution should be browser independent. maybe
they broke
the spec ?