log☇︎
500+ entries in 0.035s
mp_en_viaje: now that said, i'm still thinking about how the fuck to get mp-wp working on two machines best.
pizdi: lobbes: I am MP-WP bot version 598170.
lobbes: To lay it out, my convoluted process last time of getting you the data you needed was: 1) Pulling logs from my Postgres database to a flatfile 2) importing that into mp-wp's MySQL database 3) getting a mysql dump of *that* 4) altering said dump with e.g. sed escapes, etc. then finally 5) I give it to you
feedbot: http://billymg.com/2020/03/mp-wp-roadmap-proposal/ << billymg -- MP-WP Roadmap Proposal
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 ?
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: mp_en_viaje: agree. ugh, yeah, i've really been meaning to publish a roadmap for mp-wp that others can comment on
billymg: at least as an interim until proper theming in mp-wp is solved, just so the correct select mechanism is at least included in the package on first press
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
billymg: http://logs.ossasepia.com/log/trilema/2020-03-01#1958703 << i have a strong feeling the reason it's *not* this, and the reason the mp-wp genesis is 7x the size of trb genesis by LOC, is because it was designed by the "no one user matters more than another" crowd
mp_en_viaje: the whole "theme" thing is iffy, and part and parcel of why this particular tree (mp-wp) is so deeply misbehaving is that it rests upon a large pile of intricate design errors and failures.
diana_coman: trinque: billymg works on mpwp and hosts the full tree afaik.
deedbot: dorion rated billymg 4 << he's doing good mp-wp work, writes at billymg.com
feedbot: http://thetarpit.org/2020/footnote-callback-tooltips-for-mp-wp-thetarpit-markdown-plugin << The Tar Pit -- Footnote callback tooltips for MP-WP thetarpit Markdown plugin
ericbot: Logged on 2020-01-27 13:01:32 mircea_popescu: http://www.krankendenken.com/2020/01/mp-wp-bot-my-current-problem-and-possible-solutions/ << just ditch the shithole host you ran into.
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 ?
mod6: jfw: aside from a possible mp-wp (future) solution to the issue; several clicks notwithstanding, I mearly worry that somehow, the gardener may simply overlook or miss one.
lobbes: if I ever get the mp-wp logger complete.. well it interfaces with the mp-wp database already so theoretically possible to hook that up to what billymg is doing down the road
BingoBoingo: Maybe not all of it, but with the lobbes bot that logs into mp-wp, there's space
BingoBoingo: See http://billymg.com/2020/01/embedded-vpatch-formatting-for-mp-wp-draft-vpatch-for-review/
BingoBoingo: The second biggest problem is that mp-wp is growing, billmg is putting work into making mp-wp do code hosting more cleanly, and the mailman software the mailing list used is an awful, poorly documented thing. If an IRC patchbot is the way to go, hooking it into mp-wp seems like the better direction to go.
spyked: http://logs.ossasepia.com/log/trilema/2020-01-31#1957750 <-- that's been on the to-fix list since I installed mp-wp, I should make it a proper to-do item already
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#1957592 << this was my rationale. from actual testing it proved safe across languages (with only a handful of exceptions in the mp-wp genesis' 162k lines)
mircea_popescu: billymg, in the original example i looked at, line 149 reads : "$footnotes_options['superscript'] = (array_key_exists('superscript', $_POST)) ? true : false;"
billymg: http://logs.ossasepia.com/log/trilema/2020-01-28#1957561 << with this in mind i made some adjustments to the CSS that i think improve the display quite a bit http://billymg.com/2020/01/embedded-vpatch-formatting-for-mp-wp-draft-vpatch-for-review/#S1-L1
ossabot: Logged on 2020-01-28 02:52:39 billymg: btw, when you say "language-aware indentation", do you mean something that would produce a block like http://billymg.com/2020/01/embedded-vpatch-formatting-for-mp-wp-draft-vpatch-for-review/comment-page-1/#S1-L136 ?
billymg: btw, when you say "language-aware indentation", do you mean something that would produce a block like http://billymg.com/2020/01/embedded-vpatch-formatting-for-mp-wp-draft-vpatch-for-review/comment-page-1/#S1-L136 ?
billymg: it's also on my todo list to eventually create a reference theme for mp-wp. this should be an opportunity to better support the code "content type" within the context of a blog
jfw: ah, possibly trinque is correct too, the fix got fixed. http://thewhet.net/2019/03/mp-wp-patch-for-enabling-html-comments/
billymg: hanbot_abroad: if you want to take a look i just published a draft of the vpatch. i think more can be done in terms of cleanup of the old code but i wanted to get some eyes on it before doing another pass
ericbot: Logged on 2020-01-27 13:01:32 mircea_popescu: http://www.krankendenken.com/2020/01/mp-wp-bot-my-current-problem-and-possible-solutions/ << just ditch the shithole host you ran into.
feedbot: http://billymg.com/2020/01/embedded-vpatch-formatting-for-mp-wp-draft-vpatch-for-review/ << billymg -- Embedded vpatch formatting for mp-wp, draft vpatch for review
ossabot: Logged on 2020-01-26 17:59:07 billymg: mircea_popescu: to elaborate: the original version of the footnotes plugin also includes an options.php page for saving db-stored settings. the version that http://btcbase.org/patches/mp-wp_add-footnotes-and-textselectionjs[ships with mp-wp] does not include this
ossabot: Logged on 2020-01-27 08:56:47 mircea_popescu: footnotes plugin original, one, only, etcetera, is the one on mp-wp. what other garbage idiots did is garbage idiots did.
billymg: http://logs.ossasepia.com/log/trilema/2020-01-27#1957403 << and this is the one, in mp-wp, that currently includes code that actively writes options to db. i was proposing to remove any remnants of this completely and only leave what would essentially be some constants at the top of the file (though it sounds like even predefining some of these values at the top of the file is unnecessary and can be removed as well
ossabot: Logged on 2020-01-27 08:55:58 mircea_popescu: http://logs.ossasepia.com/log/trilema/2020-01-26#1957366 << how about your preference immediately becomes working on mp-wp as opposed to falsely claiming to be working on mp-wp while in fact trying to stick random unrelated garbage in there under this guise, because at the rate you're currently going im just about ready to set the bozo bit on whatever it is you do altogether.
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
mircea_popescu: http://www.krankendenken.com/2020/01/mp-wp-bot-my-current-problem-and-possible-solutions/ << just ditch the shithole host you ran into.
ossabot: Logged on 2020-01-26 20:03:18 billymg: anyway i have something simple working, only took a few hours http://billymg.com/downloads/mp-wp-embedded-vpatch-snippets.png
mircea_popescu: footnotes plugin original, one, only, etcetera, is the one on mp-wp. what other garbage idiots did is garbage idiots did.
mircea_popescu: http://logs.ossasepia.com/log/trilema/2020-01-26#1957366 << how about your preference immediately becomes working on mp-wp as opposed to falsely claiming to be working on mp-wp while in fact trying to stick random unrelated garbage in there under this guise, because at the rate you're currently going im just about ready to set the bozo bit on whatever it is you do altogether.
ossabot: Logged on 2020-01-26 17:59:07 billymg: mircea_popescu: to elaborate: the original version of the footnotes plugin also includes an options.php page for saving db-stored settings. the version that http://btcbase.org/patches/mp-wp_add-footnotes-and-textselectionjs[ships with mp-wp] does not include this
mircea_popescu: (but to answer trinque 's original comment : stolen cookies atm not useful on mp-wp because only specified ips can wp-admin anyway)
mircea_popescu: steall all the cookies you want ; and mp-wp can even dispose with the htaccess ip lockdown mechanism currently in place.
mircea_popescu: the way mp-wp session handling should work is as following :
mircea_popescu: http://logs.ossasepia.com/log/trilema/2020-01-26#1957361 << speaking of this in the foregoing context, the way mp-wp's ~only~ cookie works is well ripe for a rewrite.
mircea_popescu: so you know, for having had useful users, mp-wp-footnotes matured. and for the opposite, crystal space not yet.
mircea_popescu: and in general, this is how "offering options" even works : sometimes portions of code function can't be figured out by the writer, has to be figured out by the user. thus things like the eulora gfx engine scriptable parts, or the mp-wp footnote options.
ossabot: Logged on 2020-01-26 17:38:38 billymg: mircea_popescu: do you see any use for UI-set and DB-stored "options" in the footnotes plugin? the version in mp-wp has most of that commented out but it's still storing/referencing them which is causing weird behavior (and makes it so the only way you can override the options is to manually edit the db)
feedbot: http://www.krankendenken.com/2020/01/mp-wp-bot-my-current-problem-and-possible-solutions/ << Krankendenken -- mp-wp bot: my current problem and possible solutions
billymg: anyway i have something simple working, only took a few hours http://billymg.com/downloads/mp-wp-embedded-vpatch-snippets.png
billymg: mircea_popescu: to elaborate: the original version of the footnotes plugin also includes an options.php page for saving db-stored settings. the version that http://btcbase.org/patches/mp-wp_add-footnotes-and-textselectionjs[ships with mp-wp] does not include this
billymg: mircea_popescu: do you see any use for UI-set and DB-stored "options" in the footnotes plugin? the version in mp-wp has most of that commented out but it's still storing/referencing them which is causing weird behavior (and makes it so the only way you can override the options is to manually edit the db)
ossabot: Logged on 2020-01-06 21:50:34 lobbes: http://logs.ericbenevides.com/log/trilema/2020-01-06#1956654 << this week I've commited to getting a Gales install and report complete, however next week I was indeed going to work on the final setup and testing for the mp-wp logger. If all goes well I should be free to give it another shot on around the 20th of this month
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
lobbes: http://logs.ericbenevides.com/log/trilema/2020-01-06#1956654 << this week I've commited to getting a Gales install and report complete, however next week I was indeed going to work on the final setup and testing for the mp-wp logger. If all goes well I should be free to give it another shot on around the 20th of this month
deedbot: diana_coman rated billymg 2 << mp-wp trimming and testing; on the move to CR; writes at http://billymg.com/
diana_coman: mircea_popescu: makes sense; atm though there's still a lot of "posts" all over mp-wp and it's annoying because it makes me trip over and go "post" when I mean article, myeah; a lot of cleaning left to do on that but irc billymg was on it so I shall refrain currently from further trespassing :P
dorion_road: http://logs.ossasepia.com/log/trilema/2019-11-29#1953863 << thanks, I applied diana_coman's fix.
feedbot: http://www.krankendenken.com/2019/12/mp-wp-bot-go-live-open-questions/ << Krankendenken -- MP-WP bot go-live: Open questions
mircea_popescu: meanwhile from the neener department : http://logs.ossasepia.com/log/trilema/2019-11-30#1953933 <-> http://ossasepia.com/2019/11/29/comments-filtering-for-mp-wp/?b=And&e=I#select
feedbot: http://ossasepia.com/2019/11/29/comments-filtering-for-mp-wp/ << Ossa Sepia -- Comments Filtering for MP-WP
ossabot: Logged on 2019-11-28 23:48:45 lobbes: what's left: publish outstanding related vpatches, get base mp-wp and then the bot installed on server, import the remaining logs > 28th march 2016
ossabot: Logged on 2019-11-28 23:48:45 lobbes: what's left: publish outstanding related vpatches, get base mp-wp and then the bot installed on server, import the remaining logs > 28th march 2016
lobbes: what's left: publish outstanding related vpatches, get base mp-wp and then the bot installed on server, import the remaining logs > 28th march 2016
ossabot: Logged on 2019-11-26 19:03:31 lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-26#1953620 << sounds good to me. The mp-wp bot needs to be completed/delivered this week (which I will have some extra time to do so due to upcoming US holidays). Once I get that and the auctionbot work estimation complete, I will propose a deadline for my ebuild 101 homework.
lobbes: and with that, I'm going back to the workbench for said mp-wp bot.
lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-26#1953620 << sounds good to me. The mp-wp bot needs to be completed/delivered this week (which I will have some extra time to do so due to upcoming US holidays). Once I get that and the auctionbot work estimation complete, I will propose a deadline for my ebuild 101 homework.
ericbot: Logged on 2019-11-13 03:01:41 lobbes: I'm aiming to get remainder of mp-wp logger complete in under two weeks. Then rest of Nov I want to tidy up auctionbot. So Dec 1st should be a good starting point for me
ericbot: Logged on 2019-11-13 03:01:41 lobbes: I'm aiming to get remainder of mp-wp logger complete in under two weeks. Then rest of Nov I want to tidy up auctionbot. So Dec 1st should be a good starting point for me
ericbot: Logged on 2019-11-13 03:01:41 lobbes: I'm aiming to get remainder of mp-wp logger complete in under two weeks. Then rest of Nov I want to tidy up auctionbot. So Dec 1st should be a good starting point for me
feedbot: http://www.krankendenken.com/2019/11/notes-on-importing-log-archives-into-mp-wp/ << Krankendenken -- Notes on importing log archives into mp wp
lobbes: mircea_popescu: In trial-by-fire updates, it turns out that mp-wp appears to barf on unicode such as " 😀 "
diana_coman: aha, that auto-complete of mp-wp is very useful indeed.
mircea_popescu found it through the mp-wp process of ossasepia.com/aspa aka "put in the first few letters of title after domain, mp-wp finds for you".
feedbot: http://thetarpit.org/2019/mp-wp-thetarpit-tweaks << The Tar Pit -- MP-WP thetarpit tweaks
mircea_popescu: in other news, i'm considering getting an upgrade for mp-wp, wherein comments marked as spam are displayed for as long as the ip they were made from is loading the page
lobbes: I'm aiming to get remainder of mp-wp logger complete in under two weeks. Then rest of Nov I want to tidy up auctionbot. So Dec 1st should be a good starting point for me
mircea_popescu: the first lol, i'm not dragging the whole mp-wp logger on forever.
mircea_popescu: this is stupid, if mp-wp becomes the de facto platform we'll be stuck with timeless logs. ;/
ossabot: Logged on 2019-11-07 21:31:42 lobbes: just to remind, it was decided that the bot itself would be on the stan logbot tree. And indeed, that is what the current mp-wp-bot.kv.vpatch rests on right now
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: But still, python-istic at the core (which does comply with your original spec).
lobbes: just to remind, it was decided that the bot itself would be on the stan logbot tree. And indeed, that is what the current mp-wp-bot.kv.vpatch rests on right now
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: there he sat, the fuckhead, FOR YEARS, "oh, one day will mp-wp, hurr durr". one day, rite. then, when push came to shove, DID NOT KNOW what didn't know. because hadn't done. because etcetera.
mircea_popescu: why not just switch to the mp-wp patch ?
lobbes is aiming to get the mp-wp bot fix out by tonight. Then needs to get the auctionbot in better shape.
billymg: i'm also optimistic about the additional attention mp-wp seems to be getting over at #ossasepia - jfw has several patches in his queue already http://fixpoint.welshcomputing.com/manifest
ossabot: Logged on 2019-11-06 12:39:33 mircea_popescu: billymg, what's the mp-wp story, did i miss some updates ?
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/