log☇︎
427700+ entries in 0.259s
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)
jurov: so you still not understand what's this all about?
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
jurov: or if someone come up with less turdy format than MIME
jurov: maybe we end up all using a script to put the package together and sign it.. but in this case it can just output an email message to be just fed to sendmail
mod6: and if those proposed steps are easier/better than what we currently hvae.
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.
jurov: question is, how to do this all better?
jurov: and metadata what the patch applies on
jurov: turdatron needs to take bundles of patch + manifest (at least, can be any other files aside from patches)
punkman: 30 pages in, "Ada for Software Engineers", the code examples look gnarly
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.
jurov: mod6 please look at bigget picture, nto jsut to this one step
n6: thanks, I'm going to try and get this to work and come back
mod6: jurov: to me thats an extra step... is that what we're all prepared to live with?
mod6: s/tries to//
mod6: gnupg tries to escape lines that begin with a dash
mod6: as you can see clearsign mangles the text: - --- a/rotor.sh .... - -../dist/configure
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
assbot: Trust relationship from user ben_vulpes to user n6: Level 1: 0, Level 2: 0 via 0 connections. |http://www.btcalpha.com/wot/trust/?from=ben_vulpes&to=n6 | http://www.btcalpha.com/wot/user/n6/
n6: I'm already in the wot just have to auth.
n6: ben_vulpes: what more welcoming then support for free?
ben_vulpes: n6: d'you plan to get into the wot as well?
mod6: it still doesn't help me view a base64 encoded submission to the deedbot
mod6: and /patch.html imho should not draw off of just any submission, only signed submissions from ben, myself and the author.
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.
mod6: punkman: <+mod6> <+ben_vulpes> there's always /patches.html... << sure if it's readable. <+mod6> what about for unsigned new submissions?
mod6: punkman: taking it back to the earlier premise.
mod6: and there are 75`000 people and 50 submissions per day?
mod6: <+ben_vulpes> there's always /patches.html... << sure if it's readable.
danielpbarron: deedbot isn't where you go to read it all; it's where you go to verify it all
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
ben_vulpes: mod6: not that my browser will do anything with the patch files but download them.
mod6: "easy to read"
mod6: and i thought that was kinda one of the requirements.
ben_vulpes: n6: all of my noodling on the topic resides at http://cascadianhacker.com/bitcoin/callgraph/
mod6: see, we could uu encode stuff or gzip stuff or do any number of things, but then it's far less readable "as-is"
danielpbarron: what about this: gzip the patch and clearsign that
punkman: yeah it's a base64 blob that includes file and signature when you --sign --armor
assbot: Logged on 15-07-2015 19:25:10; solrodar: http://178.62.64.22/dot-filter.py << instructions at top
trinque: and then yeah decrypt on the other end
mod6: danielpbarron: we're not talking about encryed docs
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.
ben_vulpes: we're just exploring the possibility space here
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
ascii_field: deedbot as adjunct to ml - works
mod6: ascii_field: im simply referring to the converstaion from this morning
ascii_field: even worse, imho, in every respect, than ml
trinque: thought gpg could wad a sig and a file together in other ways than clearsign
ascii_field: who thought this was a good idea, and why ☟︎
mod6: will deedbot take 2 parameters, a non-signed .patch file and a detached signature and somehow colese them?
trinque: I could change the thing
trinque: does it have to be clear?
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
ascii_field: like talmud.
punkman: "Like any contract, the Ada Referebce Manual is written in very precise language, and the term ‘language lawyer’ is often used for people who are experts at interpreting the document."
ascii_field: written by, of all people, fella claiming to be former lead programmer of ukraine central bank...
ascii_field: actually, the best book i have so far is in ru
ascii_field: anyone seriously into the subject will also want the 'standard' and 'rationale' documents.
ascii_field: ben_vulpes: nope, i haven't digitized copies of these. but doesn't hurt to look around
ascii_field: 'Ada 95: The Lovelace Tutorial.' David A. Wheeler << probably the most n00bish
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"
mod6: ;;later tell hanbot ping me when you get a chance plz. thx!
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
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: http://therealbitcoin.org/ml/btc-dev/2015-August/000144.html this won't truncate your debug.log unless you tell it to
ben_vulpes: what was the rollover patch called?
ascii_field: if wrong about this, will have to merge by hand, and there is no going around this
ascii_field: punkman: depends on who you think is 'longest chain'
punkman: a question that future patch submitters might have: should I patch against last release or most active branch?
BingoBoingo: It's for the best
danielpbarron: BingoBoingo, I don't recognize those names you mentioned earlier
assbot: [bitcoin-dev] "A Transaction Fee Market Exists Without a BlockSize Limit"--new research paper suggests ... ( http://bit.ly/1OQSsXP )
ben_vulpes: let me restart the thing and grab the whole bootup log for inspection
ascii_field: ben_vulpes: the debug.log fragment you pasted does not reveal the cause of your jam
assbot: For His Next Trick, Barefoot Genius Aims to End Broker Rip-Offs - Bloomberg Business ... ( http://bit.ly/1OQRv1Q )
punkman: but I'm guessing as to patch order, branches, etc
BingoBoingo: ;;later tell pete_dushenski You should see it when the DDoS abates
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.
ascii_field: http://log.bitcoin-assets.com/?date=05-08-2015#1225833 << can do this now! ☝︎
ascii_field: if someone was wondering how the system could ever be made ~less~ n00b-friendly - this'd be it..
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.