427400+ entries in 0.265s
mircea_popescu: asciilifeform some nodes may be like
that, but it's necessarily going
to be
the exception not
the rule
shinohai: My
thoughts as well. I'll
throw up a webserver or stuff like
that on
there. But
those sorts of postings are a big nope for me.
shinohai: Some idiot on jobs4bitcoin. Some days
the requests baffle me.
shinohai: nm,
they arent
the connections I specified.
shinohai: asciilifeform: with
the pogo binary from
the mailing list I got 3 connections xD
shinohai: I just commented out my addnode/connect jazz just
to run for now :/
trinque: I'm saying one setting for "serve blocks
to others" and another for which nodes
to connect
to
trinque: is
this just stupid behavior entirely re: connect?
shinohai: I was about
to say ... ive been using -connect only for weeks
trinque: needs something akin
to connect but with multiple, right?
mircea_popescu: asciilifeform [...] microhammer << was just an early suggestion, no one's married
to it.
assbot: Logged on 04-08-2015 21:50:14; ascii_field: danielpbarron: he was a relatively early 'computer sucks and must be rebuilt' person. sadly, i've no idea what he is up
to
these days.
mircea_popescu: jurov ie, like being in procust's bed, crushed by a giant
to fit.
assbot: Peripateticists, kinda, except girls not boys, bare cunt instead of
toga and walking around
the house not
the garden, but otherwise exactly
the same. on
Trilema - A blog by Mircea Popescu. ... (
http://bit.ly/1Iqucbd )
ascii_field: 'In my village in Zimbabwe, surrounded by wildlife conservation areas, no lion has ever been beloved, or granted an affectionate nickname.
They are objects of
terror.'
ascii_field: i can confirm, ~proper~
toilets have been rare and collectible in usaschwitz, since '90s
ascii_field: 'If
the regulators really do get
their way, functioning dishwashers could become like high-flow
toilets: contraband
to be snuck across borders and sold at a high black market prices.'
ascii_field: 'Welcome
to regulated America, where once fabulous consumer inventions like refrigerators, freezers, washing machines, and dishwashers have been reduced
to a barely functioning state.
The reasons are always
the same: 1) phosphorous-free detergent, 2) a fetish with saving water, 3) weaker motors
that use less electricity, 4) more
tepid water due
to low default settings on hot water heaters, and 5) reduced water pressure in
☟︎ mod6: well and probably error prone if he/she has
to cut
the upper
text out just
to get down
to "bare" patch
to re-clearsign and submit
to deedbot... could miss line, something bad.
mod6: that would be
the way
to do it as I said earlier. but not sure if
that's really feasable.
mod6: but
then you could just have detached sigs?
jurov: having an option
to
tell deedbot "present
these
together on one page" should suffice
ascii_field: throw hashes in deedbot, sure. or even uuencodes. but
to make it a canonical repository of anything else, is a microscope-hammer.
mod6: im not ciked about
that either.
ascii_field: but for
the record i
think
this 'cram all in one file'
thing is braindamaged.
ascii_field: throw message prior
to
the first 'diff ....' in
the ,patch
jurov: or otherwise suggest
to deedbot
they're related
mod6: ok so another question i have about
the deedbot way.. would be: if we submit a patch
to deedbot, how do we
tie a message
to
that same submission? say we wanna be like "Hey,
this
thing is neat!" Will it need
to reference anothe deedbot submission or does
the patch have
to come after our statment in
the clearsigned message?
mod6: had
to look
that up.
mod6: was gonna say. "how does
that makes sense?!"
mod6: oh actually, im wrong about
that.
mod6: main difference seems
to be... we would now need
to enter our password every
time
to verify
the signature as opposed
to just --verify
mod6: <+jurov> mod6 decrypt on *clearsigned* file <<
this indeed works. created file A.txt. copied A.txt
to B.txt and subtracted some lines. created a unified diff of both. clearsigned
the diff -- which is mutilated for escaped hyphens. upon `gpg --decrypt` of
the clearsigned output patch file, i get
the same hash as
the pre-clearsigned hash file.
mircea_popescu: pruning
the
tree of all ulteriors
that depend on an unclicked patch
mircea_popescu: and opbvciously, with a checkbox "allow
this antecedent"
mod6: <+mircea_popescu> already sounds like a quantum leap
tbh << it is.
mircea_popescu: i knew
this was a
tooling problem mostly. pretty much 99% of all
that's needed is already here.
mod6: <+mircea_popescu> mod6 ^ give
that a long
think. << i like
this idea with
the wot graph + source patches as a
tree next
to it so relations can be easily seen & drilled into.
ascii_field: first needs
the chicken, err,
the embedded antecedent indicators
mircea_popescu: trinque and with a bonus "click here for
this patch" and "click here for
this patch + all its antecedents" spew.
ascii_field: (when i said 'graph walker' earlier
today)
mircea_popescu: so basically ml as restateds + grapher in
the sense of
the above, svg (clickable) is really
the definitive word on
this ?
jurov: can enlist
trinque or anyone's help with graphics
mircea_popescu: have all
the wot listed on
the side. have all
the patches AS A
TREE listed next
to it. have relations from wot
tyo patches.
ascii_field: mircea_popescu:
to be clear,
that is precisely what i had in mind when suggested
the hash embed
thing
mircea_popescu: tbh an equivalent of
the callgraph / mike's wot graph but for PATCHES would not be amiss.
assbot: Logged on 05-08-2015 19:20:55; mod6: so before I say "yup,
that's it,
that's
the
thing
that gets us
to where we want
to be", i want
to fully understand what I'm agreeing
to use.
jurov: will spew out
the original
ascii_field: and i was
trying
to explain
that
this is deeply broken
assbot: Logged on 05-08-2015 19:20:55; mod6: so before I say "yup,
that's it,
that's
the
thing
that gets us
to where we want
to be", i want
to fully understand what I'm agreeing
to use.
mod6: ah, encrypt/decrypt, but we want clearsign or am i misunderstanding
this?
jurov: as with xorg buffer, i'm curious, will see if anyone submits something with valid sig
that gpg fails
to unescape.
ascii_field: that's because
the output of 'encrypt' is a base64
turd
that isn't expected
to coexist with
text
the way a clearsigned string is.
mod6: and honestly,
this is no poor reflection on deedbot.
the
thing is cool.
mircea_popescu: i just
tried
this... it doesn't mutilate on encrypt/decrypt
mod6: i guess for me
thats
the one big
thing, we can't have any mutilation of
the patch files. or we'll just find ourselves banging our heads all
the
time.
mod6: ok
then we're settled.
jurov: sender will have
to resend with detached sig
jurov: well, if gpg can't undo it and it causes
the patch
to fail...then it fails.
mod6: ascii_field: so does `gpg --decrypt` work for
that as danielpbarron & jurov said?
ascii_field: the 'escape' operation is
thermodynamically lossy.