log☇︎
24800+ entries in 0.252s
mircea_popescu: if the same archbishop inquires as to why i poured cement the way i did i can answer without ado. ☟︎
diana_coman: mircea_popescu, ftr I saw and even experienced this sort of trouble but unrelated to C++ as such - related to *programming* in itself really, regardless of language
mircea_popescu: that i can't answer for. but some kind of model as to why deleting inside curly braces works, but not outside they've formed.
diana_coman: the way I see it is that they are basically constraints - of all sorts and not necessarily of some overall design/rationality/logical stuff; if you insist for some reason to do something in that environment, then you have to work within those constraints, as nonsensical as they might be
mircea_popescu: fwiw i personally "shoulder surfed" as i hear it's called two diff people who tried their fucking best to do it. in the end managed as much as to get a command registered and to say hi world! but that was all. well over 30 hours of brow sweat.
diana_coman: kind of curious what does pete_dushenski consider as "results" in such a case: number of participants? the "atmosphere"?
mircea_popescu: in proper terms, "we conclusively show that once reality is replaced by propaganda, nominal increase in food prices as well as nominal decreases in poverty may be claimed to have occured simultaneously. such is the power of rejecting the cold equations in favour of other views that are more nurturing of the mental processes that are most important to us."
pete_dushenski: it wasn't so long ago that 'computer' came with 'screen' for me, as per girls in that trilema piece.
pete_dushenski got goosebumps when eulora 'came to life' late last night as it was first game he's ever compiled from source on linux box or otherwise.
pete_dushenski: might as well
Framedragger: re. latter, yes postgres doesn't instruct, apparently it's efficient on bulk writes that way, as the os can use its own cache to optimize the write order etc..
BingoBoingo reading the novel formerly called Disgrace which I shall call "Africa: Country For Old MEN, and by MEN we mean Petrus" can't help but think poor dumpy Bev ought to take Dave Lurie as Bev's wife
davout: http://btcbase.org/log/2017-01-01#1595029 <<< try living i a country where you could almost buy dynamite sticks in the same shop as the barbecue meat ☝︎
asciilifeform: perhaps asciilifeform , ben_vulpes , other usaschwitz inmates, left alive as a kind of insult.
trinque: it is the empty set that explodes in circles in my mind, not that I deny that it must be named first. that the definition of all things has void as a dependency induces virtigo when looking out at the world.
mircea_popescu: and in this perspective, arguments as to the existence of gods become truly amusing. even in a world in which, through some strange workings of happenstance, no set of four items did in fact exist, nor ever had, and supposedly never will... there's also no number 4 ?
mircea_popescu: "i gotta borrow trinque for a minute. i scrubbed the expiry off my pgp key, which of course makes a new pubkey even if it is the same modulus as before" not "i gotta borrow trinque for a minute. i have a refreshed (nonexpir) pubkey as of 5 min ago"
trinque: yet another man perceives him as bedrock reality there before the stars
trinque: I'm saying a man creates "apollo" the symbol as an act of will
asciilifeform: i gotta borrow trinque for a minute. i have a refreshed (nonexpir) pubkey as of 5 min ago
trinque: as all gods of which I'm aware are written (willed) narrative, there's an interesting membrane there
mircea_popescu: you don't make a very good teacher, even as you're a fine engineer!
a111: Logged on 2016-12-31 06:54 davout: http://btcbase.org/log/2016-12-31#1594446 <<< i'm confused, isn't the 8-ball a set of factors that you multiplied into the running product, and for which 're-running' makes little sense, as being already present in the global factors product?
mircea_popescu: not as productively, yes, not for the end user, at any rate, but there never was a rule that intelligence be benevolent.
mircea_popescu: the "apple software ecosystem", while on a level dysfunctional as ben_vulpes oft informs us, is on another edge intricately designed.
asciilifeform: i dun see this as a necessary hypothesis. i dare say that if i had to write a c compiler, it would end up looking somewhat more like llvm than gcc.
mircea_popescu: but not just llvm - the whole world exists, and it produces things such as "'Static linking of user binaries is not supported on Mac OS X. Tying user binaries to the internal implementation of Mac OS X libraries and interfaces would limit our ability to update and enhance Mac OS X. Instead, dynamic linking is supported (linking against crt1.o automatically instead of looking for crt0.o, for example). We strongly recommend tha ☟︎☟︎
asciilifeform: noshit 'they knew', all compilers are built on roughly same scheme, just as all airplanes have wings, fuselage, etc
phf: windows for a longest time had a very stable abi, as per "you can run windows 95 programs still!1", where's i suspect mac os x probably doesn't. it's the same problem on openbsd, sure you can static link, but you will have to recompile after the next release.
mircea_popescu: the point, however, is that before i will use the tools, i'd rather parlay with the idiots as if they were, somehow, people.
shinohai: I think /ignore *!*@freenode/staff/* NOTICE works as well
Framedragger: btw asciilifeform, if you want to be even more sure that no postgres data is lost while being written during power failure, you probably need to disable disk controller and disk drive caches, if at all possible. but maybe you've done this.. as per https://www.postgresql.org/docs/current/static/wal-reliability.html
a111: Logged on 2016-12-31 04:50 asciilifeform: 'The ability to limit concurrent coredumps allows dumping core to be safely enabled in these situations without affecting responsiveness of the system as a whole. I have several servers running with this patch applied (actually backported to v2.6.26) and it has allowed me to deal successfully with the situation described above.'
davout: http://btcbase.org/log/2016-12-31#1594446 <<< i'm confused, isn't the 8-ball a set of factors that you multiplied into the running product, and for which 're-running' makes little sense, as being already present in the global factors product? ☝︎☟︎
asciilifeform: 'too many is as good as none, so let's then give'im none'
asciilifeform: 'The ability to limit concurrent coredumps allows dumping core to be safely enabled in these situations without affecting responsiveness of the system as a whole. I have several servers running with this patch applied (actually backported to v2.6.26) and it has allowed me to deal successfully with the situation described above.' ☟︎
asciilifeform: does a modulus count as 'has factor' if gcd(it, another) == it ?
asciilifeform: as soon as this batch fully digests, i'ma switch off the werker until further notice. could be couplea days.
asciilifeform: interestingly i found several instances in log where werker crashed with a div0. and then went, by hand, to verify if i am a tard and permitted a crafted key containing 0 as modulus to be submitted. but no dice.
asciilifeform: (werker is as it was in april.)
mircea_popescu: as you say, odds of it being composite in the end pretty good anyway
asciilifeform: (this is a bug! as in, a case i never properly handled! when entire modulus is also a factor of another. i will have to filter these)
asciilifeform: by attempting to load ~every~ result, as, predictably, it wants to.
asciilifeform: and, again, 'displayify daily' will nuke the 'use as sks, check pasted keys in real time' aspect.
asciilifeform: as usual, whenever we ~really~ lean onto something, it crumples into the pile of shit that it was.
asciilifeform: http://btcbase.org/log/2016-12-31#1594370 << no, it is a peculiar bug, that i will fix as soon as current packet terminates. though strangely enough every single instance of it to date resulted in a validly phuctured (factors smaller than self) modulus eventually ☝︎
asciilifeform: ben_vulpes: because i wrote it as one
deedbot: http://trilema.com/2016/disgrace-the-house-is-just-as/ << Trilema - Disgrace - The house is just as
asciilifeform: the one where 'chick is unsure whether she is being used as a woman, or as poke chip in a hidden casino'
asciilifeform: (google is, as usual, unhelpful)
mats: seeing as how hamas is mobile and the dome is static, i don't see how it could possibly work 9/10 times like .is claims
asciilifeform: as mircea_popescu correctly said -- snoar
asciilifeform: thing shows up as ~three mice when plugged in!
mircea_popescu: asciilifeform the loss was extracted in the field of battle, and came as actual, isis-equipping dollars.
mircea_popescu: the currency of the reich is, as the original hitler well observed, a sort of sweat.
mircea_popescu: that "and them only" trailer is mostly why we haven't had the pleasure. just as soon as hitler figures out how to remove it, he WILL burn his citizenry into a crips, as he always does.
mircea_popescu: this is a best case view not supported in practice (by which practice we mean the repeated etherape, symbolic as it is of the chances of the premier science and technology institution in the world in front of a loose assemblage of things that don't, supposedly, exist.)
asciilifeform: as soon as you touch the hot wire, you now have a 'schrodinger's blockchain'
asciilifeform: otherwise interpreted as epochtime.
mircea_popescu: but as far as software design and business risk planning goes, importing any prb means locking in a certain future loss.
mircea_popescu: asciilifeform there is no such thing as "immediately mine".
davout: mircea_popescu: yeah, i meant it as a separate, user-initiated step
davout: anyway, i guess my position basically boils down to: "as far as trb proper is concerned, best wallet is no wallet. but sane indexing mechanisms"
asciilifeform: mircea_popescu: as i understand, thread was originally about 'sane wallet mechanism'
davout: i might very well broadcast other folk's txes from my node, just as well as i might broadcast my own txes from arbitrary shitnodes
asciilifeform: even if not as catastrophic as privkey leak
asciilifeform: just walk the new blocks. as is done now.
asciilifeform: but the probability of 'txtron suggests 'send all money to karpeles' or 'send a million btc as fee' ought to be 0.
asciilifeform: ben_vulpes: as i understand, davout was asking for sane-wallet, rather than merely raw-tx-hopper
mod6: no room for error here, lest someone sends all their coins out as a large fee, or some crazyness.
asciilifeform: as in, y'know, the thing that wallet ~ought to have done from day 1~
asciilifeform: ben_vulpes: this won't , as i understand, help him, he wants to ~craft~ tx, not merely broadcast-raw
a111: Logged on 2016-12-29 22:54 ben_vulpes: jurov: would you be so kind as to update the lxr with makefiles.vpatch ?
mircea_popescu: phf yes, but a fine approach to answering "what is the basis of alf's value as an engineer" is pointing out that he runs phuctor on the phuctor box, which fails to cost 5k/mo.
mircea_popescu: what you want matters as much as what you hope.
asciilifeform: i pissed on 'db' concept as a student, and i piss today: custom data structure for each job! the year ~is~ 1972.
phf: not just postgresql mind you. oracle definitely, mssql as far as i know
phf: well, "you either expect" is because ~sql~ as a db language is specified to have acid. there are databases that support dirty reads/writes they are just not "sql"
mircea_popescu: whether i want consistency as arbitrarily defined by you is my decision, not yours.
phf: jurov: well, it's not clear where "disregard all locks" comes from in the original request. if the actual operations are as asciilifeform describes, i.e. sporadic inserts, and sporadic selects, then there will be no locks. my point is that there's no "disregard all locks" in postgresql, you solve it by knowing what lock you're hitting, and then designing your query to sidestep the lock
mircea_popescu: asciilifeform as to "how to make www respond", you use the method we were discussing last time, whereby www is a cached image and if out of date tough for viewer ; as to nursery "do we have this ? how about this?" you really want the db to do that for you, it's ~the only thing it;s good for.
mircea_popescu would not be particularly surprised if served with 100mb of query as per above postres wouldn't just fall over.
Framedragger: docs say would need to get rebuilt only if there were any unwritten changes. which there shouldn't be as asciilifeform is not using write cache
asciilifeform: mircea_popescu: the other obvious thing would be to dispense with 'real time submission' entirely, and when someone dumps in a key, it goes into next batch. but we discussed this earlier in this thread, it would mean that the thing cannot be used as sks-like tool.
asciilifeform: (and bernsteinization requires access to ~all~ moduli, as i think is obvious, and not simply 'most recent ones')
asciilifeform: and no, you can't query the nursery every time somebody loads a url, or you get SAME performance as now, omfg
asciilifeform: otherwise we get same speed as now.
mircea_popescu: yes, well, that's then the problem. they should go in as a single query the size of the batch, with the items sorted within it
asciilifeform: i dun give half a shit about 'image'. laying out the fact of why the thing is as it is.
asciilifeform: they get thrown into same hole as if human submits.
a111: Logged on 2016-12-30 16:11 mircea_popescu: http://btcbase.org/log/2016-12-30#1593286 << actually workmem should be 256mb especially as you can afford it so totally, go for it.
mircea_popescu: asciilifeform if that's where it spends most time then a) http://btcbase.org/log/2016-12-30#1593462 is very likely to help and b) preparing your whole query as ONE single sorted item will help also. ☝︎
mats: fbi evidence of ru hacking 10/10 lulz as expected
asciilifeform: phf: understand also, postgres can't store bignums as such, it stores strings
mircea_popescu: which yes takes some work, but not quite as much as the other variant.
mircea_popescu: and you do it as prepared queries, which get precompiled to a degree
mircea_popescu: trinque 's idea, bernstein as prepared queries, may be a gain.
asciilifeform: phf: nope. the only thing that happens to db as a result of bernsteinization is N queries 'do we already know this factor'
mircea_popescu: ah then not nearly as important.
mircea_popescu: 1) shared_buffers is to be per spec "25% of available ram" ; but it does diminish returns in the gb. you probably have it as 128mb, make it 2gb say.