339900+ entries in 0.216s

mod6: ;;later
tell funkenstein_
thanks. yeah,
that patch will be useful. will
try
to get it in right after
the release.
funkenstein_: mod6, keep up
the good work,
tis nice
to see some activity
funkenstein_: there was some
tree structure problem with original mailing list submission iirc
funkenstein_: it got hung up when i added another patch "chuck_checkpoints" with mistake.. now sits
there for eyeballs if anyone is interested
mod6: oh awesome, did it make it into
the ML?
mod6: funkenstein_: hey, did you write
that one?
funkenstein_: ooh cool "physically unclonable functions". is
that another way
to say reality?
assbot: Logged on 03-02-2016 02:13:21;
trinque: shinohai: I don't see anything in pybitcointools
to shove a privkey into a wallet.dat
mircea_popescu: ftr,
that's where
the now-famous first of many "calculate nth decimal of
transcendent without calculating
the others"
thing was published
danielpbarron: it's some account
that's fairly popular in
the
twatter circles of people who use
terms like opsec and infosec, pointing out
that
the proponents of larger blocks sound like
the guy who's running for president as a socialist
mircea_popescu: "wtf is with
these large buildings
they're all ugly in
the same way"
mircea_popescu: speaking of which, i was walking with a woman i walked with all over
the fucking world, and she spontaneoushly said
mircea_popescu: whereas
the correct solution is
to stick
to
the math. computers are fucking
tractors not farm designers.
mircea_popescu: trinque> also, I don't see sendrawtransaction in
trb's list o' commands... wat do? << cry all
the way home, we don't have it yet. backport it ? :D
mircea_popescu: idence of a polynomial method
to estimate a
transcendent" is really good enough. and it exhibits all
those important properties : such as, you can ~actually~ use infinite message, and you can also use any arbitrary padding you like, up
to infinity -
the hash function won't complain. and you can want it
to shit out any block size you want it
to shit out - also won't complain, but give EQUALLY MEANINGFUL results. whether
mircea_popescu: asciilifeform> i will prolly care. on
the
train, some
time soon. <<
the reason i give it is mostly didactic. it plainly shows what i mean re proper use of math and
treating your computer like a
tool
to do a job rather
than
treating your job as something
to be adjusted
to fit
the computer without having
to delve into complexities and subtleties of number
theory etc. something as commonplace as "use
the intervals of conf
phf: right, but doing just
topo won't
tell you
that
phf: well,
the idea is
that you want
to click on
the patch and see how
to press it. if i were
to click in polarbeard_* presumably i want
to press
the
tree
that includes old malleus?
phf: yeah, i'm not up
to date on logs
assbot: Logged on 03-02-2016 02:14:49;
trinque: also, I don't see sendrawtransaction in
trb's list o' commands... wat do?
phf: jurov: like
http://btcbase.org/patches/polarbeard_fix_instance_print , asciilifeform_malleus_mikehearnificarum asciilifeform-programmable-versionstring don't press because presumably conflict with programmable-versionstring malleus_mikehearnificarum in order. no idea why polarbeard_better_log_messages polarbeard_fix_instance_print don't press
though
trinque: anyone? given a privkey in hand, how
the hell do I get
trb
to send some coin? I do not want
to change addresses and nothing I find can chew on
this wallet
phf: jurov: i don't handle patch conflicts yet, until
there's some kommunitee resolution. and if
the answer is "remove
them from your patches" probably going
to add some kind of
tree walk in addition
to
topo. fwiw right now on
the site you can see patches
that wouldn't press cleanly in "pink"
kakobrekla: they also spin at
the lowest rpm of all
the high end fans i
tested
trinque: also, I don't see sendrawtransaction in
trb's list o' commands... wat do?
☟︎ trinque: shinohai: I don't see anything in pybitcointools
to shove a privkey into a wallet.dat
☟︎ mircea_popescu is still curious
to hear how people'd attack, if anyone cares.
mircea_popescu: fuck
the fucking computing-centring paradigm in crypotography
mircea_popescu: because we're specifically collecting hte noise of
the formula against
the
text and its mirror, rather
than pi itself.
mircea_popescu: anyway - being able
to calculate pi itself does not actually help here.
mircea_popescu: you
took a second
to answer after my 2nd line, minutes after
the first produced nothing!
timing attack on your brain!
mircea_popescu: it is apparently a lot easier
to follow math in words
than in symbols, EVEN FOR YOU
mircea_popescu: (basically -
they're
the classical (archimedan!) approximations of pi, for
the
text and reversed
text,
to an arbitrary precision. makes for an eminently
tunable hashfunction)
mircea_popescu: (V3 - V4) and finally d) return blocksize digits from
the key-th position in H.
mircea_popescu: asciilifeform if you feel like entertaining some crackpottery, suppose a hash function defined as follows : a) calculate PM ; pM ; P!M ; p!M where P and p are
the perimeters of polygons of K sides circumscribing and inscribed respectively in
the same circle and !M is
the bitwise negation of M ; b) calculate V1 = 2pMPM/(PM+pM) ; V2 = sqrt(pMPM) ; V3 = 2p!MP!M/(P!M+p!M) ; V4 = sqrt(p!MP!M) ; c) calculate H = (V1 - V2) *