84500+ entries in 0.588s

ben_vulpes:
i haven't seen gribble quit in some time.
ben_vulpes: yeah actually now that you mention it,
i'm abolishing users altogether.
ben_vulpes: today,
i am electing to not implement a logout button.
shinohai: Sorry BingoBoingo
I left out "would be required" after the " invoices each year.” quote
shinohai:
I think the whole place is inhabited now by human shannonizers that make mindless posts for 50 cents in satoshi a day.
shinohai:
I know but there aren't even lolz any more, nary an ingenious scam to be found.
ben_vulpes: in other satoshisms,
i found a bottle of contact lens solution that turned out to have high vitamin e oil for topical use in it
ben_vulpes: at least
i have blog-unique footnote refs now
scriba: Logged on 2016-09-19: [18:25:12] <ben_vulpes> did some late night back-of-the envelope on script length and miminum transaction size and
i don't recall it breaching u32
BingoBoingo: <mircea_popescu> "dad
i wanna get married" "honeybunch, you'll get old and your tits will sag and it'll suck. don't get married, it's a dead end" << LOL
phf:
i agree though, the numbers are unnecessary,
i'll have to borrow the whole sizeof concept :>
phf:
i think it aws en.bitcoin.it
phf:
i'm trying to remember what
i used as reference
phf:
i lisp pasted it a year ago, but
i'll dig it up if you're interested. it's hairy though
phf: ben_vulpes: ok, so that second paste is
i guess not "general purpose", you'll have to write a reader/writer for every structure that has compact size'd parts in it
ben_vulpes: (there's a fair amount of garbage in the thing
i didn't feel like cluttering the discusison with)
ben_vulpes: phf, yes, that's why
i pass a 'byte-count' keyword argument to the read-binary method for script bytes
phf: ben_vulpes:
i still think there's some misunderstanding. once you have a compact size reader, you don't automatically get "read N objects of compact size count"
ben_vulpes:
i have thought about this for at least ten seconds.
ben_vulpes: did some late night back-of-the envelope on script length and miminum transaction size and
i don't recall it breaching u32
ben_vulpes:
i don't even think you can have max compact size anything in trb.
ben_vulpes:
i only intended to write the compact size reader, not take it out of bitcoinland.
ben_vulpes: perhaps
i misunderstand you, but once
i have the type, sizeof, read-binary and write-binary implemented, then
i'll have a "general purpose 'binary type object of count `compact size`'"
phf: oh, then
i don't grok your question. "yes, it's exactly like any other hand-rolled variable length integer in c land"
ben_vulpes: at least from where
i'm sitting today.
ben_vulpes: once
i have a stake in the varint it will go precisely nowhere.
ben_vulpes: noty,
i would like to constrain the attack surface to satoshis retardation.
ben_vulpes: conveniently, the generic for read-binary accepts other keys, into which
i can pass a length for reading
ben_vulpes: phf:
i do believe that
i have to hold onto first-octet, if it's less than 253 it *is* the length.
ben_vulpes: phf:
i am open, nay, desperate for alternatives
phf: well, while asciilifeform's yak shaving,
i don't think this is correct way to handle the type
ben_vulpes:
i wasted an inordinate amount of time on various false starts in storing variable length fields.
ben_vulpes: easily fixed.
i'm more interested in correct use-of-binary-types
ben_vulpes: when
i need to handle reorgs,
i'll do so.
ben_vulpes: and
i believe that the thing hangs on to short chains
ben_vulpes:
i'm leaning on dumpblock to get them in chain-order
ben_vulpes: yeah
i have the vast majority of blocks serialized to disk and am trimming them apart.
ben_vulpes is looking for the log line where asciilifeform made a comment about how the block structure was trivially deduceable from the source, a few days ago after
i published the header serialization snippet
ben_vulpes:
i doubt it, as everything so far is little-endian, and only by convention reversed by early block explorers to show the zeros first or who the fuck knows
i've never found a sensible explanation for reversing block hashes (and only block hashes!)
☟︎ ben_vulpes: but the strange thing is that
i read the sequence number where
i expected to see the index
ben_vulpes: obvs my thinger is broken in that the hash is wrong, but amusingly
i get the sequence number as tx in index
mircea_popescu: "dad,
i want to put the cat's head on the dog's body, can
i borrow your hair trimmer ?" "that won't work, it's too small and it will get clogged in blood. here's the chainsaw."
mircea_popescu: (
i'm not even proposing it isn't, just wanna see what the showing would look like.)
trinque:
I will deny he "knows" masamune on the same grounds
mircea_popescu: trinque his objection is to the notion of "learn" and "knowledge" involved in that statement though, you might've noticed. and
i don't really see it's altogether weak.
trinque: doesn't bother me one bit, only demonstrated that "
I don't know how to network these two machines" and got thunked to... learn that.
mircea_popescu: "dad
i wanna get married" "honeybunch, you'll get old and your tits will sag and it'll suck. don't get married, it's a dead end"
mircea_popescu: but anyway, leaving the discussion aside for a moment to focus on the meta discussion : am
i the only one who's a little irked by the fact that kid wants to do x, gets list of instructions to not do x ? what is this, the nuclear family, elementary unit of the state ?
gabriel_laddel: asciilifeform: essentially
I would like all information available about all hardware vendors, neatly organized.
mircea_popescu: ehehehe. did
i mention very early trilema was discussing the eventual mysql chip ?
trinque: oh,
I told him "make the thing" and always do
phf: asciilifeform: that was an fyi. mcclim's x backend is clx,
i.e. fully networked. there's no actually ffi of any kind happening there
trinque: gabriel_laddel:
I called *your* thing an emacs, figuratively. It is "chinatown", place within a place.
trinque: but it will be a new emacs, and
I will regard it with the same resentment
trinque: ftr
I would not begrudge a new emacs
gabriel_laddel: phf: did you see the screenshot of the CLIM gui
I wrote around portage?
trinque:
I last built my musl recipe in jan, worked fine
trinque: and
I cannot be arsed to care anymore
trinque: in related lul,
I installed gentoo on this here laptop this weekend, and promptly removed it after x11 terminals couldn't be launched because /dev/pts is a magical fake filesystem with apparently myriad knobs and switches.
gabriel_laddel: when
I run into the friend with another masamune machine to we can now have a networked CLIM party