600+ entries in 0.137s
mircea_popescu: billymg, what's the
mp-wp story, did i miss some updates ?
hanbot: lol, it occurs to me...should
mp-wp backend change to reflect post --> article?
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.
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
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 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
lobbes: now, just need to do the trackbacks piece and then patch it. Looking on track for
deadline 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: 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
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.
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: 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: mp_en_viaje lobbes: The comment thing is going to take some digging. Will probably end up pressing
mp-wp again.
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?
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
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: 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
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.
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
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
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)
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