tmsr - Log 2018-03-13

mod6: Lords and Ladies of the Republic, here's my "blog" post on the UTF-8 character found in genesis.vpatch, please review:

diana_coman: nice work there mod6 ; the new V functionality seems to me potentially useful

diana_coman: fwiw I grabbed the .c check script and ran it for peace of mind on eucrypt's patches with success

trinque: since we're discussing cuntoo in pizarro, and it's more generally relevant, I'm moving the thread here.

trinque: diana_coman tried to build a cuntoo per my recipe and was bitten by the upstream musl-overlay gentoo repository having shifted enough to break the build.

trinque: I did not yet V genesis a portage overlay (which would eventually become the *only* portage tree, after republican ebuilds are made to replace items needed from the gentoo official portage) pending a resolution to the thread on how to handle v tree fragmentation.

trinque: I believe it's more or less established by this point that the solution is to have a history file that's edited by patchers if they care that their patch isn't abandoned. ☟︎

mircea_popescu: spyked "the original script doesn't always pass childNodes[0] as a parameter" << whoa, where is this ?

mircea_popescu: might be obscure bug i've been chasing ever since i put it in

mircea_popescu: http://btcbase.org/log/2018-03-13#1787748 << just about, yes. i wanted a model file so we have something to play with and the original concept was to have phf include it in his v tree of his v rewrite because it seemed the first item that's coming out at the time from l1 hands ; but if it's holding you back re tmsr-portage, go ahead and make the sample yourself and we'll see how it works. ☝︎☟︎

a111: Logged on 2018-03-13 12:59 trinque: I believe it's more or less established by this point that the solution is to have a history file that's edited by patchers if they care that their patch isn't abandoned.

jhvh1: ben_vulpes: Bitstamp BTCUSD last: 9142.99, vol: 19539.12057095 | Bitfinex BTCUSD last: 9124.9, vol: 72305.45984006 | Kraken BTCUSD last: 9127.7, vol: 13051.3224227 | Volume-weighted last average: 9128.61803267

spyked: mircea_popescu: in scrollToHash and the onmouseup callback there's this call: recur(content.childNodes[content.childNodes[0].nodeType==3 ? 1 : 0]); <-- for some reason I couldn't get this to work, so I changed it to: recur(content); which should walk through all the children in the DOM subtree, not just childNodes[0] or childNodes[1].

spyked should really reread this script more often, it doesn't seem to stick in head.

mircea_popescu: pretty humongous penalty on large articles, try one of my mb ones with that on

spyked: yeah. but for some reason I couldn't figure why it doesn't activate the #selection thing at all with this optimization. must be that the page layout is different. there was a thing that trilema did, hm... /me rereads http://trilema.com/2015/that-spiffy-selection-thing/ ☟︎

asciilifeform: meanwhile in log-archaeology, http://btcbase.org/log/2014-09-19#836087 >> subj www still alive! but no one ever saw working device; according to authors (last post 7 july '17..) they never found an anti-gsmlossiness algo that worked worth a shit. ☝︎

a111: Logged on 2014-09-19 18:34 asciilifeform: http://www.jackpair.com << we love mitm! and prng; and luser-phriendliness...

asciilifeform: ( i'd even dare to rule out the 'shown the instruments' hypothesis, given as their crypto per se was a joke from day1. but asciilifeform was interested in re the voice codec. turns out -- open problem, to this day. )

spyked: http://btcbase.org/log/2018-03-13#1787759 <-- a-ha, mystery solved! Trilema has a <div class="post"> child to <span id="shash-...">, so that portion of the script selects it when the child is not a text node (the nodeType==3 bit). thetarpit DOM tree is flatter and doesn't wrap the content in this additional div. NB, will keep it mind should performance ever prove to be an issue. ☝︎☟︎

a111: Logged on 2018-03-13 20:08 spyked: yeah. but for some reason I couldn't figure why it doesn't activate the #selection thing at all with this optimization. must be that the page layout is different. there was a thing that trilema did, hm... /me rereads http://trilema.com/2015/that-spiffy-selection-thing/

spyked: now, the question is whether all wp themes use the <div class="post"> bit to wrap the title and the content. when modifying the theme, one should make sure the [content goes here] part in http://trilema.com/2015/that-spiffy-selection-thing/#selection-112.0-120.3 has this.

mircea_popescu: spyked nice find. this'd not be in mp-wp by default, as it's eminently a http://btcbase.org/log/2018-03-01#1786583 ☝︎

a111: Logged on 2018-03-01 06:14 phf: i think there might still be a bunch of cool stuff like that hidden in your themes, that's not in wp-mp