log☇︎
476 entries in 0.642s
mircea_popescu: and no, obama didn't do this. the problem was already manifest two centuries ago, in the sense that it's entirely possible beethoven went deaf (a major early symptom of saturnism) due to drinking wines sweetened with the stuff. which was already illegal back then, but then he was a miser.
mod6: there should be a Manifest.sha512 in tehre too.
mircea_popescu: rather than put up with their manifest insufficiency and social inferiority at home, they find it preferable to go be "equal" to "everyone" in dumblandia.
phf: asciilifeform: that's silly. it took you many years to arrive to the point where you even understand what "stop overthinking" is, or how to manifest it in code and still provide the solution. i problem is in too much thinking, then you could get a complete idiot to write ffa.
trinque: unbelievable rot flows out of this place "lakeway church" nearby, literally "give us your money and god will... like... manifest you some more"
asciilifeform: it would instead manifest as one or more chains of tx that a trb node -- a particular one, that saw the particular magic orphan -- mysteriously does not want to spend the outputs of.
asciilifeform: orrectly" popup, which can be elminated with some manifest-fu.'
mircea_popescu: (ftr, these in order are the two major soaks i am aware of ; whether they manifest for you right here or not)
mircea_popescu: all coins, in the sense of agglomerations of satoshi, exist as descendents of an original block subsidy, and in that sense ARE coinbases ; much like electrons or photons are wave functions. they manifest verifiably in certain points, as "unspent transaction outputs" ; muych like waveform collapses. they interact with matter, in certain ways,this is called a transaction.
asciilifeform: 'Cisco's WebEx extension (jlhmfgmfgeifomenelglieieghnjghma) has ~20M active users, and is part of Cisco's popular web conferencing software. The extension works on any URL that contains the magic pattern "cwcsf-nativemsg-iframe-43c85c0d-d633-af5e-c056-32dc7efc570b.html", which can be extracted from the extensions manifest. Note that the pattern can occur in an iframe, so there is not necessarily any user-visible indication of what is
mircea_popescu: the "us vs them" thing is very evidently manifest. it also happened to work for them a lot better back in 2000, when they owned the de facto currency.
asciilifeform: mircea_popescu: the current setup (with the patch.nickname.sig) is an artifact of the idiocy of pgp, where one cannot take the signature and extract a hash from it with which you can look up the patch from a manifest of patch hashes in O(NlogN)
asciilifeform: note that only 1 of the items in the manifest (the first) is vpatch
asciilifeform: hey the schem hashes are in 1) the v genesis + 2) the signed manifest
asciilifeform: !!deed http://nosuchlabs.com/fg/manifest.txt
asciilifeform: but since nobody seems to have any better idea, i'ma deedbot a manifest.
mircea_popescu: poor BingoBoingo is oppressed by a manifest news drought.
asciilifeform: 'A chip can have 2 processors with 8-byte buses each, going to a DRAM giving you 16 bytes per cycle, through a shared 8-byte-per-cycle bottleneck. This interconnect is the handiwork of some time-starved dude on the chip maker's team, armed with an interconnect-generating tool. Even such an idiotic issue will manifest on some benchmarks but not others, and might not get caught at design time. And if you think that is stupid, I've hear
mircea_popescu: the logic is judicious from the pov of socialist empire : the marginal utility of stem is actually nil, because whatever rocket they invent the russkis will steal and the chinese will make cheaper anyway ; whereas the marginal utility of http://btcbase.org/log/2016-11-05#1563151 is manifest : however many are needed to brew a head of fucktoys required by bill de blasio to forget the monkey at home. ☝︎
asciilifeform: (granted we dun have the actual facts, beyond a landing manifest from buenos aires in '45 where germans unloaded ~something massive~ from a 6-engined monster junkers. but the 'red mercury', 'alien corpses', etc. are what the disinfo folk spray onto anything they dun want in the literature.)
a111: Logged on 2016-09-24 04:33 trinque: the presence of a bin folder manifest and makefile is intended to provide a place to check the sha512 hash of the built product upon such time as we can beat gcc into producing the exact same binary for a given release.
trinque: the presence of a bin folder manifest and makefile is intended to provide a place to check the sha512 hash of the built product upon such time as we can beat gcc into producing the exact same binary for a given release. ☟︎
mircea_popescu: dude... who the fuck wants as much as a farthing's worth of pest control work from someone who regards their mentally deranged state as manifest in their subjective confusion re their sex as an integral part of the process ?
mod6: So, a clearsigned manifest that holds the URL and the SHA512 that I attest is correct then, deedbotted?
mod6: So was thinking a clearsigned manifest could do the trick there.
mod6: I could create a clearsigned manifest that could reside on deedbot.org that could be also pulled down, verified and used.
mircea_popescu: the moment the bs with "everyone" and "anyone" and so on starts, the game's lost, all that's to be still established is the exact manner in which the fuck-up will manifest. but the fuck-up is already baked in at that early point.
asciilifeform: see MANIFEST.TXT.
phf: i'm not sure i understand where compromise is. i'm comfortable working with big ball of mud. i see a vpatch as a transition of state of mud to a new state of mud and vpatch is an exhaustive description of what that state transition means. it's signed by asciilifeform which is all the pedigree i need. vpatch itself can come with out of band comment "might be buggy" or "ready for war deployment". there are known problems with that approach that manifest at scale (like for example multiple slightly conflicting version of "utilities" or "math functions" that get copied back and forth, finding bug in one means that the other might remain unpatched, etc.)
mod6: <+asciilifeform> SHA1 manifest, of course. << lol. i do some shitshoveling at a place that still uses md5 and sha1 at all times.
asciilifeform: SHA1 manifest, of course.
asciilifeform: INSTEAD, it has a manifest list and a loader...
phf: but if the question is about other people, then there's a trust slice that is manifest on the system. the kind of person who trusts his os x, should also trust the password generator on it. kind of person who downloads random online apps by some criteria, would be able to apply same criteria to selecting a password generator/manager
phf: that decision had causes that in turn took several months to form and manifest as these things usually go
mircea_popescu: 1 has the manifest disadvantage that it is an exact replay of the bitbet drama. it may be argued that it is "clean" and "elegant" and "all i wanted was to protect you, son", which is so much idiotic patriarchical nonsense it makes my skin crawl - and thus let's extend kakobrekla in public the same sympathies extended in private ;
phf: as manifest in every "my first crypto", this is so convoluted i can't grok it, surely nobody else can
ascii_rear: what would be handy is if the thing could spit out a manifest of all the crap it expects to find
mod6: ben_vulpes: the buildroot hash is in deps/Manifest.sha512
ben_vulpes: ;;later tell trinque i may be exceptionally retarded today, but is there a reason why shit/Manifest.sha256 doesn't contain a hash for buildroot?
mod6: awe crap, sorry my manifest file is in the list.
mod6: you know, one thing that I did to ensure that my pressing of the tree was happening correctly was to press out a tree, then do a full `find . -xtype f -print0 | xargs -0 sha512sum > manifest` to see what the final hash of the source file was, then compare it to what we had before -- what we were patching by hand.
mircea_popescu: if she had to repay all her debts (and forget the financial angle - if she had to do all the work to count as educated at the level of education she perceives herself to occupy, manifest inability to think or even spell be damned) she'd simply figure "life is not worht living" and lie in a ditch to die.
mod6: the main problem here is going to be tagging the MANIFEST file, like i did in the 'test-v054-REL-wLayout.vpatch' -- because it'll be a clearsigned file. no way to 'tag' a file like that.
assbot: Logged on 22-12-2015 22:43:02; mod6: so i think jurov has a good question; if we don't drop the turdballs into V, which we're not, and the MANIFEST is the only thing in the 'shit' directory that is pressed out by 'V', where do the tarballs come from?
mod6: so i think jurov has a good question; if we don't drop the turdballs into V, which we're not, and the MANIFEST is the only thing in the 'shit' directory that is pressed out by 'V', where do the tarballs come from? ☟︎
mod6: we're not going to do that, we're just gonna create a manifest with their proper SHA512 hashes.
mod6: <+jurov> oh it's going to be all unpacked there? << yeah, perhaps not. currently i extract & build all that stuff under 'rotor'. i guess shit should just be: <+jurov> "The shit: BDB, Boost, OpenSSL & the MANIFEST for turds" <- this stuff the turdballs and the manifest.
jurov: "The shit: BDB, Boost, OpenSSL & the MANIFEST for turds"
jurov: and the manifest in /shit
mod6: so the manifest should live in build directory as we were talking about?
mod6: <+mircea_popescu> mod6 but this manifest... wouldn't you say it's of the nature of the sigils ? << im not sure i understand this.
mircea_popescu: mod6 but this manifest... wouldn't you say it's of the nature of the sigils ?
mod6: <+mircea_popescu> the manifest should live wherever the rotor.sh lives neh ? << I would argue that all of these scripts would live outside of bitcoin source V tree.
mod6: the interesting part about dropping in a manifest file is that i'll be off on its own as its own root and its own leaf since it'll have no decendents or antecedants.
mircea_popescu: the manifest should live wherever the rotor.sh lives neh ?
mod6: anyway my question to ascii_field, jurov, et. al. is: given we create a manifest, where should it live in the context of the bitcoin source tree itself
mod6: this Manifest we're talking about creating would need to fit somewhere in the directory structure of bitcoin itself, if it is to be 'v'-ified.
mod6: ascii_field: http://log.bitcoin-assets.com/?date=20-12-2015#1348988 << So I'm gonna be putting just the sha512 hashes of BDB/Boost/OpenSSL .tar.gz files in a manifest that will be added into 'V'. ☝︎
mod6: <+mircea_popescu> listen we really gotta pick one of these and stick to it. << will sort this out with the manifest/file-o-hashes
mircea_popescu: your manifest has .bz2 for boost, .gz for everything else
mircea_popescu: oh the manifest is sha512.
mircea_popescu: and this differs from fc512d3bfa6a39a60fee548775c97239271cf757587b8df7ed739c800844a819a359dca172be0e69ad7752753753139bf11f0813d650066d58386662fe32842d boost_1_52_0.tar.bz2 in the manifest
mircea_popescu: god damned half filled manifest.
mircea_popescu: so basically, the entirety of work of interest here is : go to http://therealbitcoin.org/ml/btc-dev/attachments/20150627/stator_7447d6ad798179d04e9d277acb72799b3c7d0eae.tar.gz ; In 'distfiles', read 'MANIFEST' and place the tarballs found therein in said dir.
mod6: or simply just a manifest of tarballs/deps required for the one-button-push deployment of trb
mod6: dl'em, sign 'em, hash 'em, put 'em in a manifest and distribute?
mircea_popescu: and now : how the fuck is superman going to provide the manifest possibility he's killing the woman ?
mircea_popescu: behaviour manifest in herbivores ffs.
punkman: I don't see why it's better than release being a manifest with a patch sequence
mircea_popescu: no, just make a special patch (for historical reasons called a manifest) that does exactly what you describe
assbot: Logged on 25-09-2015 01:27:12; mod6: one possibility to publish releases in the future now that we have V is to create a manifest of V patches and have the co-chairs sign the manifest, as well as the patches.
asciilifeform: ;;later tell mod6 http://log.bitcoin-assets.com/?date=25-09-2015#1285169 << the way i suggested doing it is to avoid having multiple classes of signed objects. manifest for a release would be merely another kind of patch - one that simply takes every leaf that is to form part of the release head, and add a comment to the top of the file, 'REL-xxx.' this auto-gloms the leaves into a single patch 'handle', think about it. ☝︎
mod6: we could have a signed list of mirrors in the same location as the manifest so that there is some redundancy
mod6: (incase there are patches added to the site webdirectory that are not included in the release manifest)
mod6: So I added subroutines to pull all patches, wots and seals from the foundation site, and/or audit what's already local by checking the local vpatch hashes against the manifest.
mod6: so for instance, I've made http://thebitcoin.foundation/v/TEST2.manifest, so far unsigned as its just for testing my code for a minute here..
mod6: one possibility to publish releases in the future now that we have V is to create a manifest of V patches and have the co-chairs sign the manifest, as well as the patches. ☟︎
mircea_popescu: anyway, the heretical, unwelcome, incorrect, impudent, poisonous, insolent, frivolous, vulgar, coarse, brazen proposition that the poor are not lesser humans but more, in contrary of nature, obvious fact and the manifest will of any conceivable divinity.
ag3nt_zer0: for today's speculative waste: I think it would be great if this room had an educational manifest in the meatspace... sort of like an intellectual spartan boot camp
phf: while china is playing catch up, you get a computing equivalent of wild west with areas where the control simply didn't have resources to manifest, as soon as u.s. stops driving chip design, china will start closing up same holes u.s. is in the process of closing up right now
mircea_popescu: (for the record - lest you be "familiar" with the term from the broken contemporary dictionaries - impudence does not mean "being disrespectful of another person". it has nothing to do with others. impudence is grossly manifest pretense to unwarranted importance. and it's been the distinguishing mark of young adults in agrarian societies since forever.)
mircea_popescu: that there's so precious little intellectual effort dedicated to the topic is prolly the saddest manifest of a dead culture.
asciilifeform: a 'release' can simply be a deedbotted manifest.
asciilifeform: i am also considering a knob whereby one can sign a manifest
asciilifeform: the original manifest used sha256
trinque: result of patch -p1 < genesis.vpatch is a tree which matches the manifest.
mod6: <+mircea_popescu> yeah, mod you have teh honor. << thanks. I've confirmed that what I get from genesis.vpatch out of thin air is the same manifest as `bitcoin-0.5.3-no-crud.sha256.manifest`.
ascii_field: mod6: just grep the diff for '+++' and compare the hashes with sha512sum of directory (your local manifest)
assbot: Logged on 20-08-2015 02:20:07; hanbot: <mod6> asciilifeform: your step "2)", do you mean to indicate reference [1] instead of "also [3]" which is the email to chicken? << i must be dense, where's "bitcoin-0.5.3-no-crud.sha256.manifest"? i don't see it in 1), i don't see it in 3).
hanbot: <mod6> asciilifeform: your step "2)", do you mean to indicate reference [1] instead of "also [3]" which is the email to chicken? << i must be dense, where's "bitcoin-0.5.3-no-crud.sha256.manifest"? i don't see it in 1), i don't see it in 3). ☟︎
mircea_popescu: anyway, i can appreciate the part where usg is there to give money to "compensate" the retarded kids that didn't reverse their spectrometer and so ended up with X loss tjhrough any of thbe multiple avenues. and i can appreciate how this makes lazy people manifest thjeir lazy.
mircea_popescu: recessive genes do not manifest by themselves, thus you can have unaffected carriers. thus they never die out.
mircea_popescu: that's the thing. why we still have hemophilia in spite of it not being desirable : dominant genes manifest by themselves, and thus you can't have unharmed carriers, and thus they die out under pressure.
mircea_popescu: for lack of a better example, might consider http://trilema.com/wp-content/uploads/2015/07/foxy_eulora_craftbottar.gz (included manifest), which does in fact do this, if crudely.
jurov: turdatron needs to take bundles of patch + manifest (at least, can be any other files aside from patches)
mircea_popescu: ascii_field you will notice, if inclined to notice, the distress manifest in the reduction of funding.
trinque: that's what I have in my stator manifest
hanbot: achtung noobkart. stator's distfiles manifest lists a boost bz2, ml67 pulls in gz. bz2 from sourceforge doesn't match manifest's sha512sum, where is correct bz2 located?
ascii_field: mod6: your bdb and other tarballs in distfiles match the checksums in MANIFEST ?
hanbot: asciilifeform / ml folks: from where is one supposed to get the items in "manifest"? eg openssl-1.0.1g.tar.gz