200700+ entries in 0.122s
trinque: danielpbarron: seems ok, maybe my
tar or gzip has
the HIV
danielpbarron: and is it redundant
to include sha512 on both
the
tar.gz and
the iso?
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: danielpbarron: lets work on getting
those in next week
trinque: then also danielpbarron
this project with ISOs might
take rewriting
the downloader, will have
to look at it
trinque: I'm getting on
the previous batch of deeds
that I have insufficient funds, which is bullshit.
danielpbarron: will be interesting
to see if my unopened 5.5 cd1 is
the same bitwise as
the one in
the above mentioned deed
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?
trinque: got 10s of gigs over
there free, nah
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: does
this query look up
the mod IDs
to append
their factor arrays, or does your worker already know
those
trinque: know mod IDs
to update at
this point?
trinque: array
type in db or join
table?
trinque: the insert statement can return its id
to a calling update statement
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.
trinque: the "unique" is just an index which yes eggogs if insert happens and is already present.
the eggog is just a matter of how do you want
to find out about
this
trinque: well one sec, so you're
trying
to establish relationship between keys and factors in
the db, yes?
trinque: you have a keys
table, factors
table, factors has a unique constraint on value column of factors,
there is a join
table called key_factor which joins key and factor
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: you conflate
the paper delivery kid with
the printing works and
the writers and, and, at your own design
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: so you're
talking
to me about Framedragger's whatever, k
trinque: ^ find reference for
this pls
trinque: asciilifeform: you did not seriously cogitate on anything I sad for more
than 5 seconds
trinque: if so dispense with republic, bring on
teh stalin
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: rewriting 60000 lines for
this.. how does
that follow..
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)
trinque: not let
them seep all
through
trinque: my proposal was
to put your
turdworks in a box
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.)
a111: Logged on 2017-04-07 15:30 asciilifeform:
this is how winblowz ended up with bookcase-length api, people.
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: which means, "whenever new row, send it off [without having
to execute a new select query etc]"
Framedragger: it is updated in ~realtime from
the master via streaming replication
Framedragger: but you no longer reading from
the front (in
the sense of sql queries), which in db-land is good for performance.