log☇︎
500+ entries in 0.047s
jfw: I mean, I could easily say "use this gpg command and look for this message to verify, then if that succeeds run this patch command", I tested all that, it will work, but I don't perceive it to solve the problem at hand.
jfw: I confess I mostly run 'patch' by hand, but v.pl modified for keccak or any other supporting same should work.
jfw: polarbeard patch which I haven't yet got reground.
mp_en_viaje: man asciilifeform & his gravitating windbag make for SUCH a moron field... what THE FUCK is "centralizing" about http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/comment-page-1/#comment-77 ?
jfw: Um. And ada, sql, patch, lisp, python... ~everything not C-like ?
mp_en_viaje: i guess we'll have to patch bash to recognize it, and that's that.
mp_en_viaje: moreover, how do bitcoin transactions figure into it ? are you talking about "the clearsigning proposal" as in, http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/comment-page-1/#comment-75 ?
ossabot: Logged on 2020-02-04 01:38:36 mircea_popescu: so given bvt's recent and indeed quite shiny work on a new v : is there any interest in actually attempting something like the new clearsign scheme ?
billymg: as for vpatching the server side select mechanism, since mp-wp ships with two base themes a patch could at least be made to include the select mechanism in those. seeing as how most people copy/paste one of the included theme directories to customize/create their own
mp_en_viaje: i practically have the choice of either publishing a screamingly offensive non-patch in november of 2019, or else wait until there's a place to meaningfully add it as a patch ; which necessarily is stalled on "what the fuck is the correct cut for themes, cuz it seems evident it isn't what's now done", which in turn rests on a half dozen or so more nodes that are all further away from what is actually being worked now.
trinque: I've also done some spelunking in the php myself, and there might be other ways to pull it in aside theme, if I can see the patch
trinque: I don't have w/e patch improves the quoting mechanism apparently
mod6: I'll just, withold the patch. Make a blog post. If people want it, I guess they can say.
mp_en_viaje: 0 chances ima deploy some patch you cooked up as things stand right now. also 0 chances ima deploy any patch baked of this "21:02. tried a patch, not worked. 00:12 oh now fixed it. i think" washington post / planeshift "development" model/nonsense.
ossabot: Logged on 2020-02-17 18:32:47 dorion: I'll let him show and tell, his patch removes the whole rotor orchestra since Gales is musl static anyway.
mircea_popescu: http://logs.ossasepia.com/log/trilema/2020-02-17#1958136 << i'd say you got the right idea here, manifest.txt is an add-only buffer, attempts to modify it ~= pirate patch.
dorion: I'll let him show and tell, his patch removes the whole rotor orchestra since Gales is musl static anyway.
dorion: jfw is expecting to finish the offline side of Gales Bitcoin Wallet this week, so his development plate will be clearing a bit. He has an unpublished patch to trb to simplify the build system on Gales, so checking/working with mod6 and getting his patch published could be his next priority. Among other simplifications
ossabot: Logged on 2020-02-04 01:38:36 mircea_popescu: so given bvt's recent and indeed quite shiny work on a new v : is there any interest in actually attempting something like the new clearsign scheme ?
mircea_popescu: so given bvt's recent and indeed quite shiny work on a new v : is there any interest in actually attempting something like the new clearsign scheme ?
ossabot: Logged on 2020-02-03 20:22:10 mod6: All I'm saying, is that without said possible future solution, it may be somewhat difficult to track through 39 different blogs watching for patch submissions all the time.
jfw: perhaps a comment thread on your own blog where someone proposing a patch can "officially submit" it?
mod6: All I'm saying, is that without said possible future solution, it may be somewhat difficult to track through 39 different blogs watching for patch submissions all the time.
jfw: "It puts it on me to chase these down" - this seems to be the core of it; why not leave it to the sponsor(s) of a patch to keep their blogs online & organized enough to find patches (category, code shelf or whatnot)? It's then, what, couple clicks per patch or a wget to import to your own collection - trivial compared to the effort of actually reviewing the patch I'd imagine
mod6: Let me work through these here. Glad you're going to try out a build. Please do let me know how it goes. I did just find three 'gotchas' on CentOS (6.10); whereby 'bison', 'flex' and 'patch' all need to be installed manually. Apparently these are not a part of the default system.
spyked: mircea_popescu, answer'd your comment: http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/comment-page-1/#comment-93 (for now it's in billymg's moderation queue)
ossabot: Logged on 2020-01-21 12:43:04 billymg: spyked: left a response to your comment http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/comment-page-1/#comment-85
billymg: http://logs.ossasepia.com/log/trilema/2020-01-28#1957575 << i'm not sure i follow here. you would need to scroll right to read the line with the regex and then back left to continue downward (since i've already updated the formatting of the patch viewer on my site so that lines now wrap to fit the viewport, here is what i was referring to: http://paste.deedbot.org/?id=p1jb )
jfw: ah, possibly trinque is correct too, the fix got fixed. http://thewhet.net/2019/03/mp-wp-patch-for-enabling-html-comments/
ossabot: Logged on 2020-01-27 10:54:52 billymg: i will go ahead and remove the notion of options from the footnotes plugin and publish the patch for review. going forward i will make more of these calls on my own and let the published draft patches speak for themselves
billymg: i will go ahead and remove the notion of options from the footnotes plugin and publish the patch for review. going forward i will make more of these calls on my own and let the published draft patches speak for themselves
billymg: http://logs.ossasepia.com/log/trilema/2020-01-27#1957400 << i was proposing removal of unnecessary code currently existing in mp-wp, not the addition of any. you can see from my patch history and communications in the logs that the removal of all cruft in mp-wp is what i'm working towards
billymg: mod6: been doing some testing with your privkey_tools patch and afaict everything's working as it should. i applied it manually after pressing the trb stable tree
billymg: spyked: left a response to your comment http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/comment-page-1/#comment-85
ossabot: Logged on 2020-01-19 08:58:25 mircea_popescu: billymg, wouldja handle the moderation incantations for http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/comment-page-1/#comment-84 ; i dun want him to read one without the other.
mircea_popescu: billymg, wouldja handle the moderation incantations for http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/comment-page-1/#comment-84 ; i dun want him to read one without the other.
diana_coman: http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/comment-page-1/#comment-75 - mircea_popescu, I never quite understood why detached sigs for vpatches in the first place; I kind of got the idea that it was so that there is no need for sync on signing (no possible clash of the sort A and B sign independently same thing and then one needs to re-sign so as not to end with 2 versions of same vpatch?)
billymg: mircea_popescu, diana_coman: responded to comments http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/comment-page-1/#comment-76
feedbot: http://billymg.com/2020/01/mp-wp-patch-viewer-and-code-shelf/ << billymg -- MP-WP Patch Viewer and Code Shelf
mp_en_viaje: http://fixpoint.welshcomputing.com/2019/review-of-polarbeard_add_sendrawtransaction_rpcvpatch/ << but anyways, cuteness, jfw discovering the horrors of satoshi bitcoin. most of the insanity you discover in the guy's patch is just carried over.
ossabot: Logged on 2019-12-14 14:05:02 trinque: "While I have striven to make prudent and security-conscious choices, I am not attempting to keep up with the "penetrate and patch" rat-race in its many third-party components." << This is somewhat concerning, in that you say "eh" about the "many third-party components". I'd instead try for the minimal possible bootable src surface area.
trinque: dorion_road: it's more a comment that "why isn't your patch a vpatch atop the gales genesis"
trinque: I don't think you expect to actually be yourselves patching acpica autoconf automake bash bc bison bzip2 cl-hyperspec clisp dash db flex gales-util gcc64 git gnupg less libevent libressl libusb links m4 man-pages man-pages-posix mandoc ncurses nginx ocaml openssh patch pciutils perl php56 py-setuptools python python-docs qmail readline redis sbcl sqlite sqlite-doc tmux ucspi-tcp vim xz zlib
trinque: "While I have striven to make prudent and security-conscious choices, I am not attempting to keep up with the "penetrate and patch" rat-race in its many third-party components." << This is somewhat concerning, in that you say "eh" about the "many third-party components". I'd instead try for the minimal possible bootable src surface area.
ossabot: Logged on 2019-09-14 04:06:31 mircea_popescu: unrelatedly : hey trinque, now that there's actually multiple functional castles the time's prolly come to update the deedbot voice model into awareness of this situation. so how about a patch making voice in #trilema dependent on ~my~ wot, rather than deedbot's own ; and similarily in any castles that ask for it / you come to an understanding with the lords thereof, so they can use the voice model there if the
jfw: I was remembering this phrase but not where from; turns out my own link, hah. Which pretty sure I found via the logs.
ossabot: Logged on 2019-12-01 06:02:16 spyked: http://logs.ossasepia.com/log/trilema/2019-11-30#1953918 <-- fwiw, write-ups usually take me at least an hour. testing's the easy part, except when I encounter weird stuff, which adds another 1-2 hrs on top of those 10 minutes it should take.
spyked: http://logs.ossasepia.com/log/trilema/2019-11-30#1953918 <-- fwiw, write-ups usually take me at least an hour. testing's the easy part, except when I encounter weird stuff, which adds another 1-2 hrs on top of those 10 minutes it should take.
mircea_popescu: im thinking... maybe the best kind of patch available is the one that takes the maker ten minutes to make.
mircea_popescu: incidentally -- there's a divergence in your patch. on the first heading you say and comment_type = '' but on the second heading you say
mircea_popescu: diana_coman, this could be a patch, no ?
diana_coman: I guess so; but I meant it more as in why default in the genesised mpwp; anyways, perhaps billymg makes a patch to take those out of there and to put also trackbacks/pingbacks as last in comments (I've fixed this on my blog only a few days ago but by default they mix in comments too)
ave1: As for current status, I have a big patch file that works as part of the build scripts. So the genesis is feasible. I could also put the build scripts (and other dependencies) in the genesis but this would need to be discussed in light of the OS setup.
diana_coman: fwiw I'd rather go with only c/cpp/ada in genesis and then if someone else wants fortran/whatevers, let them patch it on top.
bvt: ty, i guess after the article it will become possible to decide what to use for each of the hashes; after that one more patch - user-settable key for hashing, and rng work will be done
lobbes: mircea_popescu: nice bug findin'. I'll make sure it is rolled into the patch
ossabot: Logged on 2019-11-07 22:53:05 mircea_popescu: couldja patch this in ?
lobbes: http://logs.ossasepia.com/log/trilema/2019-11-07#1950221 << I don't mind setting out to do so, but I also don't want to delay the bot's deployment (I have found that I am quite slow and inexperienced still). Would you want this patch before deployment?
mircea_popescu: couldja patch this in ?
ossabot: Logged on 2019-11-07 21:31:39 lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-07#1950085 << I guess what I'm trying to ask is do you want me to release a separate mp-wp patch for the xmlrpc.php fixes before we deploy the bot?
lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-07#1950085 << I guess what I'm trying to ask is do you want me to release a separate mp-wp patch for the xmlrpc.php fixes before we deploy the bot?
mircea_popescu: why not just switch to the mp-wp patch ?
lobbes: mircea_popescu: before I commit this fix to a patch, do the excerpts on these comments look saner to you as well? http://blog.ericbenevides.com/2019/11/generic-pingback-target/#comment-134
ossabot: Logged on 2019-11-06 11:37:43 mircea_popescu: and you verified you can actually deploy this proto cuntoo on various hw, so we're good here : as to 1, smg will use proto-cutnoo until can switch to cuntoo ; and meanwhile ima see what trinque has to say re cuntoo and try to get bvt to patch against it and so on
billymg: http://logs.ossasepia.com/log/trilema/2019-11-06#1949939 << nothing major, a minor bug was discovered by several mp-wp users. once it was determined that it was the result of the latest patch i was able to zero in on the offending change and issue a fix plus a test http://billymg.com/2019/11/bug-fix-to-preserve-encoded-html-characters-in-post-body-between-edits/
mircea_popescu: there's also eg http://thetarpit.org/2019/vpl-v-patch-syncing-bug-fix isall this synced ?
mircea_popescu: and you verified you can actually deploy this proto cuntoo on various hw, so we're good here : as to 1, smg will use proto-cutnoo until can switch to cuntoo ; and meanwhile ima see what trinque has to say re cuntoo and try to get bvt to patch against it and so on
mp_en_viaje: diana_coman, the reason i brought it up being specifically "In the past, software development could be done by applying a series of patches to arrive at a final program state. With v, the patch is replaced with the slightly different vpatch, as described below."
BingoBoingo: Outside the parks, there's the occasional patch of fescue or some other real grass that makes for quite the stark contrast.
lobbes: now, just need to do the trackbacks piece and then patch it. Looking on track for deadline
Bingoboingo: And the patch panel
spyked: http://logs.nosuchlabs.com/log/trilema/2019-10-23#1947814 <-- not sure what's gained by this, other than making sure that the mind-boggling weirdness doesn't occur. v.pl init downloads patches and seals, so the verification process still relies on the keys already being there. tho I'll admit, wget -r is not the best
feedbot: http://thetarpit.org/2019/vpl-v-patch-syncing-bug-fix << The Tar Pit -- v.pl V patch syncing bug fix
asciilifeform: hell knows. seems to remove the mutilation tho, w/out breaking anyffin (if anyone sees a breakage from this patch on my www, or remaining mutilated quotes -- plox to write in)
asciilifeform: i'd like to finally patch mine
ericbot: Logged on 2019-10-17 05:09:47 lobbes: I will apply said patch tomorrow and see if that fixes things
lobbes: I will apply said patch tomorrow and see if that fixes things
lobbes: but I think I forgot to re-apply the later hanbot patch for html in comments. Possib. BingoBoingo also forgot.
asciilifeform: BingoBoingo: meanwhile , kindergarten arithm: in machine rack (22u) 1 hole occupied by patch panel (1u), power strip (1u), then will need 1u moar of mains sockets , 1u for switch, 1u for shelf (entrance router, apu's) , 1u asciilifeform will reserve for own www box, leaving 16 holes ; in 1 , rk plant will live. 15 for the courageous among l1 .
asciilifeform: now i also wish that could give working boxes, as easily as patch...
asciilifeform: diana_coman: i made same mistake the other day, was convinced i had made a broken patch
asciilifeform: nuffin catastrophic in that patch, simply cures the single-quotes thing.
lobbes: and neato re: patch. I still need to apply the detect_disconnect patch as well. Will do that tonight before bed
asciilifeform: bot is unaffected by this patch, diana_coman & lobbes can emplace w/out reset .
asciilifeform: baitbot is a working logger btw (on the latest patch). just aint of any practical use, it's a fire magnet is all.
asciilifeform: ( atm the barf you get if you , like asciilifeform , hamhandedly forgot to include a patch in 'patches' , is cryptic )
asciilifeform: hrm i prolly oughta patch vtron so that actually gives detailed barf when encounters an apparently 'martian' antecedent, and for ~all~ such encounters in full list.
asciilifeform: 'detect_disconnect' is a valid patch.
asciilifeform: will make the removal of the broken doublequote thing a separate patch tho.
lobbes: asciilifeform: roger that. I've yet to deploy latest patch anyways, so this'll work out
asciilifeform: meanwhile, diana_coman , lobbes , i'ma have to regrind the latest patch, it is defective (and not simply on acct of the double quotes thing) , apparently in 'a' of diff had wrong copy of MANIFEST .
asciilifeform: if diana_coman or lobbes get to this 1st, i will later sign & mirror the patch .
asciilifeform has internal policy of not regrinding a patch for mistakes in comments; folx oughta read the actual proggy before connecting to live missiles
asciilifeform: 'To disable forced disconnects, set disc_t to zero' is wrong btw. will give actual off switch on next patch.
asciilifeform: i noticed last night that on none of the piz outages did the thing actually realize it's dead. hence this patch.
asciilifeform meanwhile wrote patch for bot to make it actually detect disconnects. is in staging box locally.
lobbes: about to switch over ericbot to new patch; about 30 seconds of downtime
lobbes: http://logs.ericbenevides.com/log/trilema/2019-10-03#1939767 << nifty! I will apply patch later today (submerged in saecular liquishit atm)
asciilifeform: fixed!! in current copy; will cut patch shortly
snsabot: Logged on 2019-10-02 20:35:30 lobbes: wonders if it is worth it in next patch to have bot.py simply parse the MANIFEST.txt for version number emitting