596800+ entries in 0.367s
mircea_popescu: asciilifeform similarly
there's no substitute for salt pickles
jurov: are
theses sprats cryptographically signed?
kakobrekla: just saying
the standard is poorly defined.
kakobrekla: still
this is very arbitrary. can expect
to stuff
this in avg head and also on
the other hand some people can digest some funky shit.
ben_vulpes: but
tis but a guess and
that guess from me, and discounts should be applied heavily.
ben_vulpes: few
things are certain even
to
those capable of reasoning about
them. i must fumble in
the dark making guesses. my guess
though, is
that some parts of it work.
ben_vulpes: if it does what it says on
the
tin, i find it a vastly more palatable meal
than say a dollar
kakobrekla: the
test "if you can stomach" it is not
the best one imho
kakobrekla: 'fits in head' < meh, some folks fit 50k digits of pi in
ther head.
ben_vulpes: it's at least an example of
the desired process.
ben_vulpes: best
to do it correctly,
though. and binaries are not my concern - source is.
assbot: Logged on 27-08-2014 01:00:10; asciilifeform: 'pardon my cynical
twist, but what are you doing with
that 20,000×20,000 double-precision floating point matrix you say you need
to invert _today_? If you answer "nutt'n, I jus kinda wondered what it'd be like, you know", you should be very happy
that I am most likely more
than 3000 miles away from you, or I would come over and slap you hard.'
kakobrekla: never ? < ah i got it. wait 18 months for computing power
to double
ben_vulpes: watch
that
turn out
to be an aws maxi-sized VPS
kakobrekla: > A single machine acting as a full node
takes approximately 10 minutes
to verify and process a 32 MB block, meaning
that a 32 MB block size is near
the maximum one could expect
to handle with 1 machine acting as a full node < but how is a single machine going
to catch up when it falls behind ? never ?
cazalla: actually, ben_vulpes was
that even in response
to article or chat above
ben_vulpes: what are
the stats of
this "one machine"?
assbot: Conformal Release Bitcoin
Transaction Simulator | Qntra.net
ben_vulpes: i'd like
to have a
thing
that built a patch; booted
the resulting artifact on
testnet, mined some
TN coins, sent
them
to itself, etc
assbot: [RFC] Bitcoin QA : Continuous integration,
testing robot
ben_vulpes: surely
there's more rigor possible
than
this.
ben_vulpes: i build
the
thing, and
then boot it, and if getblockcount increments under my eye - it passes?
ben_vulpes: would like
to run
tests, write
tests, etc
ben_vulpes: i have zero familiarity with
the c ecosystem
ben_vulpes: the
test-bitcoin line in makefile.unix - is
that where i should look for running
tests?
jurov: i have
to
try it first what
the "signature on
the post" means if it si not S/MIME
jurov: Yes.
then
the patch above can be used: "A post will be distributed only if
the PGP signature on
the post is from one of
the list members."
jurov: and whoever want
to sign it, sends patch-author-id.sig
too
ben_vulpes: asciilifeform:
to digress, what's
the rationale behind keeping makefile.linux-mingw?
jurov: when multiple files are needed, can be
tarred
jurov: other people shall reply and send only
their signatures
jurov: no it's looking like one attachment
the
tarball, another attachment
the signature
ben_vulpes: <asciilifeform> jurov: also at some point we ought
to have people sign off on others' patches, once
they read << would a new
tarball with sig attached suffice?
jurov: ic,
the
tarball is easy be signed by others
jurov: you want
to send patches in above
tar.gz format?