log☇︎
86800+ entries in 0.641s
ben_vulpes: not a bad idea
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: menial wwwtronix are just a matter of time
ben_vulpes: i received a /spam/ comment.
phf: from the "wat" department https://www.thesun.co.uk/news/1799205/sex-change-soldier-is-britains-first-female-to-fight-on-front-line-after-being-born-a-boy/
asciilifeform: http://cascadianhacker.com/07_v-tronics-101-a-gentle-introduction-to-the-most-serene-republic-of-bitcoins-cryptographically-backed-version-control-system
asciilifeform: it was closest thing there was to a 'textbook of v'
scriba: Logged on 2016-09-19: [18:13:11] <phf> the type is called compact size (in bitcoin src parlance), it is simply an number. the reader reads a byte, decides what to do, ultimately returns ~the number~
mircea_popescu: much like a "press", it's a personal take on the lightcone as-it-is.
mircea_popescu: in a sense getting rid of historical "orphans" is very much community-trying-to-insure against the nature of the blockchain.
mircea_popescu: http://log.mkj.lt/trilema/20160919/#461 << technically you don't know it will be orphaned ever, because "being orphan" is not a quality of a block/chain. if tomorrow we decide to extend an "orphan" from 2014 and in the process strand extant bitcoin, we ~can~.
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: well, you write your heathen-octet-stream wrapper around your default sb-internal::binary-trit-tryte-input, so that read-byte on a stream gives you the right things
asciilifeform mutters 'what if i'm on a box with 7-trit trytes'...
phf: i lisp pasted it a year ago, but i'll dig it up if you're interested. it's hairy though
phf: it's a worthwhile attempt anyway, because implementing binary types from scratch with necessary parts to support bitcoin is not that hard. mine is 129 lines
ben_vulpes: http://wotpaste.cascadianhacker.com/pastes/d6kbl/?raw=true << i have to run for a bit
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"
asciilifeform: it's a very sad pattern though. promisetronic. in that you have a format ~in your head~ and then write 'reader' and 'writer' and there is no machine-assured isomorphism between the one and the other, and definitely not with the format.
phf: no, but it's a common pattern
phf: ooh, you don't write c, yes, it's a common pattern
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: ben_vulpes: well, what you're calling "varint" is called compact size in bitcoin source, and it's used exclusively as a size prefix for variable length lists <compact size><item 1><item 2><item 3>
ben_vulpes: once i have a stake in the varint it will go precisely nowhere.
phf: well, step two after writing compact size reader/writer is to figure out how to make a general purpose "binary-type object of count `compact size`"
ben_vulpes: conveniently, the generic for read-binary accepts other keys, into which i can pass a length for reading
phf: so it's up to reader to decide if it should return first octet as ~the number~ or read first octet and read a bunch of stuff after and return that as ~the number~
phf: the type is called compact size (in bitcoin src parlance), it is simply an number. the reader reads a byte, decides what to do, ultimately returns ~the number~
asciilifeform: phf: i dunno that binary-types offers a clean way of handling this type
phf: ben_vulpes: you don't have to store first-octet since, it's a property of variable-integer (also if you change variable-integer, you'll have to make sure to correspondingly update first-octet)
ben_vulpes: fell back to a setf from read-binary.
ben_vulpes: 'tis a tree
asciilifeform: ben_vulpes: it helps to remember that the blockchain is ~not~ in actuality a simple linear sequence
asciilifeform: ben_vulpes: these already lived in a consecutive pile.
asciilifeform: you will never have to go to the town market to buy a new rhinoceros or new bulldog, you can cut the head of this one as many times as it takes.
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
asciilifeform: https://github.com/lbotsch/wireshark-bitcoin << not a wholly bad guide to the thing
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: however many f's you need for a u256
asciilifeform: ( it must've been a real downer for these folks, who turned into boring, snoring car mechanics, dentists, etc. 'hey, remember when we used to saw dude apart and stitch his head onto his arse? ' 'shuddup, pass the oil pan' )
mircea_popescu: gotta be a lot more nurturing in the way of rope supplies, by your own theory ?
asciilifeform: a dude who believes that he is genuinely solving some actual problem by bolting a gui onto 'portage', is engaging in willful idiocy
mircea_popescu: trinque yah, but now it's in a much better formulation. at least to my taste.
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"
asciilifeform: it isn't as if we tied him to a pole to keep him from going into it.
asciilifeform: mircea_popescu: what is to be gained from ~not telling~ the kid that the dead end is 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 ?
mircea_popescu: really, making a lisp that works for serious applications in this sense is outside his pay grade
asciilifeform: (as in, with human, in a chair, looking at a screen)
asciilifeform: there ~isn't a pro computing market.
asciilifeform: trinque: there is a pro number crunching market.
trinque: if he even gets an inkling that there's a professional computing market that'll be useful information.
trinque: iirc another such character did pretty well bolting shiny things to a BSD
mircea_popescu: myeah. afaik no statically linked mysql was yet made, which is kinda a first step
mircea_popescu: phf im pretty sure that if db-on-a-chip happens, it'll be mysql first. much to the chagrin of sane people.
asciilifeform: phf: this is actually a mature market in, e.g., gene sequence biz
phf: a friend of mine bought a house in san francisco last year, because he's working on "mysql chip", really an fpga that does a bunch of mysql specific optimizations. (mostly query compilation)
trinque isn't mad at the idea of a hardware db
gabriel_laddel: even if this is just a list of .pdf files I can parse
asciilifeform: gabriel_laddel: it is a very very short list.
asciilifeform: mircea_popescu: iirc the thread was about a pedestrian list of 'hardware we like'
gabriel_laddel: asciilifeform: you remember my asking after a hardware database?
mircea_popescu: asciilifeform YOU don't. because one's ideology, ie, theoretical insight, is a shield for that one.
mircea_popescu: asciilifeform a) all concepts are insane ; b) the only way this is ever usefully established is through prototyping.
mircea_popescu: trinque having a sane prototype is not a bad idea ; whether you can or you can't make it.
trinque: one should have a plan to make hardware if he intends to do anything in computing going forward.
trinque: this isn't a reason not to do it, but it describes limitations that are unavoidable
trinque: gabriel_laddel: I called *your* thing an emacs, figuratively. It is "chinatown", place within a place.
mircea_popescu: yes. the "can't abstract broken software with other software" is a restatement of godel, "There may not exist specific algorithm A for any formal system F that includes statements of certain elementary mathematical truth as well as its own consistency so that A will create subsystem F' which is consistent and an homology of F"
asciilifeform: 'i'm not a transgendered goat, i dress up as one voluntarily'
phf: asciilifeform: fwiw there isn't actual athena in mcclim, it's a skin designed to look that way
phf: trinque: there's a handful of adequate contenders, problem with emacs is that everyone wants all those hacky, emacs-version-specific .el files that actually do stuff
asciilifeform: programmers have a mindboggling lack of grasp of basic ecology even compared to illiterate afghani goat herders.
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: asciilifeform: look, we can and do hack around and get things done in broken software everyday. If an environment exists in which one can WITH A SINGLE PROCEDURE CALL write the "world" out to a USB/CD/whatever it should be a plenty stable platform for whatever computations are required for new hardware.
asciilifeform: gabriel_laddel: didja sell enough to buy a postbox yet ?
gabriel_laddel: asciilifeform: the purpose of masamune is to provide funds for the republic (by selling them) and a development platform from which to build new hardware.
scriba: Logged on 2016-09-19: [16:25:37] <gabriel_laddel> It is a revolt against G-d and all that is good and true that there does not exist a platform, even on UNIX that one can buy for lisp development.
asciilifeform: gabriel_laddel: if you think such a thing is remotely a good idea, and that the crud will not irreparably spill out from under the 'skin', i got a bridge to sell ya.
asciilifeform: trinque: if i had a working mussolinic gentoo, i'd never have cooked up 'rotor'
asciilifeform: thus far, every time i sit down and make a gentoo box, more or less ~yearly since '06 or so, it ... works
trinque: openbsd has a proper static file dev
asciilifeform: trinque: pts isn't a gentoo-specific ball of shit
trinque can't wait until masamune realizes that google fucked gentoo into a million pieces
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: mircea_popescu: that is correct. Hence enforcing a SINGLE hardware platform from which to generalize.
gabriel_laddel: when I run into the friend with another masamune machine to we can now have a networked CLIM party
asciilifeform: gabriel_laddel: if you get tired of having to toggle the nic to autocrossover, get out a pair of scissors and make an actual crossover snake
mircea_popescu: gabriel_laddel ironically, turns out trinque did have a point eh.
gabriel_laddel: Thank you. A tsmr~ ghetto with its own CLIM-web internet is now possible.
mircea_popescu: i'm sure a lot can be done to bleed the computer socialism from inside.
scriba: Logged on 2016-09-19: [16:18:08] <gabriel_laddel> just a minute, have rebooted both machines.
asciilifeform: mircea_popescu: i maintain a delousing spray strictly.
gabriel_laddel: while we're here - does anyone know of a script that downloads the whole of the gentoo documentation?
phf: it is clearly documented, in a man page
gabriel_laddel: locally, in a manual.