Results 1 ... 250 found in trilema for 'mp-wp'
| →
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
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".
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/
mircea_popescu: billymg, what's the mp-wp story, did i miss some updates ?
lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-05#1949577 << I'm sold on 'articles', tho it dun help the cause any that the mp-wp database uses the 'posts' terminology everywhere (posts table, post_id, post_content, etc.)
hanbot: lol, it occurs to me...should mp-wp backend change to reflect post --> article?
feedbot: http://www.krankendenken.com/2019/11/mp-wp-botkvvpatch/ << Krankendenken -- mp-wp-bot.kv.vpatch
diana_coman: mircea_popescu: can I get the random-post-on-landing-page trick that trilema uses? I'm weary of just hacking it into mp-wp atm.
mircea_popescu: i'm all for mp-wp rss style only, tbh.
spyked: http://logs.ossasepia.com/log/trilema/2019-11-02#1949277 <-- guids are currently arbitrary strings tho. mp-wp puts the link in ?p=postid style there iirc.
spyked: http://logs.ossasepia.com/log/trilema/2019-11-02#1949269 <-- hm, I'd keep that distinct from the bot spec (which'd spec bot inputs/outputs and behaviour), but it does bring to light the question of whether feedbot should accept non-mp-wp-style feeds. on one hand I might want to subscribe to heathen feeds on the internets. on the other, the rift is growing anyway (e.g. feedbot doesn't do https), so it's pro
ossabot: (ossasepia) 2019-11-01 spyked: http://logs.ossasepia.com/log/ossasepia/2019-10-31#1008349 <-- ftr, I also stumbled upon this: http://thetarpit.org/2019/a-guide-to-systematically-exploring-the-entrails-of-mp-wp-illustrated-using-some-weird-found-in-the-post-editor . wrapping the input field content in htmlentities did the trick for me, but otherwise I thought this is something particular to my environment
spyked: http://logs.ossasepia.com/log/trilema/2019-11-01#1949218 <-- oh I see. mircea_popescu, this explains the diff between behaviours then. I'm running latest mp-wp press.
spyked: nyways, this sort of thing can be handled on the operator end, e.g. I can temporarily disable feeds on demand and now we know the sort of thing that alters mp-wp rss feeds
mircea_popescu: incidentally : i'm pretty suspicious of something after-i-released it, because ~my~ mp-wp doesn't do the weird thing re chars/encodings spyked & all been comp;laining about.
diana_coman: so it would seem that jfw has actually found a bug with those html chars, except it wasn't in the original mp-wp but in billymg's trimming patches so that should get fixed now.
diana_coman: because yes, I wanted that but never made the time to dig in the mp-wp
diana_coman: there seemed to be a bit more to it from jfw's notes http://fixpoint.welshcomputing.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/?b=omfg&e=wysiwyg%20editor#select
ossabot: Logged on 2019-10-31 21:35:20 lobbes: and in mp-wp bot updates: I've got the thing pretty much complete at this time. Trackbacks-from-IRC still aren't sending 100% of the time, so I need to fix this first. After that I will be doing final code cleanup, testing, and then vpatch. Still truckin' along
lobbes: and in mp-wp bot updates: I've got the thing pretty much complete at this time. Trackbacks-from-IRC still aren't sending 100% of the time, so I need to fix this first. After that I will be doing final code cleanup, testing, and then vpatch. Still truckin' along
ossabot: Logged on 2019-10-16 20:49:54 lobbes: mp_en_viaje: re: mp-wp bot's spitting of the files, do you want some automated cleanup of said directory at every Nth file, or fine to just leave them be? Also, are you fine if they are static php files or is html (with teh embedded php) an absolute must?
lobbes: mp_en_viaje: in mp-wp bot updates: I've got the search results piece (with the auto-delete-old-results functionality) complete.
mp_en_viaje: as it turns out, mp-wp has a ... well, i dunno, i hesitate to call it a bug. it has the following issue : if the publishing of an article (which is itself handled as a http post) gets interrupted for whatever reason (such as the connection dying, the closing packet being waylaid, anything), the article will still be publioshed, partially, ie what made it there ; however because various settings (notably, whether comments etc) ar
feedbot: http://thetarpit.org/2019/decoupling-mp-wp-post-editing-from-the-www-interface << The Tar Pit -- Decoupling MP-WP post editing from the WWW interface
mp_en_viaje: http://logs.ossasepia.com/log/trilema/2019-10-24#1948056 << he's not adding it, you add it, gotta subscribe to the feed. dunno about your own setup but on mp-wp it's something like !1subscribe http://thewhet.net/comments/feed/ or such.
ossabot: Logged on 2019-10-23 11:18:46 asciilifeform: fwiw a mp-wp extension that lets folx 'download these-here patches' imho may be useful. but really ought not to be ~in vtron~ .
BingoBoingo: asciilifeform: iirc the point version your wp split from automattic shit-wp is very close to where mp-wp split from shit-wp.
asciilifeform: fwiw a mp-wp extension that lets folx 'download these-here patches' imho may be useful. but really ought not to be ~in vtron~ .
spyked: when I first looked into it, I found it a little odd myself, since it expects a particular URL structure, e.g. mp-wp/v/{patches,seals}. but then I got used to it and even adjusted my v mirror to match. afaik v.pl is the only vtron that comes with this functionality
BingoBoingo: mp-wp kills em already, and Qntra-wp code hasn't much changed since the cazalla days
BingoBoingo: billymg: Just going to run an mp-wp site?
BingoBoingo: billymg: Sure thing. Just please see http://bingology.net/2019/10/16/reasonable-lamp-setup-for-mp-wp-on-centos-6-and-anyserver-terms-of-use/
feedbot: http://thetarpit.org/2019/the-tar-pit-mp-wp-theme << The Tar Pit -- The Tar Pit MP-WP theme
BingoBoingo: press of current mp-wp for comparison to the one I produce and commit to offering it for download on the main site for your venture in at from at least one page describing the shared hosting offering.
BingoBoingo: hanbot_abroad: Let me know if your use of the LAMP discovers any weird, hard corners, etc. .htaccess for classic mp-wp rules works. No more weird apache 2.4 require statements. Good old allow, deny works
ossabot: Logged on 2019-10-19 00:37:48 lobbes: http://logs.ericbenevides.com/log/trilema/2019-10-18#1946439 << I see no issues with this as long as the bot will have permissions to write files to the 'mp-wp root directory'. I'm not very familiar with the old UY1 mp-wp setup and permissions setup so I couldn't say for sure (I used the rockchip for my bloggin' with piz)
lobbes: in a nutshell, the primary domains of the bot are a) interfacing with IRC b) connecting to a running mp-wp mysql database c) writing (and deleting) files in a sub-directory of the mp-wp install directory
lobbes: http://logs.ericbenevides.com/log/trilema/2019-10-18#1946439 << I see no issues with this as long as the bot will have permissions to write files to the 'mp-wp root directory'. I'm not very familiar with the old UY1 mp-wp setup and permissions setup so I couldn't say for sure (I used the rockchip for my bloggin' with piz)
ossabot: Logged on 2019-10-17 01:44:25 mp_en_viaje: c) you're thinking too cleanly, which is adequate for republican work but inadequate to interfacing work (a point somewhat reminescent of this php discussion). it's the empire of shit for a reason, let it have it.
BingoBoingo: http://bingology.net/2019/10/16/reasonable-lamp-setup-for-mp-wp-on-centos-6-and-anyserver-terms-of-use/ Leaves out the directory structure figuring someone may want to use the instructions for their own use rather than necessarily bringing up a shared machine.
feedbot: http://thetarpit.org/2019/mp-wp-v-patches-markdown-plugin-and-the-tar-pit-lbs-post-importer << The Tar Pit -- MP-WP V patches: Markdown plugin and The Tar Pit LBS post importer
lobbes: http://logs.ericbenevides.com/log/trilema/2019-10-17#1946089 << on initial testing, the re-application of said vpatch seems to have done the trick
BingoBoingo: mp_en_viaje lobbes: The comment thing is going to take some digging. Will probably end up pressing mp-wp again.
lobbes: but I think I forgot to re-apply the later hanbot patch for html in comments. Possib. BingoBoingo also forgot.
lobbes: http://logs.ericbenevides.com/log/trilema/2019-10-17#1946083 << hmm, when I did my recent blog resurrection I used hanbot's mp-wp genesis
mp_en_viaje: in continuing lulz : http://bingology.net/2019/10/16/reasonable-lamp-setup-for-mp-wp-on-centos-6-and-anyserver-terms-of-use/#comment-1385 went through as such, but originally read you break it -- you buy it, which led to stale page.
mp_en_viaje: looks quite like a bug, is it in mp-wp ?
ossabot: Logged on 2019-10-16 20:49:54 lobbes: mp_en_viaje: re: mp-wp bot's spitting of the files, do you want some automated cleanup of said directory at every Nth file, or fine to just leave them be? Also, are you fine if they are static php files or is html (with teh embedded php) an absolute must?
mp_en_viaje: c) you're thinking too cleanly, which is adequate for republican work but inadequate to interfacing work (a point somewhat reminescent of this php discussion). it's the empire of shit for a reason, let it have it.
lobbes: mp_en_viaje: re: mp-wp bot's spitting of the files, do you want some automated cleanup of said directory at every Nth file, or fine to just leave them be? Also, are you fine if they are static php files or is html (with teh embedded php) an absolute must?
feedbot: http://bingology.net/2019/10/16/reasonable-lamp-setup-for-mp-wp-on-centos-6-and-anyserver-terms-of-use/ << Bingology - BingoBoingo's Blog -- Reasonable LAMP Setup For MP-WP On CentOS 6 (And 'anyserver' terms of use)
BingoBoingo: http://bingology.net/2019/10/16/reasonable-lamp-setup-for-mp-wp-on-centos-6-and-anyserver-terms-of-use/ << bvt hanbot nicoleci peterl Please note that anyserver is not the place to put IRC bouncers
feedbot: http://thetarpit.org/2019/a-guide-to-systematically-exploring-the-entrails-of-mp-wp-illustrated-using-some-weird-found-in-the-post-editor << The Tar Pit -- A guide to systematically exploring the entrails of MP-WP, illustrated using some weird found in the post editor
BingoBoingo: Well, the LAMP thing has three moving parts that gotta talk to each other. mp-wp seems happier on apache 2.2 than the 2.4 UY1 had. But, that means cleaning up all sorts of version to version nitpicky breakages.
BingoBoingo: The apache version on anyserver from the 2.2 line which means mp-wp Deny, Allow statements in .htaccess will work as opposed to needing 'Require' statements as per UY1's apache 2.4
spyked: mp_en_viaje, lobbes: re. digging into mp-wp coad, it happens I have an article in the works on exactly that (emerging from the editor weird). /me will try to get it done tomorrow
mp_en_viaje: aaand in other MAJOR http://trilema.com/2018/how-things-have-changed/ developments, http://www.krankendenken.com/2019/10/mp-wp-bot-workplan-now-until-november-3rd/#comment-133 stands like an absolute milestone. there's also a cultural aspect to contend with now!
feedbot: http://www.krankendenken.com/2019/10/mp-wp-bot-workplan-now-until-november-3rd/ << Krankendenken -- mp-wp bot workplan: Now until November 3rd.
ossabot: Logged on 2019-10-05 06:32:26 mp_en_viaje: http://thetarpit.org/posts/y06/0a5-work-plan-vi.html << if you care for w43 suggestions, the one most painfully outstanding mp-wp item is the multi-image uploader.
billymg: BingoBoingo: i took a snapshot of my blog db when piz briefly came back after the unexpected outage, and i have local copies of my patches (i see diana_coman mirrored the mp-wp patches, but i also have the mp-wp-tests patches)
lobbes: turns out, btw, that the whole "detect permalinks structure" thing wasn't even needed... the "guid" field does not represent, as I erroneously thought prior, the absolute path to the post. mp-wp just puts the absolute path in there "by default" as the guid. Saved a lot of time by realizing that
lobbes: in other news, I have knocked out all items in week 4 mp-wp work plan. Next on list is: the search blog portion, and the sending pingbacks from irc portion
lobbes: On that note, I'm off to sew mp-wp bot before we all die of old age
mp_en_viaje: or what, "hey, instead of sucking my toes & finding whores / palaces to hang out with, i'll pay for hotel rooms so you can sit and nerd out, find new hosts, install mp-wps, all that" ?
mp_en_viaje: but you know, first, gotta see lobbes mp-wp combo, THEN
lobbes: mp-wp bot couldn't be a thing without it, for example
lobbes: in that case I will deploy detect_disconnect tonight methinks. The mp-wp bot will probably end up forking from this point in the logotron tree as well
lobbes: since my [blog.lobbesblog.com][main blog] is stuck in the latech mire atm, I will give my unofficial 'mp-wp-bot week 5 workplan' in the logs: I have virtually all of week 4's work complete, save for the piping in of needed values from the mp-wp-config bits, which I may be able to complete tonight.
ossabot: Logged on 2018-10-31 19:16:55 mircea_popescu: http://btcbase.org/log/2018-10-31#1867924 << ikr, multi-upload has been on the wishlist for mp-wp ever since... hey hanbot how long's it been now ?
mp_en_viaje: http://thetarpit.org/posts/y06/0a5-work-plan-vi.html << if you care for w43 suggestions, the one most painfully outstanding mp-wp item is the multi-image uploader.
mp_en_viaje: http://blog.lobbesblog.com/2019/09/mp-wp-bot-work-plan-week-4/#comment-125 << this is not even altogether a meritless issue, "how and when to rationally merge trees"
feedbot: http://blog.lobbesblog.com/2019/09/mp-wp-bot-work-plan-week-4/ << lobbesblog -- mp-wp bot work plan: week 4
spyked: in other news, I'm in the process of standing up a mp-wp for thetarpit and migrating posts from the current platform there. will post a genesis for the current blog later today and then work out a plan for migration
billymg: mircea_popescu: http://billymg.com/2019/09/additional-tests-for-mp-wp-now-according-to-spec/comment-page-1/#comment-50
mircea_popescu: moreover, if that's all you want, you could just add per-para anchors with some tiny tweaking of the mp-wp
snsabot: Logged on 2019-09-26 00:13:24 lobbes: re: two or more mp-wp loggers agreeing with each other; I'm not sure they would ever need to agree with each other in terms of links... IF not indexing. In other words, each instance of a mp-wp logger and its output becomes indistinguishable from any other blog post on said blog. (in other words, if you don't care to sync, or don't care if "missing" lines, then not an issue)
snsabot: Logged on 2019-09-25 22:34:53 billymg: just found it now and read it over, did not know mp-wp trackbacks were broken in this way
lobbes: http://logs.ericbenevides.com/log/trilema/2019-09-26#1938150 << nevertheless, things like this are harder to implement once the concept of dates are thrown out the window
ericbot: Logged on 2019-09-26 00:54:16 mircea_popescu: whereas on trilema you have the whole power of the mp-wp selectylanguage at your disposals, you don't need the line numbers because you can just select w/e actually interests you
lobbes: Now, to revisit upstack, if you are intending to *sync* one mp-wp logger with another mp-wp logger, then I guess you'd run into the same issue as the trad. loggers. I.e. In order to sync you *would* need to index.
lobbes: re: two or more mp-wp loggers agreeing with each other; I'm not sure they would ever need to agree with each other in terms of links... IF not indexing. In other words, each instance of a mp-wp logger and its output becomes indistinguishable from any other blog post on said blog. (in other words, if you don't care to sync, or don't care if "missing" lines, then not an issue)
snsabot: Logged on 2019-09-25 21:41:56 mircea_popescu: consider both the positive (no convergence language'd ever have emerged out of "oh, phf did excellent job with logger") and the negative (without "we have these loggers, how do we sync them" nobody'd have ever understood why mp-wp is a better display mechanism than "this shit i just brewed").
billymg: just found it now and read it over, did not know mp-wp trackbacks were broken in this way
snsabot: Logged on 2019-09-25 21:41:56 mircea_popescu: consider both the positive (no convergence language'd ever have emerged out of "oh, phf did excellent job with logger") and the negative (without "we have these loggers, how do we sync them" nobody'd have ever understood why mp-wp is a better display mechanism than "this shit i just brewed").
snsabot: Logged on 2019-09-25 21:38:22 mircea_popescu: whereas on trilema you have the whole power of the mp-wp selectylanguage at your disposals, you don't need the line numbers because you can just select w/e actually interests you
mircea_popescu: consider both the positive (no convergence language'd ever have emerged out of "oh, phf did excellent job with logger") and the negative (without "we have these loggers, how do we sync them" nobody'd have ever understood why mp-wp is a better display mechanism than "this shit i just brewed").
mircea_popescu: whereas on trilema you have the whole power of the mp-wp selectylanguage at your disposals, you don't need the line numbers because you can just select w/e actually interests you
snsabot: Logged on 2019-09-25 20:12:27 lobbes: hmm this makes me rethink my current design re: mp-wp bot as well. As it stands, there is no way to "re-sync" since it just spits the lines into a blog post.
lobbes: yeah, I'll guess I'll let the man speak to if he wants sync capabilities in the mp-wp-tronic branch
lobbes: hmm this makes me rethink my current design re: mp-wp bot as well. As it stands, there is no way to "re-sync" since it just spits the lines into a blog post.
billymg: i did some reading on pingbacks vs trackbacks and it looks like we could remove trackbacks without anyone noticing (mp-wp supports pingbacks and that seems to be what everyone is using)
billymg: http://billymg.com/2019/09/additional-tests-for-mp-wp-now-according-to-spec/comment-page-1/#comment-49 << mircea_popescu: i now see what you mean about the pingbacks supporting the extra selection parameters but i'm still not sure what is meant by "trashing the whole trilema trackback pile as extant, and having them re-done in the new manner"
feedbot: http://blog.lobbesblog.com/2019/09/mp-wp-bot-work-plan-week-3/ << lobbesblog -- mp-wp bot work plan: week 3
ericbot: Logged on 2019-09-22 16:37:18 lobbes: With that out of the way it has been going smoothly, and I'm mainly making up for lost time now. It would seem I'm on track to hit my deadline though. I will probably have some demo output for mircea_popescu to look at by the end of the day
lobbes: diana_coman: it was productive, at least. Learned things, sharpened skills. Know the logotron code more intimately as well as the mp-wp mysql "guts"
lobbes: asciilifeform: well, mircea_popescu's spec all of the lines are to appear on mp-wp articles (hence, the database piece is the backend for mp-wp, which is mysql)
lobbes: With that out of the way it has been going smoothly, and I'm mainly making up for lost time now. It would seem I'm on track to hit my deadline though. I will probably have some demo output for mircea_popescu to look at by the end of the day
snsabot: Logged on 2019-09-21 23:38:50 lobbes: has been glued to console most of the day; almost has the first chunk of mp-wp-bot functioning (inserting log lines to blog post piece)
snsabot: Logged on 2019-09-21 23:38:50 lobbes: has been glued to console most of the day; almost has the first chunk of mp-wp-bot functioning (inserting log lines to blog post piece)
lobbes has been glued to console most of the day; almost has the first chunk of mp-wp-bot functioning (inserting log lines to blog post piece)
lobbes coincidentally saw that key a few hours ago while grabbing your main key for a mp-wp install for testing
feedbot: http://blog.lobbesblog.com/2019/09/mp-wp-bot-work-plan-week-2/ << lobbesblog -- mp-wp bot work plan: week 2
diana_coman: mircea_popescu: in comments at http://blog.lobbesblog.com/2019/09/the-mp-wp-bot-job-offer/
lobbes: In other news, I wish this mp-wp-bot already existed. I've been trying to locate a Trilema piece for this post I'm working on, and I must've gone through a few dozen by now with no luck.
lobbes: How's this: I'm going to begin by attacking Thing 2 in this comment (grr the new server-side selection does not work for comments it seems?), after which I should have more info on my ability and the time it should take. I can give you a better estimate then I hope
mircea_popescu: http://logs.nosuchlabs.com/log/trilema/2019-09-10#1935373 << ayup. and the svg-ing of mp-wp and so on
snsabot: Logged on 2019-09-09 20:14:25 lobbes: http://logs.nosuchlabs.com/log/trilema/2019-09-09#1935281 << bvt, would you be able to produce the vpatch? I would, but a) my knowledge of tcp stack / kernels / etc. is pretty much nil and b) I'm gearing up to focus 100% on mircea_popescu's latest mp-wp bot ask if I end up winning this auction.
lobbes: http://logs.nosuchlabs.com/log/trilema/2019-09-09#1935281 << bvt, would you be able to produce the vpatch? I would, but a) my knowledge of tcp stack / kernels / etc. is pretty much nil and b) I'm gearing up to focus 100% on mircea_popescu's latest mp-wp bot ask if I end up winning this auction.
feedbot: http://blog.lobbesblog.com/2019/09/the-mp-wp-bot-job-offer/ << lobbesblog -- The mp-wp bot job offer
billymg: without going into too much detail my current mp-wp roadmap is: 1) finish writing tests, 2) mass delete cruft/unnecessary "features", 3) formalize a republican theme (or a few themes)
ossabot: Logged on 2019-09-06 04:37:22 spyked: http://logs.ossasepia.com/log/trilema/2019-09-04#1933694 <-- ftr, I'm pretty sure that the same coat can be applied to mp-wp without much effort. so if e.g. billymg is interested, I can provide him with everything he needs; tho the blog is online already, not especially difficult to see how the webpage is structured.
snsabot: Logged on 2019-09-07 04:57:27 mircea_popescu: the line where it was mentioned as text and the url to the logotron ; and c) deploys this to pizarro box (should be getting one presently i'm understanding) -- this step will also include putting a trilema clone in there (i'll provide the mp-wp install/db dumb, all that's needed is a mysql glue such that local myql server slaves trilema.com mysql server ; i intend to make a one line edit to the forms, such that comments le
mircea_popescu: (perfectly acceptable for logger part of bot to consist of simply updating article in mpwp-posts, tagged as "logs" category, have one for each day. mp-wp will do the rest.)
mircea_popescu: the line where it was mentioned as text and the url to the logotron ; and c) deploys this to pizarro box (should be getting one presently i'm understanding) -- this step will also include putting a trilema clone in there (i'll provide the mp-wp install/db dumb, all that's needed is a mysql glue such that local myql server slaves trilema.com mysql server ; i intend to make a one line edit to the forms, such that comments le
snsabot: Logged on 2019-09-06 04:34:33 spyked: magemagick (what I believe mp-wp uses currently?) or gimp batch processer; regardless of what is to be used, the tools *are already there*, it's the user's problem how or what he uses. I for one don't wanna use web interface for photo processing, nor did I ever intend to add this to thetarpit, nor would I stop anyone from adding them if they wish
spyked: http://logs.ossasepia.com/log/trilema/2019-09-06#1934014 <-- more along the lines of: convert from thetarpit-format to mp-wp-format so that paragraphs, photos etc. display properly; it's not a big deal, but I expect there are a few unknowns that might require manually walking the article list. which isn't *that* big, but still.
ossabot: Logged on 2019-09-05 18:04:58 mircea_popescu: spyked, "the painstaking labour involved in moving every post to MP-WP (plus fixing the links) would take a yet-to-be-determined amount of time" << why is this to be a pain ?
snsabot: Logged on 2019-09-06 04:25:25 spyked: http://logs.ossasepia.com/log/trilema/2019-09-05#1933930 <-- eh, when I first wrote the blog, I chose "markdown" as markup, so now would have to write some extra code to take the generated html content and add it to mp-wp db; problem is, there's the manual step of verifying that the resulting content looks okay, and e.g. the photoblog posts use thetarpit-specific css.
mircea_popescu: http://logs.nosuchlabs.com/log/trilema/2019-09-06#1933996 << for all the whining re php, one thing mp-wp most definitely does right is that it separates the article from the mark-up
spyked: magemagick (what I believe mp-wp uses currently?) or gimp batch processer; regardless of what is to be used, the tools *are already there*, it's the user's problem how or what he uses. I for one don't wanna use web interface for photo processing, nor did I ever intend to add this to thetarpit, nor would I stop anyone from adding them if they wish
ossabot: Logged on 2019-09-05 18:04:58 mircea_popescu: spyked, "the painstaking labour involved in moving every post to MP-WP (plus fixing the links) would take a yet-to-be-determined amount of time" << why is this to be a pain ?
spyked: http://logs.ossasepia.com/log/trilema/2019-09-05#1933930 <-- eh, when I first wrote the blog, I chose "markdown" as markup, so now would have to write some extra code to take the generated html content and add it to mp-wp db; problem is, there's the manual step of verifying that the resulting content looks okay, and e.g. the photoblog posts use thetarpit-specific css.
spyked: http://logs.ossasepia.com/log/trilema/2019-09-04#1933694 <-- ftr, I'm pretty sure that the same coat can be applied to mp-wp without much effort. so if e.g. billymg is interested, I can provide him with everything he needs; tho the blog is online already, not especially difficult to see how the webpage is structured.
mircea_popescu: spyked, "the painstaking labour involved in moving every post to MP-WP (plus fixing the links) would take a yet-to-be-determined amount of time" << why is this to be a pain ?
mircea_popescu: BingoBoingo, afaik mp-wp takes postgres out of the box
feedbot: http://billymg.com/2019/09/additional-tests-for-mp-wp-now-according-to-spec/ << billymg -- Additional tests for mp-wp, now according to spec
snsabot: Logged on 2019-08-30 06:59:30 mp_en_viaje: trying to maybe gwt out of it, hence the work to spec "blog" in the abstract ; but mp-wp stack works for trilema TODAY ; i ain't taking a break from publishing untul "better world". god knows the week long #trilema outage was long enough.
mp_en_viaje: trying to maybe gwt out of it, hence the work to spec "blog" in the abstract ; but mp-wp stack works for trilema TODAY ; i ain't taking a break from publishing untul "better world". god knows the week long #trilema outage was long enough.
diana_coman: re logger atm I am undecided as my options so far seem to be: 1. do another round of madness with flask until it works on this old (but stable at least) centos 2. replicate environment aka burn down centos and have fun installing remotely on the machine cuntoo 3. simply run irssi (as I'm otherwise running this code anyway as my client) with logging to db into an mp-wp database and be done with it (possibly each line a one comment - will end
snsabot: Logged on 2019-08-23 12:34:46 spyked: asciilifeform, IMHO the custom markup idea for new blogotron ain't bad, but it might piss off ppl used to mp-wp, who still use ye olde html tags. I'm curious to hear opinions, given that I'm working on this exact thing for thetarpit
spyked: asciilifeform, IMHO the custom markup idea for new blogotron ain't bad, but it might piss off ppl used to mp-wp, who still use ye olde html tags. I'm curious to hear opinions, given that I'm working on this exact thing for thetarpit
diana_coman: I suspect he just missed that/did not update his local mp-wp, that's all
mircea_popescu: im not re-debugging this, spent a day year-or-so ago on it, i expect the resuklts to be in the mp-wp tree!
diana_coman: mircea_popescu: I do; and a few other bits that are on the list to change but on which I kept thinking "there will be a mp-wp theme" and then can tweak; hm, who was it, billymg ?
mp_en_viaje: this is kinda-sorta where my "add logger to mp-wp pages" thing goes towards. conceivably one could have a reconcillation process as part of one's blog
billymg: mp_en_viaje: responded to your comment on the tester post http://billymg.com/2019/08/mp-wp-automated-testing-proposal-and-vpatch/comment-page-1/#comment-33
snsabot: Logged on 2019-08-09 01:57:33 billymg: ^ i put together a quick POC for e2e testing on mp-wp. i have to sign off for the night and will be away from my main machine this weekend but will be checking the logs/comments if anyone has any feedback
mircea_popescu: someone can then configure a local ~eater~ (taking, eg, bot cvs dumps) and have the logs (of w/e chan interests them) directly on their mp-wp. which means -- including the selection thing etc.
mircea_popescu: incidentally, lobbes or billymg i guess -- if either of you feel like futzing with it, having a logger bot that spits out days formatted for mp-wp into MPWP_posts table formatted into a category so one can just plug that into their blog will prolly be fantastic.
billymg: ^ i put together a quick POC for e2e testing on mp-wp. i have to sign off for the night and will be away from my main machine this weekend but will be checking the logs/comments if anyone has any feedback
feedbot: http://billymg.com/2019/08/mp-wp-automated-testing-proposal-and-vpatch/ << billymg -- MP-WP Automated Testing Proposal and VPatch
diana_coman: BingoBoingo: done and indeed this way it works; I wasn't aware of this bug in mp-wp though
BingoBoingo: diana_coman: This is odd. I an unsure how or why mp-wp tries to paginate comments. Will try to see if I can uncover anything.
diana_coman: BingoBoingo: the comments links seem broken on younghands.club; is there more weirdness with the mp-wp install? e.g. http://younghands.club/2019/07/28/week-2-progress-summary-3/ links to http://younghands.club/2019/07/28/week-2-progress-summary-3/comment-page-/#comment-4 that 404s
feedbot: http://trilema.com/2019/how-to-restructure-the-categories-of-articles-on-mp-wp/ << Trilema -- How to restructure the categories of articles on MP-WP
BingoBoingo: diana_coman: I'll get to pressing an updated mp-wp
diana_coman: BingoBoingo: the mp-wp on younghands.club seems to be still stripping all tags; is it deployed without the patch or what?
mp_en_viaje: diana_coman, alternatively, you set up a mp-wp on postgres.
|
→