219900+ entries in 0.987s
a111: Logged on 2017-01-27 18:04 asciilifeform: but in latest lulz,
http://archive.is/8G35m >> 'O’Grady was mistakenly identified
this week as a Secret Service agent (also named Kerry O’Grady) who is under investigation for posting a statement on Facebook
that appeared
to indicate she preferred jail over being shot and killed for President
Trump.'
mod6: <+davout> mod6:
ty, will
try
the gnu-awk
thing << ok, gl. let us know how it goes. i've had
this issue before myself. i ~think~
that's what I did
to resolve it on my african box.
trinque: jobs may have actually killed someone with his hands if he saw
the "o look mother I put
the apple watch inside
the mac"
ben_vulpes: asciilifeform: on
the "oh noes apple broke more shit"
thread, not only do pageup/down not work, but apple's own messenger wastes all
the CPU
that "Slack" left on
the
table
ben_vulpes: it's not even an altruism
thing, it's a "do you serve a churning vat of cockroaches or kings with names"
Framedragger: on
the other hand, i could see
the latter being *really* useful for many. granted, neither you or me are altruists.
ben_vulpes: logs and search will at
the least provide interesting lessons in postgres design and optimization. writing my own disqus, not so much.
☟︎ Framedragger: re. a), i
totally hear ya. i mean, who does. re. b), yes i can see
that.
ben_vulpes: Framedragger: for all of
the
time i have spent losing my mind in radioactive webtech mines i a) do not like
the domain b) have zero desire
to build half-baked solutions when ~fully baked ones exist
Framedragger: that does break
the 'change, see immediate effects' loop, hm.
ben_vulpes: Framedragger: because it is wholly unacceptable
that i not be able
to see
the effects of changing one
tag in
the source files immediately.
ben_vulpes: and i wanted comments, but did not want
to bake myself further into an ossified
tower of software retardation.
Framedragger: why's
that bad? i understand if
the 'time it
takes
to render' function is exponential in some way or another, but if linear growth and less
than say 30 min - what of it, really
ben_vulpes: eventually grew
to over sixty seconds per export run.
ben_vulpes: Framedragger: you missed
the good old days when i exported raw html from an org file
a111: Logged on 2016-07-15 10:31 Framedragger: regarding LAMP stacks and blog software: static site generators are
there for a reason. significantly smaller codebases and attack surfaces cf. wordpress. just sayin'.
Framedragger: i'm still preferring
http://btcbase.org/log/2016-07-15#1503181 but granted, don't have a working "moderated but without captcha" comments solution. best i can
think of is, write very light backend service
to handle comment post requests, store
them somewhere sensible, allow operator
to accept/deny comments (could be flat
text files)
☝︎☟︎ ben_vulpes: outhouses and
trenchfoot.
that's webdev!
trinque: be ready
to fill with dirt and dig another, and everything will be fine
trinque: anything
touching
the web is an outhouse
ben_vulpes: except of course
threaded comments, and
this and
that and
the other
thing.
☟︎ ben_vulpes: fact of
the matter is
that wp 2.7 does ~everything a person needs from a personal cms afaict.
ben_vulpes: but yes, fix
the javascript only
to find
that it never worked in
the first place, and
the replytocom query parameter doesn't set
the parent_id variable apparently at all
ben_vulpes: but
the use of a friend's backhoe
to put in a septic system
to replace
the outhouse.
ben_vulpes: am wasting
time fixing
the wp comment
threading shitshow already.
Framedragger: (i personally like
the pink highlight, it's immediately noticeable but still readable)
ben_vulpes: asciilifeform: no, i'm ready
to eat
the whole wad.
ben_vulpes: yes well i may as well just scrape btcbase at
that point asciilifeform
Framedragger: bouncer is actually quite nice, as phf said;
that's what he had before, he wanted db for xrefs etc
ben_vulpes: i *have* put some
thought into
this project, asciilifeform.
Framedragger: nothing pretty. if any use, could give
tarball of bouncer logs
ben_vulpes: is it not bouncer logs -> html
transform?
ben_vulpes: asciilifeform: i can scrape btcbase as well as
the next feller.
ben_vulpes: was
this before or after
taking responsibility for critical infrastructure?
ben_vulpes: which, subject
to opsec constraints, is a fine
thing
to do.
ben_vulpes: unless i misremember,
the man is in
the habit of at least mentioning prolonged absences.
☟︎ jhvh1: asciilifeform: phf was last seen in #trilema 1 day, 22 hours, 3 minutes, and 31 seconds ago: <phf> so if you have a system
that you implemented fast, but it's slow, but you know how
to now slowly make it fast, you have a strategy. if you're chasing corner cases, running a profiler and get mostly flat distribution, writing in special cases, etc. you don't have one
ben_vulpes: phf: and on
this,
the
third consecutive day of asking, would you kindly acknowledge receipt?
☟︎☟︎ trinque: the guy already said ok
to shipping a
txn maker with
the patch!!
trinque: the wallet merely generates inputs
trb will validate or not independently of it
trinque: the wallet does in no way define
the operation of
the protcol or validating blocks
trinque: must be right next
to
the "fork
topic" button
davout: asciilifeform:
trb is about keeping
the core, prb is about "moar featurez"
ben_vulpes: davout:
there are many parts of a kalash
that are not strictly ergonomic.
davout: ben_vulpes: yeh, not
that
the miner-snipping doesn't itch
ben_vulpes: asciilifeform: no argument, but i do not see
the point of moving output indexer into a separate bin given
that it needs a live blockchain anyways.
trinque: and it
tells me "fuck you" or "yum"
trinque: nothing helps me generate a valid lisp statement for sbcl other
than I pop one in
davout: ben_vulpes: but even if separate binary i see
this more as a "reference wallet" in
the same way
the "reference miner" demonstrates what a miner does, but isn't actually used by anyone professionnally issuing
transactions
trinque: for someone with such unwieldy metaphors, allow me
that one. whether it was an RI was not my point
ben_vulpes: i don't see
the benefits
to
the increase of binary compilation
targets
to 3 from
the one extant.
trinque: does sbcl also not only have
to be able
to interpret / compile common lisp; it must also provide a UI for you
to generate statements in it?
ben_vulpes: davout: what /currently/ compiles as
the single binary "trb"
ben_vulpes: now /that/ i am sold on slicing from
the node.
davout: i'm not really sure whether
transaction signature itself should stay in
trb or be extracted out
ben_vulpes: i am still not sold on moving
the wallet outside of what compiles as "trb"
davout: asciilifeform: if
trb provides sane endpoints
the wallet can be written in whatever floats anyone's boat
davout: wallet
tells you what coin you can spend, you select
the particular outputs, you define
the outputs, it may warn you if
the implied fee is ridiculous but
that's it
davout: the way i see
things,
the "fee estimation" code must die
☟︎ davout: asciilifeform:
to me
there is and remains a difference in kind between "the
thing
that defines what money is" and "the particulars of your personal wallet"