4200+ entries in 0.241s
trinque: !s
deedbot.org/genbootstrap
punkman: trinque should make
deedbot accept signed colours which assbot will use to colour the logs!
trinque: kakobrekla: pls to cname deeds.bitcoin-assets.org to
deedbot.org ?
trinque: hey, btw. if someone cnames deeds.bitcoin-assets.com to
deedbot.org I'll make that link in the declaration work again.
shinohai: guvment efficiency. Notarize with
deedbot or something.
King_Rex: lurker, very interested in
deedbot and the bitcoin foundation and your node efforts
shinohai: trinque: does
deedbot run on limnoria ?
trinque: Adlai | trinque: where exactly is
deedbot-'s source? << on my laptop and a server, no shithub to be found
Adlai: trinque: where exactly is
deedbot-'s source?
mod6: on the other side of the coin, if we do something like this with
deedbot, we need to ensure a mirror is always available.
mod6: so i guess all in all, the
deedbot solution, if it can be created, seems better than my initial proposal of 2 mailing lists; one for everything, one for patches accepted only. which seems simple as well, but now we have to manage two lists.
mod6: that way it sort of also solves the problem of keeping track of who signed which patch. since
deedbot stores these sigs in a horizontal fashion next to the address.
mod6: but what if we then, say, at the end of a testing/release cycle were to (instead of signing or as well as posting to the mailing list) post the plaintext patch and a detach signature from the originating author, myself & ben to
deedbot as a perm storage for these patches?
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.
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.
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: and honestly, this is no poor reflection on
deedbot. the thing is cool.
mircea_popescu: if it stays as a ml, becomes a wiki, somehow otherwise including
deedbot or not changes i do not care per se
assbot: Logged on 05-08-2015 18:54:25; 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:
mircea_popescu: mike_c anyway ima link to
deedbot just as soon as it pops.
jurov: yes that one is solved. but
deedbot can be used only if clearsigned and without any accompanying text
mod6: it still doesn't help me view a base64 encoded submission to the
deedbot danielpbarron:
deedbot isn't where you go to read it all; it's where you go to verify it all
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
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
mod6: will
deedbot take 2 parameters, a non-signed .patch file and a detached signature and somehow colese them?
trinque: mod6: as for how
deedbot- might be used, not clearly defined yet
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: so I've looked at
deedbot.org
trinque: and then maybe
deedbot farts out additional nav controls on the html versions of these interesting deeds with a particular sexp in them
trinque: you could implement the data structures needed for VCS atop
deedbot in a similar manner
jurov: email was chosed because it allows for structured text + attachments. not sure how to do it with
deedbot jurov: mircea_popescu:
deedbot has currently even less friendly archives than mailman
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
mircea_popescu: jurov what if the only way to add an edit is "
deedbot pastebin/soandso" ?
mircea_popescu: in practice, it'd prolly be more practical to transition
deedbot and its site to this job i think
BingoBoingo entered into
deedbot that condemnation for more than just "there exists" a misdemeanor charge
BingoBoingo notes filings issued in venues other than a #b-a
deedbot will from now and from twenty years in the past be treated as suggestions rather than orders.
decimation: trinque: a web page with links to whatever
deedbot spits would be sufficient
shinohai: Sorry, I just discovered
deedbot doesnt like pms
shinohai: ;;later tell trinque am i doing something wrong, or is
deedbot down?
trinque: I'll say writing
deedbot- was highly instructive.
trinque: unimpressed, and he wrote the bot I based
deedbot- on
hanbot: trinque ya but said ml67 pulls in from sourceforge, whaddamigonnado.
deedbot would be great
trinque: I can put my copies of the distfiles on
deedbot.org
trinque: could just
deedbot your resume and announce here, though
trinque: mats: time for me to switch
deedbot- to the next tank :)
assbot: Logged on 29-07-2015 04:13:52; mats:
deedbot-: dpaste.com/3QCXX90.txt
mats:
deedbot-: dpaste.com/3QCXX90.txt
☟︎