67700+ entries in 0.505s
Framedragger:
i wonder how you'd categorise the 'affect heuristic' as kahneman et al. call it.;
i.e., when you make decision with at least partial influence of current emotion. it's very *fast* (thereby falls under kahneman's type 1). ridiculous scenario where it's useful:
i'm chased by tiger, see two paths in woods, one has sign 'DANGER' in red,
i don't have time to even parse word without making decision,
Framedragger: kk. yeah
i won't argue further without doing some decent mp1 thought here :)
Framedragger: (but
i'm probably conflating things too much, maybe you'd call such reactions something else)
Framedragger: also just to note, (obvs) type 1 (mp-type 2) has its merits and is important. but yeah
i got your point
a111: Logged on 2017-04-07 18:08 Framedragger: mircea_popescu:
i thought one of the parts was a c proggy. quite certain it is, asciilifeform mentioned it multiple times. python is the web backend afaik
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
a111: Logged on 2017-04-07 16:33 Framedragger: (
i'll just note that the *permalink* can be derived on the slave box, and nowhere did
i say something contradicting this)
Framedragger: mircea_popescu:
i thought one of the parts was a c proggy. quite certain it is, asciilifeform mentioned it multiple times. python is the web backend afaik
☟︎ a111: Logged on 2017-04-07 16:18 asciilifeform: understand, if
i paste a gpg key into phuctor, and cannot then ~immediately~ link to it in-chan -- phuctor is broken!!
danielpbarron: also please let me know if my format was right.
I emulated mod6's thing but maybe there's a better way to do it with iso
trinque:
I'm getting on the previous batch of deeds that
I have insufficient funds, which is bullshit.
danielpbarron:
i even have the missprint 5.8 and the replacement cd they sent afterwards
danielpbarron:
i can do an unboxing video or something.
i have 5.5 through 5.8 in original sealed packaging
☟︎ trinque: when we get it to work, all, far as
I'm concerned
danielpbarron: on a related note, which openbsd cds are specifically wanted?
i did 5.5 cd1 because
i have that pack opened already, and because the more useful cd2 (containing amd64) got damaged when
i tried to remove it from one of my iMac G3s that wouldn't spit it back out (it also has ppc -- probably the arch of interest)
shinohai:
I was gonna say, all those trb artifacts were huge
danielpbarron:
i was voiced obviously, but maybe deedbot had reconnected since then, and didn't see me as authed anymore?
a111: Logged on 2017-04-07 16:48 asciilifeform: trinque: can
i , purely using sql query, force it to not attempt write ( and -- importantly -- to take no locks ! ) if an item already exists ?
trinque:
I'm of course shooting in the dark as to what happens when in what you have.
jurov: coinbr public announcement: there are some stuck orders, and it came at worst possible time. During the weekend
I should be able to fix.
Framedragger: last note before
i fuck off: the "user submits key; gets permalink (immediately); meanwhile key gets sent to master (immediately), and master puts it into "to be inserted" queue" + "all inserted + updated rows get sent back to slave via streaming replication and pg trigger" doesn't look like petrocheese to me. is all.
trinque:
I'm not defending that because it's not what
I said.
Framedragger: (
i'll just note that the *permalink* can be derived on the slave box, and nowhere did
i say something contradicting this)
☟︎ trinque: asciilifeform: you did not seriously cogitate on anything
I sad for more than 5 seconds
trinque:
I find the notion that asciilifeform here is the only guy capable of adhering to own standards lulzy
Framedragger: asciilifeform: yeah
i said some stupid things, apologies for depressing you there
Framedragger: if people decide to compromise on things after an agreement was made not to,
i mean.. fuck those people
Framedragger: asciilifeform: fwiw
i'd be willing to set up a read slave on 16gb dedi box (siphnos, unmetered connection) for fri, that part is not hard imho. sure, if/when decision would be made to *actually expose it to everyone*, things could be moved (and maintained by someone else), but this is one way to prototype things.
trinque: you *have* turdworks by your own decision to use www (which
I think is reasonable)
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: that is fine, and a postgres trigger would mean that any affected row gets sent off.
i do understand that new-key-addition is a db-intense process, of course
Framedragger: (again,
i did realise that the "oh very simple" angle isn't strong here)
a111: Logged on 2017-02-19 03:54 asciilifeform: (iirc we had a thread where
i described how corporate ameritards, if given a problem like phuctor, would happily soak up a few $mil and megawatt of iron)
Framedragger: alright.
i will grant you that the end system wouldn't be "oh so elegantly simple", because you would have to have a submission queue (maybe something that trinque had in mind). user submits key; gets permalink (immediately); meanwhile key gets sent to master (immediately), and master puts it into "to be inserted" queue. under normal loads, the insertion happens ~immediately,
☟︎ Framedragger: however, you won't agree to drop it,
i take it.
Framedragger: hold on, hold on. first of all, regarding the permalink: you can have this anyway, because the hash is computed in python anyway (
i ~recall the procedure that you once gave me). so,
Framedragger: asciilifeform: aha, right, that.
i literally forgot about that lol. but wait, first we need to clear up the question about whether you want an immediate result to be shown to user upon gpg key submission.
Framedragger: (again tho, it's very easy to just point finger at features, so
i'll gladly shut up)
Framedragger: well,
i'm not that certain, but
i am assuming you have more experience there with me.
i will only remark that you merely need a *read slave*, not an actual mirror db which can handle writes and sync state. the syncing would go one way only. (hence the multiple references to pg streaming replication.)
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: 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.
a111: Logged on 2017-04-07 14:44 trinque: mircea_popescu: more clearly stated,
I do not see a www as part of the algorithm of phuctor. it is one source of input where there could be many, and one output idem. with a clearly defined line between www and phuctor (even allowing for that www may require cached copies of phuctor data to operate properly), this gives you something you can nuke later and replace.
mircea_popescu: no
i don't mean that.
i just mean, yes in principl;e doing something with the plebs is not a bad idea ; but the exact what and wherefore coulo use more conteplation.
trinque: mircea_popescu: more clearly stated,
I do not see a www as part of the algorithm of phuctor. it is one source of input where there could be many, and one output idem. with a clearly defined line between www and phuctor (even allowing for that www may require cached copies of phuctor data to operate properly), this gives you something you can nuke later and replace.
☟︎ shinohai:
http://btcbase.org/log/2017-04-07#1639637 <<< This is what
I said to Steemit evangelist R. Hilarski a few days ago when he accused me of just hating on altcoins. "When you lose all your BTC in scams, at least your wife is kinda hot so she can come by trilema and bare her tits for bits."
☝︎ trinque:
I'll close with the observation that asciilifeform's "fits in head" serves "build to iterate and throw away" very well.
trinque: asciilifeform:
I threw away first bot, and second bot, and we sit here with the 3rd
a111: Logged on 2017-02-19 03:54 asciilifeform: (iirc we had a thread where
i described how corporate ameritards, if given a problem like phuctor, would happily soak up a few $mil and megawatt of iron)
trinque:
I could tune my truck's engine all day and hauling 7000lbs vs 2000lbs will have greater effect
trinque: asciilifeform: if stuck on python, which
I grant is practical, can't really refuse the customary sins to make it go
mircea_popescu: open question whether cl would be fast enough. though
i know there's some people itching to answer it.
trinque: oh
I proposed nothing for this fractal hell!