log☇︎
135500+ entries in 1.027s
ascii_field: nah i get to see enough meat shannonizing in real life
shinohai: I saved the hated Ubuntu for last
mircea_popescu: http://log.bitcoin-assets.com/?date=05-08-2015#1225198 << blessfully, i don't think we're short these, by any sort of conceivable measure. nobody has that quality*count. we were however becoming a little short in organizing their effort, but i think that's resolving. ☝︎
mod6: <+ascii_field> mod6: i'm willing to re-create all of mine << ok no rush here. lemme just re-read and think about all of these things for a bit.
mod6: i gotta think about it a bit
mod6: i kinda like what i heard about that earlier.
ascii_field: mod6: i'm willing to re-create all of mine
hanbot: mod6: ;;later tell hanbot ping me when you get a chance plz. thx! << heya, i've got one
mod6: i need to re-read all of the logs from today and have a nice long "think" about it.
ascii_field: mod6: easy. i take mine and sign'em again
mod6: ok forget that im still confused for a moment because im dumb, and maybe I'll just get it in a few minutes...
mod6: I think I need to see a concrete example of this - end to end. I just can't picutre it mentally.
ascii_field: yes, i agree with mircea_popescu re: how patches should embed hash of antecedent file. and imho this solves whatever problem exists (that is, enables it to be solved locally by any participant, in the style he prefers)
ascii_field: colour me thick, but i still don't get where the 'crisis' is
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: <+jurov> mod6 please look at bigget picture, nto jsut to this one step << i think partly ... my general concern is my understanding of how this proposed system would work. this concern is based on the fact that when the current system was proposed, i had the oppertunity to speak out and put in my say in the matter, but I didn't understand it so I don't think I objected very much. and now look at where we are.
punkman: I wouldn't mind something like http://gogs.io/ but too much css I guess
mod6: i guess im just trying to picture in my mind how i would have to use, step by step, the proposed system every single day.
mod6: other than what I already talked about and that's not really better either.
mod6: good question. not sure that i have any useful answers here at this time.
mod6: i'd like to make something better, this is for sure. just whatever it is, i wanna know that it is better, not just sideways.
n6: thanks, I'm going to try and get this to work and come back
mod6: anyway, the main point i wanted to bring up re: clearsigned patches into deedbot was this email: http://thebitcoin.foundation/ml/btc-dev/2015-July/000136.html
n6: I'm already in the wot just have to auth.
ben_vulpes: n6: i understand that this is not a welcome message.
n6: I will try that, thanks.
ben_vulpes: i recommend spinning up an aws gentoo instance. i've given up on macos support for this project.
ben_vulpes: n6 i have no idea, buddy
n6: ben_vulpes: still having an issue getting "bitcoin/src/serialize.h:963:10: error: class member cannot be redeclared" even with your callgraph.sh, what am I missing?
mod6: are you guys following what I'm saying?
mod6: could be scripted i suppose... but just sayin
punkman: I just mentioned it as an easy way to make deeds out of patches
mod6: that's fine, but what if I just wanna look through the submitted patches in deedbot? i now have to do a bunch of extra gyrations to even see the text
mod6: and i thought that was kinda one of the requirements.
trinque: I don't remember
mod6: i've been thinking alot about the ML issues that have been brought up lately. and lastnight I bascially came up with: Mailing list A: for all submissions testing or experimental or otherwise.. Mailing list B: for accepted, signed and released patches, in order. And jurov's /patch.html (or w/e its called) should draw from there.
trinque: was merely saying I am willing to put in the work *should* deedbot- be some part of it
trinque: I gotta depart to a meeting, but to summarize I have no strong opinion that deedbot is the solution
trinque: I could change the thing
mod6: trinque: i think it's awesome :]
trinque: mod6: heh I did the site with a nod to the foundation's
mod6: now, it might be that I'm not exactly understanding what the proceedure for submitting to deed bot would be. but if clearsigned .patch files, that can not work. ☟︎☟︎
mod6: if our idea is to clearsign patches and then submit them to deedbot, i urge you all to review this email and consider why that doesn't work: ☟︎
mod6: i also like how it lines up the signatures to a specific hash horizontally
mod6: and I like the site, and the bitchin motif
mod6: so I've looked at deedbot.org
ascii_field: actually, the best book i have so far is in ru
ascii_field: ben_vulpes: nope, i haven't digitized copies of these. but doesn't hurt to look around
punkman: I'm also tempted to go with Ada 2005 so I can have all teh unicodez
punkman: gernika, my beard being short, I'm looking for something closer to "Ada for dummies"
gernika: punkman - I have the Ada 95 reference manual. Seems thorough. Also you can print out a copy of the GNAT User's Guide at Kinkos - which I've also done. Haven't actually made any progress in reading it but... Seems good by looking at TOC.
punkman: I grabbed a random Ada book last week, it was awful. need to look again
ben_vulpes: punkman: hell if i know
danielpbarron: I also like the idea of a webpage (maybe a wiki) that organizes it all, linking to the deeded content of course
assbot: Logged on 05-08-2015 14:45:46; mircea_popescu: also i'd like to keep this conversation open, for all the folks whose time is not day atm yet.
danielpbarron: http://log.bitcoin-assets.com/?date=05-08-2015#1225757 << i like the deedbot idea; that is submit patches as deeds. The mailing list has stuff i need to decrypt/verify anyway, and I'm not a big fan of email in general ☝︎
punkman: a question that future patch submitters might have: should I patch against last release or most active branch?
danielpbarron: BingoBoingo, I don't recognize those names you mentioned earlier
ben_vulpes: i was hoping you'd contradict my own conclusions, but alas.
punkman: but I'm guessing as to patch order, branches, etc
punkman: ascii_field, I'm doing it
assbot: Logged on 05-08-2015 15:24:59; punkman: I don't want another VCS system. I just need a way to import patches in my existing VCS.
assbot: Logged on 05-08-2015 15:03:16; mircea_popescu: the biggest headache to date for jurov/users of ml seems to have been the mailing itself. i wonder how much sense simply deedbotting messages would make.
ascii_field: http://log.bitcoin-assets.com/?date=05-08-2015#1225798 << how do i embed ~unmutilatable~ binaries in deedbot? uuencode ?!!! ☝︎☟︎
ascii_field: http://log.bitcoin-assets.com/?date=05-08-2015#1225805 << this is what i refer to as 'blackholed' ☝︎
ben_vulpes: http://log.bitcoin-assets.com//?date=05-08-2015#1225499 << i know, apologies all around ☝︎
ben_vulpes: <Adlai> ootb, signed patches. deeding signed patches from darcs is less work than doing so from git etc << how so? i've never touched darcs, the question comes from ignorance.
punkman: I imagine they already have people in those companies, why make it official?
trinque: I mean they all can, but well?
punkman: I don't want another VCS system. I just need a way to import patches in my existing VCS. ☟︎
trinque: I probably missed one, and they also divide into further classifications, ref for example can be a tag, branch, stash
jurov: i am not a git
trinque: no reason I can't add some html nav around that a la dpaste
trinque: to date I've tried to keep it simple, hence the deeds are plain textfiles linked to by a single index
mircea_popescu: jurov i wasn't proposing they be used as is.
shinohai: asciilifeform, mircea_popescu: this is what I get http://dpaste.com/1889469
mircea_popescu: the biggest headache to date for jurov/users of ml seems to have been the mailing itself. i wonder how much sense simply deedbotting messages would make. ☟︎
trinque: and I can modify deedbot- however it helps; he already statically generates his site, perhaps he could interpret metadata in certain deeds and take action
trinque: mircea_popescu | asciilifeform and mod6 and mebbe we have trinque do the graph << I'm in; seems like yet another static site generator job
shinohai: I can see 8333 from ny1.hashbang.sh tho
shinohai: The one I just started has advertised ip
shinohai: Could be I just started this one, the one I am already running returns 28670932
shinohai: Watching tail though I see exactly what asciilifeform describes
asciilifeform: shinohai: this is a persistent problem, and i have every reason to expect that it will get worse.
asciilifeform: i.e.,
mircea_popescu: also i'd like to keep this conversation open, for all the folks whose time is not day atm yet. ☟︎
asciilifeform: i will add, if it isn't obvious, that patches like the one i suggested will apply on a standard unix patch util
jurov: i like it. to be able to remove files without dumping whole contents, patch should be patched, too
diana_coman: it took me half an hour only, but yeah, I did not have to re-read the code or anything
diana_coman: yes jurov, I did verify it, applied it etc
mircea_popescu: and yes, i applied, by hand, compiled, etc.
mircea_popescu: ~I~ applied the diffs.
mircea_popescu: i dunno how you folks understand code otherwise, might be that i'm rusty or inept, but anyway.
mircea_popescu: in fact, if you ask diana_coman, she recently delivered a bot for eulora client, and i had her make me diffs.
mircea_popescu: i didn't care for that.
jurov: i get it
mircea_popescu: i have nfi how come it doesn't exist. must be a switch
asciilifeform: i'm about to post an example
mircea_popescu: jurov i dun see why it would be
asciilifeform: as i understand, any mechanized thing really depends on patches stating their antecedents