431600+ entries in 0.279s
ascii_field: phf: for so long as it runs on a consumer pc, it will exhibit
the braindamage characteristic
to
the pc.
phf: ascii_field: oh i wan't
talking in
the abstract, i was
thinking in
terms of prescriptive specifically when it comes
to working on bitcoind
shinohai: Heh i need
to find
those dumb dogecoins i have somewhere and cash 'em out for btc, i could use it.
ascii_field: e.g., hardly anyone knows - or needs
to know - what chemical process precisely it was
that produced his cpu.
ascii_field: it is entirely possible
to make abstractions which do not, in any meaningful sense, leak.
ascii_field: it is very helpful, and should be introduced, so
that we know whom
to boil in oil.
ascii_field: phf: no. if it leaks, should find
the author and boil him in oil.
phf: ascii_field: is your argument
then, on a higher level, if abstraction leaks it should not be introduced?
peterl: first I would have
to make one
pete_dushenski: trinque
they do seem
to have
their place and
their purpose.
pete_dushenski: kakobrekla
that's buttrex
trading engine at 9,000 rpm for ya.
peterl: I should have emailed
the ISIS and cc'ed NSA?
trinque: above I spoke about being fond of my folks having
the drive
to "not suck"
kakobrekla: a whole 8 buttcoin volume on
that
thin, is
that all
they got?
shinohai: Be evil peterl and send emails
to ISIS recruiters.
trinque: pete_dushenski: it was in reference
to
the ISIS convo
peterl: no, just some derpy schmoe. I
thought about sending funny emails
to all his friends, but didn't.
assbot: Logged on 30-07-2015 20:52:13; peterl: so I go
to use
the computer at $LocalLibrary, sign into
their winblows system, pull up gmail, and lo and behold
the previous user is *still signed in*.
pete_dushenski: eth up a solid 20x over ipo price for
those (like saifedean) who
threw a couple bucks at it and are ready
to cash
the fuck out.
☟︎ peterl: hmm, yeah, I havn't had
time
to keep up with
that, did you use it? I suppose I could resurect it?
peterl: does it matter how much hashing pwer
they have if it is pointed at
the other side of a fork?
ascii_field: understand,
the
thing can work while being used only by mircea_popescu and five other similar fellas
to 'hawala' at each other.
ascii_field: trinque: say,
the cellular automata apparatus i described last year
trinque: ascii_field:
the hashing power monopoly scenario; say it forks and
there's nearly no hashing power on
the side of
therealbitcoind
peterl: so I go
to use
the computer at $LocalLibrary, sign into
their winblows system, pull up gmail, and lo and behold
the previous user is *still signed in*.
☟︎☟︎ trinque: I've
taken
the size of
the network as one of
the
things ensuring its continued existence.
shinohai is glas he discovered
therealbitcoin
ascii_field: there is
the gavins, and
there is
the actual people.
trinque: better
to get bitcoind right?
trinque: but in
that case I suppose "let em fork" ?
trinque: ascii_field: supposing
the network goes
the way of
the gavins
peterl: btw, I alrways read your name like it rhymes with drink, is
this right?
ascii_field: trinque: i'll repeat
the question - what is
the meaning of 'isn't
time' here ?
ascii_field: the reason
to remove machine gun from
the hands of a demented anal child is not necessarily
that you need
the
thing for anything.
trinque: I
took
that
to be one of
the reasons
to
take over development of bitcoind
trinque: or are we already in a position where
things like
the blocksize limit debate are moot
trinque: ascii_field:
tactically speaking, supposing
there just isn't
time for antifuse rom?
ascii_field: we know how. but market does not want penicillin. it wants
the normal cocktail of horseshit and opium
trinque: sure, just needs a business case
that works like anything
ascii_field: in
the sense
that 'cold fusion' or elixir of immortality is
trinque: but
then
to continue in
that vein, I do see how
trying endless mitigations is a death by a
thousand cuts.
trinque: and while you're fabbing hardware, might want
to keep
the integrity of
the
thing in
the meantime
trinque: chewing up a database on disk is a fine way
to run afoul of
the "I do not have
the correct blockchain problem"
the whole piece of software by its very purpose
tries
to avoid.
kakobrekla: <trinque> maybe
that's called for here < actually its called for in many other places, you still dont get it.
ascii_field: trinque: in precisely
the same way
that abdominal surgery increases required standard of hygiene
trinque: amazing how bitcoin drastically increases
the requirements on rigor and correctness
ascii_field: (though still have
to be careful because enemy can make holes in any place where you had not)
ascii_field: as will
the
tape deck and a piece of 'scotch'
ascii_field: a fifty-cent magnet will 'rewrite' happily,
these magical 'write once'
tapes.
ascii_field: was
told
that it is ordinary
tape. but with a magic hole in
the cartridge - like old floppy disk
ascii_field: this piqued my curiosity and i inquired
to
the vendor, how, precisely, does one make a write-once magnetic
tape ?!!
ascii_field: the docs mentioned
that one could buy 'write-once
tapes', for usg regulatory compliance
ascii_field: trinque: i was pointing out
that you need a relatively minor (from r&d standpoint) device,
that was ~once available~ and isn't
today.
ascii_field: but in virtually every case known, it was really a case of 'i won't go in
that hole, promise'
trinque: maybe
that's called for here
trinque: fair point, yet
that means no atomicity
til bitcoin has its very own hardware arch
ascii_field: there is an important difference between 'x will not happen because i promise not
to stick it in
that hole, really' and 'x cannot happen because physics'
phf: well block*.dat are essentially append only,
the idea can be emulated by having
transaction bits. you write a
t bit, you write rest of block, when done flip
t bit. on restart you walk backwards until
the first flipped bit and you file
truncate anything from
that point on
trinque turns
the death metal on again, fitting as it is
ascii_field: now go buy a silicon fab so
that antifuse rom gets produced again.
trinque: there,
that's an awesome idea.
ascii_field: blow
the last bit when 0...n represent valid block.
ascii_field: n+1 bits per block, with
the last one signifying 'finalized'
trinque: how, a fine
thing
to
think about
ascii_field: now we also need a
tcp crud pipe for every access
to
the blockchain ????!!
ascii_field: trinque: you speak as if
this
thing didn't eat enough ram and weren't slow enough
trinque: it's not an unsolvable problem
to just hack off
the frayed bit and begin again from
there
trinque: write ahead log is for
that
trinque: ascii_field: would not do
this
ascii_field: trinque: and go, unplug
the disk of, e.g., a postgres
trinque: I'm going
to restart it from
the beginning
ascii_field: for
the last week or so, after (briefly) fully synced
ascii_field: yes,
there is a ministry of usg
that occupies itself with finding nails for
the microscope
to pound in, badly
mircea_popescu: "it has problems, can't deliver on customer expectations, etc". you see
the seeds in
the amazon recent lol/
ascii_field: wake me up when
they can't afford
to mine spamblox any moar.
mircea_popescu: the 2016 usg line re bitcoin will be
that "never happened, not important, uninteresting"
mircea_popescu: 2 uni profs aren't a
threat
to
the fucking mice in
their own lab.
ascii_field: that 2m is ~just~ for
that particular sc4ml4b
mircea_popescu: but in fact it withered
to a coupla, and doled out
through
the university program.
mircea_popescu: last year it was, "tens of millions". merely not jumping
to hundred
this year = fail