Framedragger: mircea_popescu: everything except sadmods so as not to upset phuctor too much. need to discuss frequency of caching with asciilifeform i think

Framedragger: eh there was a plan for phuctor to ingest these certs, too, i think?

Framedragger: BenBE: you can generate the phuctor fingerprint for linking directly to phuctor via http://siphnos.mkj.lt/datadrop/crap-from-scans-to-be-sorted/phuctor-fp.py (could be useful)

Framedragger: !$ phuctor

Framedragger: BenBE: you had some questions about phuctor?

Framedragger: mircea_popescu: re "nothing here" the idea would be that upon user submitting gpg key, page reloads *instantly* (vs. near-instant page load on current phuctor - reloads only after key inserted into db), shows permalink and "waiting for insertion" msg; html could have property to auto refresh every second until master responds with any links to other keys. but i understand asciilifeform's reasons against this

Framedragger: (just so i don't feel like just throwing random verbiage at you, what i mean is something like `CREATE TRIGGER setup_send_update AFTER INSERT OR UPDATE ON phuctor FOR EACH ROW EXECUTE PROCEDURE send_update);` - it wouldn't be hard to try.)

Framedragger quite certain he would get erection from that small c program in phuctor, and that is great ☟︎

Framedragger: you are presenting a false dichotomy consisting of {current phuctor; $multi-mil db setup}. you propose to escape it by writing new db as the only way to escape it.

Framedragger: now, complexity management-wise.. maybe; having same person manage both boxes may not be best idea (and the alternative has its own advantages). but the current "phuctor is down, i don't know why, it's a black box" isn't the greatest example of current setup, either. (this may be a red herring, i'm not sure)

Framedragger: bandwidth required for the www box would be ~same as what's currently needed from phuctor.

Framedragger: bandwidth? bandwidth required for phuctor box would be "what's needed to send new rows to this other box".

Framedragger: of course being able to point to a working prototype would do so much more than arguments. unfortunately that would most likely require the needed modifications on the phuctor box, so a bit of chicken-and-egg.

Framedragger: asciilifeform: hold on. the idea was to separate reads from writes. having a separate box for www which gets updates from phuctor box, and having pg indices on it for quick search is *not* resource-intensive. i can cite examples but basically i'm quite certain that a <= 16gb memory box would suffice. phuctor box is 256 gigs yes, but it does *so much more*.

Framedragger: asciilifeform: the parallel to "this is how winblowz blew up" breaks, imho, if you consider the splitting-off of www not as an addition, but as actual splitting-off, i.e., the box with phuctor on it may no longer have a www interface (just an option, i know you may be against it). if you picture it that way, it's more about modularisation vs. fixing and inflating a single monolithic thing.

Framedragger: obtw which postgres version on phuctor asciilifeform? those two features not available in old versions. i don't remember which ver is in debian stable

Framedragger: yes indeed, however asciilifeform's initial objection (besides other less clear unwillingness) was the requirement for phuctor to show 'live data'. which imho is not necessary. ☟︎

Framedragger: asciilifeform: i also wonder if phuctor site my come under additional stress now that you removed those 'Disallow' entries from robots.txt :/

Framedragger: !$ phuctor

Framedragger: anyway http://siphnos.mkj.lt/phuctor-stats/ will continue to rehost phuctor stats (including http://siphnos.mkj.lt/phuctor-stats/phuctored.html), and will see about more lenient update times (5min is excessive anyway)

Framedragger: asciilifeform: phuctor.nosuchlabs.com timing out, do you think this could be related to the cron cacher? (GET /stats every 5min, GET /phuctored every 60min)

Framedragger: mircea_popescu: if you're planning to rehost, maybe useful (very simplistic, i've just put this into cron for now): http://siphnos.mkj.lt/phuctor-stats/download-stats.sh

Framedragger: i sed'ed the relative urls, as in "<a href="/">Submit GPG Key</a>", to point them to phuctor, etc

Framedragger: btw asciilifeform mircea_popescu i'm rehosting the main '/stats' page here, autoredownload every 5min (handles http timeout cases): http://siphnos.mkj.lt/phuctor-stats/ ☟︎

Framedragger: heh. well http://nosuchlabs.com/robots.txt does have "Disallow: /gpgkey/" but phuctor.nosuchlabs.com itself should still be indexed i think? ☟︎

Framedragger: that didn't work till i read that the password is now phuctor. omg lmao

Framedragger: last note mircea_popescu, paper in question does acknowledge the fact that as regards rsa factorisation, their attempt is a *replication* (unless i misread). but yes, should be beaten for not mentioning phuctor.

Framedragger: asciilifeform: how little of the data is public is indeed *shameful*, and in that regard, phuctor should be lauded for making all data available.