asciilifeform: and what else they've been lying about.

asciilifeform: i'd like to know!

asciilifeform: i have nfi. but process runs reniced.

asciilifeform: lying liars.

asciilifeform: supposing i even see it again.

asciilifeform: but please do not expect anything like regular update

asciilifeform: Framedragger: you are welcome to a copy of db as soon as i get my hands on it again

asciilifeform: and not without rewriting entire thing.

asciilifeform: but not effortlessly.

asciilifeform: Framedragger: it is doubtless possible to optimize .

asciilifeform: whenever ANYTHING is added , it first has to be searched for in each of these classes of item, in the case that it may already exist there.

asciilifeform: and moduli, stored separately, linked bidirectionally to/from keys, ditto factors for same.

asciilifeform: it is a db of ~5 mil KEYS, each of which is from 1 to 20kB, and links, etc.

asciilifeform: it is not a wordpress blog with ~static 5 mil words.

asciilifeform: try to apprehend the scale of the thing.

asciilifeform: because, for instance, the key-eater is a separate process. and has nfi that someone else wants the db.

asciilifeform: if you want anything from the db, you wait. for , possibly, HALF A MINUTE

asciilifeform: understand ?

asciilifeform: Framedragger: TOUCHING THE DB AT ALL IS SLOW

asciilifeform: understand, if phuctor were an american 'corporate' production, it would make use of at least entire RACK of boxes

asciilifeform: *possible

asciilifeform: we are at the farthest possibly limit of what can be done on one box, at anything like reasonable budget (whether paying the cost of a small european flat for a server for public service is 'reasonable' is separate question) ☟︎

asciilifeform: ^ is the db

asciilifeform: Framedragger: you do not seem to understand, so i will give illustration: http://www.swapmeetdave.com/Humor/Workshop/Lumber-Car-A.jpg

asciilifeform: and there is ~0 way around it , other than by doing the static thing.

asciilifeform: Framedragger: db being hammered 24/7 with 'do we have this hash' 'do we have this fp' 'add this and this' 1000/sec is the bottle. ☟︎☟︎☟︎

asciilifeform: and, to continue to rain on the parade, if every www site has to be run like mpex, it will cost. and the range of things that can be provided 'for the public', 'for phreeee', will correspondingly shrink.

asciilifeform: this was my reaction also.

asciilifeform: ^

asciilifeform: Framedragger: it is called phuctoring

asciilifeform: Framedragger: understand, EVERY page in phuctor is subject to change

asciilifeform: Framedragger: because at its current speed this will take you 50 years.

asciilifeform: true, as of this week.

asciilifeform: but not raw.

asciilifeform: mircea_popescu: that would make problem even worse, could no longer search logs for a gpg fp

asciilifeform: the answer is 100% yes.

asciilifeform: and reprocess ENTIRE db.

asciilifeform: Framedragger: the fundamental problem is that i will have to rewrite WHOLE THING for any of this to possibly happen.

asciilifeform: (and then , in debian run, the rss feeder itself overflowed )

asciilifeform: mircea_popescu: for quite some time, the rss thing did not display clickable links in chan for phuctor due to overflow

asciilifeform: (pretty sure these 2 did. slowly, painfully.)

asciilifeform: i dunno that anyone other than google and yandex ever made a ~full phuctor~ snapshot.

asciilifeform: fri. sept. 23.

asciilifeform: http://www.loper-os.org/pub/snap/ph_snap.html

asciilifeform: mircea_popescu: there is an independent snapshot on my blog, also. but also a month old.

asciilifeform: my hands presently are quite full with polishing off the prospectus for said item, and www page / invoicetron.

asciilifeform: as in , physical device.

asciilifeform: Framedragger: dunno if you read the broadcasts, but we have an actual product rolling off conveyor as we speak.

asciilifeform: probably how www will work, if it at all even works, in near future.

asciilifeform: i really ought to have made entire thing a c proggy that shits out static html once in a while.

asciilifeform: currently they are generated programmatically. will have to rebake whole thing such that they exist as static texts on disk.

asciilifeform: well yes, but each one is own page

asciilifeform: though then you want to see the unpopped subkey siblings of the popped moduli, and start clicking, and you'll get zip.

asciilifeform: but yes, 'phuctored.html' is a few MB currently.

asciilifeform: 'just popped' means that you can no longer use it, as previously suggested, in place of sks, for instance.

asciilifeform: likewise bandwidth, considerably.

asciilifeform: that's a few dozen GB.

asciilifeform: Framedragger: db would have to exist locally on the vps, for the thing to work more or less reasonably in real time

asciilifeform: the 1 minus is that the -- already quite costly apparatus -- would cost yet moar.

asciilifeform: but yes, mircea_popescu is quite right re 'ought to cut'em apart'

asciilifeform: i dun think anything short of unplugging the box will stop processing.

asciilifeform: this, yes.

asciilifeform: (needs 0 net pipe for this)

asciilifeform: i will point out that, unless the box has been stolen, it is still processing keys at same rate

asciilifeform: mircea_popescu: cheap vps will fall down just as readily when flooded (as will the trb node, mine or anybody's)

asciilifeform: the box per se is ultra-responsive, even when 'werker' is firing (i leave a core open)

asciilifeform: the db!

asciilifeform: dollars to doughnuts thing is under syn flood.

asciilifeform: it wasn't overloaded.

asciilifeform: 1st ask'em 'wtf'

asciilifeform: can ping, 150ms or so, but that's all.

asciilifeform: trb, ssh, www, all.

asciilifeform: mircea_popescu: it's dead in the water.

asciilifeform: (and , for folks with poor reading comprehension, i will repeat - entire box is ~unreachable, trb node, ssh, 80, etc )

asciilifeform: Framedragger: all of this is quite academic if thing cannot be made to reliably stay up.

asciilifeform: ben_vulpes: heathen-facing publicationtron is inherently contradictory thing . ☟︎

asciilifeform: then it ain't 'box'

asciilifeform: box that stays up - likely, needs new internet.

asciilifeform: them who want mig -- are the lucky'uns. all ya need is a bag of money this-wide and this-tall, and here's yer mig.

asciilifeform: box that stays up - different matter.

asciilifeform: mig -- actually exists...

asciilifeform: at any price point

asciilifeform: which seems to be beyond the current technological state of the art.

asciilifeform: ben_vulpes: the main thing wanted by 'people doing most of the analysis' is a BOX THAT STAYS UP

asciilifeform: db is under ~constant ~100% load as-is.

asciilifeform: i cannot offer anything REMOTELY resembling real-time replication, either.

asciilifeform: (backups are a monthly affair, any more often would -- again -- grind whole thing to a screeching halt)

asciilifeform: the most i can offer to anyone is a static copy of the db. and that is supposing that the box comes back up, and stays up.

asciilifeform: it needs a key eater that doesn't saturate the db capacity 24/7 -- yes. a server that doesn't fall down when washington farts on it -- also yes. 'js visualizations' ??

asciilifeform: i utterly do not see , i confess, why phuctor needs 'visualizations' etc

asciilifeform: but it is neither here nor there, the server - falls down whenever enemy wants it to fall down.

asciilifeform: http://btcbase.org/log/2016-11-19#1570743 << i have, as you can surmise, own comp, that still works ☝︎

asciilifeform: mats: familiar with idea of 'risk homeostasis' ?

asciilifeform: ('but,' , said my internal mircea_popescutron, 'nobody had the slightest inclination to examine anything!' -- but this is besides the point)

asciilifeform: i wrote, in the qntra piece, 'examine debianized boxes for nsaware'. now 'owner' will have a chance to clean up before any mass 'examination' takes place. ☟︎

asciilifeform: Framedragger: it is unreachable WHEN IT COUNTS

asciilifeform: the 24/7 ssh pipe i had to the box on dedicated display - also dead.

asciilifeform: the trb node just as dead.

asciilifeform: it's a syn flood.

asciilifeform: (but -- loads.)