496700+ entries in 0.928s
ascii_field: punkman: i'm partial
to older 'tyan' boards
punkman: guess I'll have
to look into
that
ascii_field: pathetic buggers, doing
the one and only
thing
they are good at - 'spinning
the controversy'
ascii_field: oh noez
the user is not caged properly!
there are a few loose bars!
ascii_field: in every single case, it was a 'oh noez
this is accidentally auditable'
ascii_field: 'oh noez,
the chip is auditable when we don't want it
to be! boobytrap!'
ascii_field: turned out, it was possible
to read back
the bitstream from a 'locked' unit
ascii_field: at one
time
there was much crowing re: a 'xilinx fpga backdoor'
punkman: AMD's "management engine" equivalent is also bad, isn't it
though
ascii_field: 'oh noez non-crippled hardware, someone other
than usg could modify it'
nubbins`: man, reddit's
taking a page from
the book of alf
today o.O
ascii_field: to continue with
the line of
thought, as soon as we so much as frag less
than gavin's
turd, someone - anyone - could send us off on a fork of less-retardation.
mircea_popescu: as
teh expression goes, "relax, you have plenty of
time.
tomorrow - you die."
ascii_field: we don't even know for a fact what it is
the miners use..
ascii_field: and until
then, what? we are required
to leak at
the same rate as which extant bitcoind?
mircea_popescu: like i've been waiting, on many
things, for many years.
ascii_field has no idea how, or even whether,
this is handled.
mircea_popescu: we explain
the problem, publish
the measuring
tools, let people declare
themselves retarded.
ascii_field: at what point do 'we' get
to proclaim
that folks using
the buggy version are retarded ?
mircea_popescu: not among which,
the opnion of reddit,
the headers of miners etc.
mircea_popescu: nevertheless, before any sort of change, like say a block size increase,
this will have
to be measured
ascii_field: didn't say
that it was (except
that it - was, i measured)
mircea_popescu: we don't care atm, because we know experimentally
the system as deployed is stable.
ascii_field: at any rate,
this gedankenexperiment is an interesting one - where does 'bug for bug compatibility' legitimately stop? are we obligated
to crash for 1GB of uncoalesceable crud, or 2GB? 4? 16?
ascii_field: 'isn't a jewel' << mega-understatement of
the century
mircea_popescu: and
the bitcoind allocation scheme isn't a jewel or anything.
jurov: bdb is much more coplicated and hard
to debug api
than malloc/free
mircea_popescu: which obviously differ from your coder heuristics. but differ
to our benefit.
mircea_popescu: in general, going by
the "never one single bug in kitchen, and noting
that bdb locks are a resource of
the kind
that pointers are, just one easier
to exhaust, i propose
this as likely, on
the basis of my business heuristics.
mircea_popescu: but do you mathematically see
the proof where it never would ?
jurov: you just flush
the disk cache by your misallocations and
then
take longer
to verify
the block
jurov: i don't see
the issue why
that would lead
to fork per se.
mircea_popescu: that gavin [pretends like he] doesn't know such is exactly why
the verbiage as
to
the retarded boy in one of my articles debunking
the nonsense.
mircea_popescu: currently
the 1mb limit is blessfully keeping
THIS (among its many sisters) under
the water.
mircea_popescu: note
that
this is one of
the majorest issues lurking in
the "larger blocks"
☟︎ ascii_field: that
the fragging issue itself results in ludicrously overpowered boxes being put
to use
ascii_field: mircea_popescu:
this in fact happens 'in
the wild.'
the only reason it does not lead
to forks where folks with, e.g., 1GB of ram wheel off into a parallel universe from folks with 2GB, and 4GB, etc. is,
BingoBoingo: <ben_vulpes> who's on
the qntra /reddit as usg mouthpiece/ beat? <<
There is a
trilema post
tracking
this phenomenon, but if you want
to elevate it
to a sustained operation go for it.
mircea_popescu: by
the
time you're entirely exhausted, i broadcast some more
txn and mine a block with
them.
mircea_popescu: i also broadcast 50k 150 byte
txn.
these go in your pile, and on fresh memory.
BingoBoingo: <mircea_popescu> dude i swear
there was a different coinsetter
that was
trying
to be a sort of coindeks << I constantly run into new ventures
that imagine
they are qntra competitors
mircea_popescu: so i broadcast 50k 140 byte
txn. you allocate
these,
they fail, you deallocate
them. before you had
time
to go
through
the lot however,
ascii_field: it was an epic lameness and a number of folks ought
to have felt
the stake
mircea_popescu: in fact,
this has happened (not due
to
the heap issue,
true)
ascii_field: if such a
thing could,
then bitcoin is buggy and
the sooner it is detonated,
the better
ascii_field: mircea_popescu: a proper 1m block should never be able
to 'make everyone crash'
mircea_popescu: ascii_field it will construct and mine a block
that makes everyone else crash, conceivably.
mircea_popescu: kinda why idiots (and by
that i mean satoshi) shouldn't be allowed
to code in
the first place. but hey, we believe in
the power of belief...
ascii_field: mircea_popescu: if allocator leads
to fork, it is wrong
mircea_popescu: this is one of
those places where bug
to bug compatibility rears it's ugly butt.
mircea_popescu: yes but it's worse
than
that : if you have an elegant alocator and
the people do not, your chain will fork and
theirs will not.
ascii_field: typically
this is handled with custom 'multi-generational' allocator
mircea_popescu: no, i just mean, with bitcoin is
to some degree unavoidalbe, because
txn.
mircea_popescu: ascii_field part of
the problem is
that you're stuck mushing
together items
that can arbitrarily be anything between 100 bytes and whatever, 250kb. and
there's a lot of
them. no way
to allocate but dynamically, willy-nilly keep getting
them allocated and deallocated and again and again.
gribble: Bitfinex BTCUSD
ticker | Best bid: 246.0, Best ask: 246.01, Bid-ask spread: 0.01000, Last
trade: 246.01, 24 hour volume: 38386.95711616, 24 hour low: 242.72, 24 hour high: 256.4, 24 hour vwap: None
mircea_popescu: it's been danced around with all sorts of patches and whatnot, but multiple ddos avenues related
to fragmentation.
mircea_popescu: I believe in markets and
trading
to increase
the wealth of
the world."
mircea_popescu: i dunno why
they were filed under "just another subreddit" but w/e.
assbot: Logged on 30-04-2013 01:55:22; mjr___: kakobrekla: "The skateboard ride
to Saks
today was a little rough, but
the skateboard back was great!" I am not joking
that is
the latest status update from coinsetter CEO...he's a nice guy
ben_vulpes: they may have some slave in
the
third world cranking aggregation on
their blog, perhaps
that's what's got you spun.
ben_vulpes: integrity check
to mircea_popescu's symbol
table please
mircea_popescu: dude i swear
there was a different coinsetter
that was
trying
to be a sort of coindeks
mircea_popescu: oh, i see, because
they have no btc, all
they have is "mindshare", and in respect
to
that pseudo-capital coinsetter is better capitalised
than cavirtex ?
mircea_popescu: wait, in
this lalaland of imaginary imaginations
the newspapers acquire
the failed banks ?
fluffypony: so I
think CoinBase's SendGrid account has been compromised?
☟︎ fluffypony: "Want
to become a professional investor? Our first short-term investment program starts
today - GET 150% FOR A 10-DAY DEPOSIT."
ben_vulpes: who's on
the qntra /reddit as usg mouthpiece/ beat?
lobbes: I
think you are correct. I just did a quick
test; no [removed] flag. Just disappears from
the page. Going
to
the url just displays
the 'by [deleted]' flag
lobbes: I believe a user can remove his own,
though I'm not sure if
that results in
the [removed] label
ascii_field: reddit users: does it have
to be a moderator who deletes a piece,
to result in
the '[removed]' label?
lobbes: "DISRUPT - Divide community consensus and steer
towards Operational and COMMAND objectives by means of standard counter-actor and sabotage procedures."
assbot: TotesMessenger comments on
There is a
targeted attack on Bitcoin occurring right now, coordinated by national agencies. I know
this because I am an insider with prior involvement in a key operation. ... (
http://bit.ly/1PknucE )
nubbins`: i hope WC orders me a good
type of pizza
nubbins`: blockchain analysis says
this didn't happen, but w/e