log☇︎
302000+ entries in 0.189s
a111: Logged on 2016-05-11 21:38 mircea_popescu: world of tanks lol. trinque wtf the api can't be that broken ?!
mircea_popescu: as the romanian expression goes, prostu' parca nu-i destul daca nu e si fudul.
luke-jr: asciilifeform: things I'd like to see in it would be merged mining, additional inputs to the generation transaction, and maybe fix block withholding
mircea_popescu: also, please don't refer to tmsr as "a community". it is not "a community", it is your liege. ☟︎
luke-jr: asciilifeform: to show the industry that a hardfork and consensus is a possible thing
luke-jr: (unreasonable people demand we support 2 MB old transactions)
asciilifeform: well nobody can answer this mega-question until the concretes are given, neh ?
luke-jr: asciilifeform: not sure yet; ideally, only things that everyone thinks are acceptable (including people here)
luke-jr: is there any possibility of that, or is it just impossible?
luke-jr: so we're discussing whether we can get consensus for a hardfork with the community here
asciilifeform: at one point i considered buying one, but was not able to swing the access to the needed microscopy
asciilifeform: (and the 'macivory' product that sat in a 68k mac, was simply a card with the smbx cpu in it... no cables at all)
asciilifeform: the last true smbx box, xl1200, actually had standard scsi in it.
asciilifeform: dc power supply (a monster, iron box in the machine) was made by 3rd party and has labeled screw terminals
asciilifeform: (disk is on a st-506 cable but the pinout is public and you can buy the cable on, e.g., ebay)
asciilifeform: the internals are mostly on the backplane.
asciilifeform: i will note that there are no unusual cables (other than the long triax console cable) in my lispm
asciilifeform: (ti sold what was mostly a straight miniature clone of the original mit lispm)
phf: there are some funny comments about t.i. people on the margins
asciilifeform: it might be possible to recreate the last 2 from the schematics.
asciilifeform: the lispm itself, the 'fep' (which did disk/tape/etc. i/o, and was its own m68k machine) plus another m68k in the console
asciilifeform: (smbx had this, apparently, before ~anybody else, though today it is sop)
asciilifeform: ditto the synthesis system
asciilifeform: it existed almost entirely as src text
asciilifeform: phf: the vlsi falls squarely in the software side afaik
phf: but after shuffling "assembly" and "harness" papers for two days i know for a fact that some dedicated japanese man will be able to lovingly carve an smbx replica as his chosen otaku hobby
phf: i know that mallery owns the entire software side, no idea where the vlsi falls, but afaiu that's the reason why nobody's doing anything with the assets
asciilifeform: or rather, he admitted that they were sold, but did not say to whom, i discovered through other informants
asciilifeform: phf: last thing dks said to me was that the rights to the whole shebang were bought at auction by prof j mallery of mit/nsa.
deedbot: mircea_popescu updated rating of phf from 3 to 4 << Keeper of the logs ; and of Symbolics history.
mircea_popescu: $rate phf 4 Keeper of the logs ; and of Symbolics history.
phf: the main constraint is those same open maintenance contracts, but ultimately guy wants all that stuff preserved
deedbot: mircea_popescu rated phf 3 at 3668926147 << Teh desire has been expressed and heard!
phf: that's true, but those are not lost either
asciilifeform: (either that or the 'snap4' emulator source code) ☟︎
asciilifeform: and they are what is needed to replicate the thing on fpga.
asciilifeform: i'll be quite surprised if these are to be found in the papers david s releases to machine owners
asciilifeform: as smbx was among the first outfits to use synthesized logic
asciilifeform: rather than schematics
asciilifeform: most of the 'good stuff' was GAL listings
a111: Logged on 2016-05-12 14:19 phf: no, this needs further slow movement. i'm still hoping to get the whole set on another trip
asciilifeform: http://btcbase.org/log/2016-05-12#1466158 << there is one possible boojum that i know of: ☝︎
phf: and since asciilifeform is a lispm owner i don't see particularly reason why s.nsa shouldn't have access to it
phf: the intended purpose is to help lispm owners maintain systems on their own since the number of available parts is basically two stables in a barn and those are going to the usual suspects
phf: while the bulk is software, a dwindling part of it is repairs and console upkeep
mircea_popescu: what's the constraint ?
phf: like there are cable assemblies, that are handy for repairs or new construction, that i just don't have time to capture
phf: no, this needs further slow movement. i'm still hoping to get the whole set on another trip ☟︎
mircea_popescu: phf care to qntra ? :)
asciilifeform: how many schmidts you had to kill to get these!
phf: there's really too much documents for my lowly eos 5d, but i'm going for teh ic schematics and such. it's mostly like "here's how you machine part 560345 front left hinge"
shinohai: I managed to make my own gentoo livecd a few weeks ago ... I used the roll-your-own initramfs thing like jurov posted earlier
asciilifeform: it is in the logz!
a111: Logged on 2016-05-12 13:09 mircea_popescu: jurov> funny that I can't remember any concrete source how I learned that stuff. it somehow accreted <<< thinking about it i dun think a proper source exists, outside of carder forums or w/e equiv.
mircea_popescu: o hey, paymium now joins bitstamp on the list of wanna-be bitcoin exchanges that email spam. ☟︎
mircea_popescu: maybe good move for gabriel_laddel to actually post that thing on his blog once he makes it.
mircea_popescu: jurov> funny that I can't remember any concrete source how I learned that stuff. it somehow accreted <<< thinking about it i dun think a proper source exists, outside of carder forums or w/e equiv. ☟︎
punkman: jurov, dunno looks like it covers the whole thing
jurov: ;;later tell gabriel_laddel you'll definitely need this: https://wiki.gentoo.org/wiki/Custom_Initramfs
jurov: funny that I can't remember any concrete source how I learned that stuff. it somehow accreted
jurov: punkman these look like kernel innards, gabriel was asking more about userspace
punkman: ;;later tell gabriel_laddel https://0xax.gitbooks.io/linux-insides/content/Booting/
indoor_jellyfish: without such a document, the masamune replication will get done, but it'll take a while..
indoor_jellyfish: I don't really understand how the C linker or the rest of the linux "toolkit" works (eg, chroot) and a detailed explanation of how I would arrange a set of files + binaries, bundle them and generate a minimal bootable USB would go a long way.
indoor_jellyfish: which uses and unpacked archive of binaries from the author of that blog post
indoor_jellyfish: ie, it the current process doesn't package together the existing libraries / binaries /sources on disk into the bootable USB, and instead uses my re-write of "Roll your own ResueCD" (https://www.phenix.bnl.gov/~purschke/RescueCD/)
indoor_jellyfish: Does anyone know of a document that explains the linux boot process in detail? I've lisp code that builds /a/ ResuceCD (http://paste.lisp.org/display/315833) but not /the/ ResuceCD needed for Masamune.
asciilifeform: ;;later tell mircea_popescu http://dpaste.com/247510B.txt << don't die of laughter.
shinohai: http://log.bitcoin-assets.com/?date=11-05-2016 <<< congrats to asciilifeform for most lines posted yesterday LOL
mod6: where ``keep it'' invoves doing the hard, useful things that need doing.
shinohai: np, no good thing comes without hard work and trials
shinohai: Yup, I registered on May 25, 2015 ... how time flies. I thank you all for the knowledge I have gained in said time.
mod6: 'tis the difference between a republic that people want to be a part of and want to work, and an ad-hoc gaggle of people "doing stuff"
shinohai: I've been lurking here almost a year now, good things happen here that just do not happen elsewhere.
mod6: thanks for your input here, i think it takes a simple idea and scales it up nice.
mircea_popescu: it totally did not work what can i say.
mircea_popescu recalls the humble beginnings when we came up with the nutty idea of having a bot do voicing in chan. that was never going to work.
mod6: there really are so many things going on, and many more to come, we gotta be able to track this stuff.
shinohai: Absolutely one of the most useful tools in Bitcoinspace hands down
mircea_popescu: totally going that way huh shinohai
shinohai: heh mod6 this is too awesum :D
mircea_popescu: quite possibly, see what trinque says. running two bots does not necessarily mean one must write two bots. ☟︎
mod6: i think it's a fine idea, Sir.
mod6: now.. deedbot might have the infrastructure already in place to make this easier.
mircea_popescu: truth be told, even without permissioning it'd be pretty useful. that's more like a sort of you know, experimental wunderwaffen division, why not ask for things, see what happens.
mod6: i do like this idea though.
mircea_popescu: yeah. that's the iffiest part.
mod6: anyway, i think it's some thing i can work up to.
mod6: not sure how i'd do the encrypting part and keep it sec with minimal cost.
mircea_popescu: well alright then
mircea_popescu: all this make sense in your head ?
mircea_popescu: and i should be able to add tickets in the same sense, either public or wot or specified persons by encrypting it to bot's key.
mircea_popescu: whereas $bot deedbot me would result in a dump of ticketlist for deedbot encrypted to my key that's of level world and wot and me.
mircea_popescu: $tbot btcbase wot would result in a dump of the ticketlist for btcbase encrypted to my key that's of level world and level wot.
mod6: yeah, that part will be a huge pain.
mircea_popescu: the pgp permissioning being perhaps the trickiest part of it all. but ideally iut'd work like
mod6: as long as they're in the wot.
mod6: so, make 'tbot' for instance. then allow people to create tickets under whatever project they want.
mircea_popescu: you'd have to give him sql access to a log db.
mircea_popescu: rather than him having to make logger bots *m