328700+ entries in 0.209s
phf: select
thing is still vaguely broken
though
ben_vulpes: hey phf
this btcbase
thing would rule with anchored line numbers on patches
ben_vulpes: aha i assumed, just
thought it funny how quickly
that number got bigger and by how much
phf: after application, run with -swank in addition
to all
the other shiva args, and connecting
to
the shiva port with slime-connect should work mircles
phf: big buffer ensures i can send big function over wire and
tinyscheme doesn't barf
ben_vulpes: heheheh strbuffsize goes from 256
to 2048
phf: yeah no reason why it wouldn't work from
there..
assbot: Logged on 28-02-2016 03:38:49; phf: 1) brew install cmake 2) patch < foo.patch 3) link_directories and include_directories in CMakeList.txt need
to point
to be modified
to point
to your boost/db4/openssl locations 4) mkdir foo; cd foo; cmake ..; make
phf: i don't imagine it matters at
the moment, can always shuffle
things
☟︎ ben_vulpes: phf, asciilifeform: where is an appropriate place for custom
trb scheme, and what mechanism should load it? just appending
to
the bottom of init.scm feels wrong.
ben_vulpes: phf: and in
the c function declarations?
ben_vulpes: asciilifeform: is it inane of me
to ask about hyphen/underscore conventions in shiva.cpp?
assbot: Logged on 28-02-2016 05:38:28; phf: asciilifeform: i
think he's looking for a way
to slice scheme into an arbitrary part of bitcoind, like CInv inv = scheme_apply('inv-process', cons(...));, unless i'm mistaken, but seems confirmed later in log
phf: asciilifeform: i
think he's looking for a way
to slice scheme into an arbitrary part of bitcoind, like CInv inv = scheme_apply('inv-process', cons(...));, unless i'm mistaken, but seems confirmed later in log
☟︎ assbot: Logged on 28-02-2016 02:14:54; ben_vulpes: asciilifeform: what's
the
thinking behind using IMPLEMENT_RANDOMIZE_STACK in shiva.cpp?
assbot: Logged on 28-02-2016 02:49:59; ben_vulpes: asciilifeform (phf, adlai, mod6_, mod6): okay
this is grand and i can see several rpc commands
trivially slain in
this vein, and others with application of work. but but but! would someone send me a map for running /scheme/ code from within satoshis abortion?
phf: oh i meant, what was
the entirely other reason?
assbot: Logged on 28-02-2016 03:15:29; BingoBoingo: From Google
Transgrish: "Due
to hardware accelerators supporting GOST 28147-89, processors "Baikal-T1" have certified compatibility with software and hardware encryption
tools. At present
the work as part of AWS "Meadowsweet
terminal" preparing several Russian means of information protection.
The company develops InfoTeKS for "Tavolgi" customized solution based on
the constructor protected ViPNet networ
assbot: Logged on 28-02-2016 04:08:36; mircea_popescu: phf> i
think ascii short
term plan is specifically rewrite of rpc, because it's an easily achievable low hanging fruit, which when done completely will let us get rid of json/
http << quite.
mircea_popescu: phf> i
think ascii short
term plan is specifically rewrite of rpc, because it's an easily achievable low hanging fruit, which when done completely will let us get rid of json/
http << quite.
☟︎ phf: i'm going
to have some kefir and decompress from
the day
ben_vulpes: i'm off
to waft
the child
through hipstergenic clouds of pot smoke
ben_vulpes: anyways, rather neet. looking forward
to shortening my loop up.
phf: well, after my eulora
travails i can
trivially build anything on mac os x with homebrew (thanks mp!), in
this case
there's not even a need
to fuck around since b-a approved versions of dependencies have brew formulas for
them
ben_vulpes: yeah i imagined
that running buildroot wouldn't make sense on a bsdalike
phf: 1) brew install cmake 2) patch < foo.patch 3) link_directories and include_directories in CMakeList.txt need
to point
to be modified
to point
to your boost/db4/openssl locations 4) mkdir foo; cd foo; cmake ..; make
☟︎ phf: but
then i also
tend
to overthink
things, for all i know
there's a perfectly
trivial solution
to all
things
phf: also
the whole
thing is not
thread safe...
ben_vulpes: okay i'll leave
that and
the slime work
to
the real artisans
phf: i
think ascii short
term plan is specifically rewrite of rpc, because it's an easily achievable low hanging fruit, which when done completely will let us get rid of json/
http phf: which requires a better understanding of how
ts's stack work, or perhaps figuring out how
to make multiple scheme instances share same oblist or something
phf: ben_vulpes: in order
to support any sort of rewrite of existing code, need
to figure out how
to have scheme runtime created at bitcoind start and
that runtime allowing for reentry
BingoBoingo: ration of VPN and PKI services.
The company CRYPTO-PRO adapts crypto CryptoPro SSP, are widely used, in particular, for
the authorization of electronic signatures in
the documents. Adaptation also
tested cryptographic USB-tokens Rutoken S and Rutoken electronic signature for secure
two-factor authentication in computer systems and storage of key information."
BingoBoingo: From Google
Transgrish: "Due
to hardware accelerators supporting GOST 28147-89, processors "Baikal-T1" have certified compatibility with software and hardware encryption
tools. At present
the work as part of AWS "Meadowsweet
terminal" preparing several Russian means of information protection.
The company develops InfoTeKS for "Tavolgi" customized solution based on
the constructor protected ViPNet network, designed for
the safe ope
☟︎ phf: ben_vulpes: so
the way
thing works right now, is
that when you connect a new instance of scheme runtime is created, which is
then fed init.scm and connected
to
the network stream fd. right now
the pattern
that we have is from inside a running instance you can call out into
trb and make it do
things
phf: ben_vulpes: depends on what you're
trying
to do
mircea_popescu: BingoBoingo i guess i'm just going
to add "this is good for fiat" comments from now on.
ben_vulpes: asciilifeform (phf, adlai, mod6_, mod6): okay
this is grand and i can see several rpc commands
trivially slain in
this vein, and others with application of work. but but but! would someone send me a map for running /scheme/ code from within satoshis abortion?
☟︎ ben_vulpes: i
thought we considered
that glass left on
the floor for barefoot burglars
ben_vulpes: asciilifeform: what's
the
thinking behind using IMPLEMENT_RANDOMIZE_STACK in shiva.cpp?
☟︎ mircea_popescu: lol. may be a long while, eulora
took
the crown for "most broken republican codebase" sometime
this year i
think
BingoBoingo: Maybe point him at
TRB documentation after he's done fixing Eulora?
mircea_popescu: guy's actually pretty good, found/fixed small cracks in
the wiki etc
BingoBoingo: mircea_popescu: Seriously
though it is far more refreshing
than YAJE, Yet Another Jackoffscript Evangelist
ben_vulpes: satoshi bless
the noobs, for
they bring lulz and drama.
phf: knuth actually made a version with working crosslinks and
table of contents and such, but
those cost as much as
the printed version and are "personalized". i
take it nobody bothered getting rid of watermark and publishing it, or i can't find a copy anyway
phf: i'd like
to read knuth chapters for a bit, but aocp warez is surprisingly awful.
torrents of pdf scans without
table of contents (!!!) and people in comments going "thanks for most useful books evaa!!!". does anybody actually
tried using
this shit?
phf: current
take is naive, uses a list of digits for presentation and a mul/shift/add approach
to multiplication. mostly a poc
ben_vulpes: ^^ nifty, asciilifeform!
thanks for bearing with my
thickness.
ben_vulpes: have fun in meatspace, i'll derp
through it.
ben_vulpes: should have communicated
to me
that 201 did not supercede 198
ben_vulpes: Apply
the pedigree bridge path, re-name
the directory
to shiva, and you get
ben_vulpes: was i not
to interpret "rebake using
the correct v-tron" as "supercedes previous missive"?
ben_vulpes: thank you for
the very explicit directions, asciilifeform .
ben_vulpes: so
to recap:
tinyscheme_genesis,
tinyscheme_snip, repl_fix, and
then flag_bug_fix?
assbot: Logged on 21-02-2016 00:37:21; phf: i can't figure out which patches are actually shiva patches.
there's "(EXPERIMENTAL) Introducing: Shiva." and
then sometime after
there's "Tinyscheme Genesis, Cleanup, and Fixes, CORRECTED; -and- Shiva Pedigree Bridge."
ben_vulpes: so i should be able
to leave
the
tinyscheme dir as
tinyscheme? or am i screwing up royally in
that my patch applications don't result in a shiva dir?
assbot: Logged on 27-02-2016 20:40:43; ben_vulpes:
tinyscheme still needs renaming
to shiva, correct?
ben_vulpes: tinyscheme still needs renaming
to shiva, correct?
☟︎ ben_vulpes: asciilifeform: d'you have a minute
to answer shiva questions?