1. I use it quite a bit for marking up an article (including footnotes), as well as approving comments, and managing categories.

2. Usually when I move my blog to a new server I end up having to edit a few records in the [prefix]options table (via mysql CLI); the 'siteurl' and 'home' options.

I also have futzed with various settings via the web UI; usually things like the permalink structure and the various options in the "Reading Settings".

3. The only plugin I use is the footnotes plugin.

4. Yes, I've modified the "WordPress_Default" theme. Mainly just changes to the formatting and layout.

5. I altered the archives to show titles only.

6. I tend to start writing and save my initial draft as just a plain text file on my local machine. Then
once I get enough written I tend to move it to mp-wp.

As far as images go, I've never actually used the upload feature in mp-wp. I usually just resize them in bulk (I use imagemagick) and then upload them directly via scp.

7. I really hate wrestling with php and mysql conflicts and the various dependency issues that go along with it every time I migrate my blog to a new server environment (if the OS version doesn't change then there's no issue, of course). Most of the other pieces I can automate, but getting the LAMP ready for mp-wp is always a roll of the dice on how much time it will take.

8. I like the potential for blog interconnectivity, specifically if pingbacks (trackbacks?) were sent 100% of the time (I still don't know why it doesn't always send them, though I did have the pleasure of poking around at the xmlrpc.php at one point and there seems to be tons of duck tape and hacks on top of hacks). But even right now it functions pretty well for blog to blog communication.

1. Do you use the mp-wp admin interface (web UI)? If so, what actions do you perform via this interface?

Yes, albeit rarely. I use it mainly to publish articles and to maintain the comment moderation queue.

2. Have you modified any of the "settings" in the mp-wp mysql database (also found in the web UI under "Settings" in the left-hand nav)? If so, which ones? When/how often? Via mysql CLI or via the web UI?

Yes, the blog title, URL, author name etc. I modified those once via the web UI, when I set up MP-WP.

3. Do you run any custom plugins on top of what's included in the trunk of mp-wp?

Yes, the Markdown plugin. It replaces the footnotes plugin, even.

4. Have you modified an included theme or created a new theme that you actively use on one of your sites/properties? If so, why / what did you modify?

Yes, I created The Tar Pit theme.

5. Do you run mp-wp with any other code modifications (outside of themes and plugins)? If so, why / what did you modify?

I've done some tweaking here and there. More importantly (for myself, at least), I loathe using the web interface for writing and editing, so I wrote my own interface into the post editor.

6. Describe your typical workflow when publishing an article to your blog (including any pre/post steps, and any other tools/scripts/etc. outside of mp-wp). Include details about working with images, code samples, etc.

It sorta goes like this:

a. initial writing and proofing occurs in whatever text editor my system has available; then

b. I use the scripts linked above to create a post, add it to the MP-WP database etc.; then

c. I do a round of review on the MP-WP draft, after which I publish it.

For code samples, tables and footnotes, the Markdown plugin does more than a decent job; this is incidentally why I decided to import it when I set up the blog, I had too much relying on it already and this stuff was working for me in the first place, so why not keep it.

I upload my files on the box using SSH, I've never used the web interface for that. In particular, as far as photos are concerned, I process all of them outside of MP-WP using GIMP or whatever, then I upload them as described.

7. What do you find most tedious or annoying about using mp-wp? (can be related to any aspect of using mp-wp)

The lack of a CLI/TUI. I noticed other people are using MySQL as a drop-in replacement for that, somehow I never bothered, which is how I ended up hooking up directly in the MP-WP API functions. Now, that Wordpress comes with some pretty weird ad-hoc abstractions itself... well!

8. What do you like most about using mp-wp?

It gets the job done, really. I don't need anything more as far as functionality is concerned; if anything, I need a lot less.

> Yes, time format, article url format, comments URL format+pagination, number of articles on the landing page. The contents/headers of sidebars as well.

Did you edit the values directly in the db via the MySQL CLI or via the web admin UI?

Yes, to post articles and approve comments.

Have you modified any of the "settings" in the mp-wp mysql database (also found in the web UI under "Settings" in the left-hand nav)? If so, which ones? When/how often? Via mysql CLI or via the web UI?

Yes, time format, article url format, comments URL format+pagination, number of articles on the landing page. The contents/headers of sidebars as well.

Do you run any custom plugins on top of what's included in the trunk of mp-wp?

The footnotes -- at least originally they were not bundled.

Have you modified an included theme or created a new theme that you actively use on one of your sites/properties? If so, why / what did you modify?

I have modified the "default" theme to a different look via CSS.

Do you run mp-wp with any other code modifications (outside of themes and plugins)? If so, why / what did you modify?

The only thing I changed for usability myself was the per-comment header. The selection mechanisms (js and span-based), as well as not showing pingbacks in the comments sidebar were added as standard MPWP items/picked up on other blogs.

Describe your typical workflow when publishing an article to your blog (including any pre/post steps, and any other tools/scripts/etc. outside of mp-wp). Include details about working with images, code samples, etc.

I type the article in the text editor (Emacs). After that, I paste it in the MPWP editor and finish the editing there. For code, I just use "pre" tags in line with my Emacs configuration -- I don't use syntax highlighting there as well. I also have a small script for building 'curl url > name.vpatch' command html code.

What do you find most tedious or annoying about using mp-wp? (can be related to any aspect of using mp-wp)

IMO it needs the information on the full set of flags with which its dependencies must be compiled -- building the apache/mysql/php with all the necessary flags is a bit tedious.

What do you like most about using mp-wp?

That it is reliable and simply works.

What is your primary reason for maintaining a blog?

I find that blogging makes 'lying to yourself' impossible, because written down, sloppy thinking becomes apparent. I mostly use it to share code, apart from a few pieces on other topics.

> I simply run the publi.sh script and it opens a post template under vim. When I finish writing I close vim in the usual manner. The script prompts me whther I wish to publish the piece or save as a draft. If I choose publish, the piece is then immediately published to the blog. Images used in the post are automatically uploaded to the proper area as long as they are present in my `pwd` when fired off.

This sounds like a pretty elegant flow tbh.

> I likely would not switch unless some sort of cli interface was devised for it, as I do not like the "web interface" at all. I echo asciilifeform's sentiments regarding db-centric design, myself preferring static pages with no kludge.

Thank you for this perspective, it's more encouraging than I was expecting actually.

@Stanislav Datskovskiy:

> If you're interested, I will include it in the next chapter update.

I would very much be interested, thank you.

> I would like an ecologically-clean replacement, but it would have to be 100% compatible with the old scheme somehow.

Gotcha, makes sense.

> IIRC it was actually a popular feature, and I was the only one who didn't use it. Could be mistaken.

That's what I thought as well but even MP seems to have worked something else out:

With the exception of the multi-uploader (which as mentioned I'm curently bypassing through a set of cmdlines I'm rather satisfied with)

And after reading responses here it sounds like the right script might obviate the need entirely.

@Michael Trinque

> Yes, IIRC the default URL format was not the one commonly used, i.e. $year/$month/$article-slug

This seems almost unanimous now, probably worth making the new default as Diana suggested above.

> Yes, I've patched the thing to support PHP 7.1, which took about an afternoon's worth of effort.

What was the reason for supporting PHP 7.1? Do you happen to know if the patched version also still works on 5.6?

Yes, to post articles. I would rather do this via some other means than a web browser.

2. Have you modified any of the "settings" in the mp-wp mysql database (also found in the web UI under "Settings" in the left-hand nav)? If so, which ones? When/how often? Via mysql CLI or via the web UI?

Yes, IIRC the default URL format was not the one commonly used, i.e. $year/$month/$article-slug

3. Do you run any custom plugins on top of what's included in the trunk of mp-wp?

I currently use some antiquated selection plugin, and will probably move to the newer selection plugin at some point.

4. Have you modified an included theme or created a new theme that you actively use on one of your sites/properties? If so, why / what did you modify?

I modified the default theme, but could have (and would have rather) easily accomplished my theme with CSS alone.

5. Do you run mp-wp with any other code modifications (outside of themes and plugins)? If so, why / what did you modify?

Yes, I've patched the thing to support PHP 7.1, which took about an afternoon's worth of effort.

6. Describe your typical workflow when publishing an article to your blog (including any pre/post steps, and any other tools/scripts/etc. outside of mp-wp). Include details about working with images, code samples, etc.

I typically write in emacs, and then paste the final item into WP when ready. A simple command-line tool to create, update, and delete posts would remove my use-case for the WP admin.

7. What do you find most tedious or annoying about using mp-wp? (can be related to any aspect of using mp-wp)

It seems crazy to have an admin panel accessible to the world, and IP whitelisting is not a solution, as it's trivial to spoof IPs. The code is also a gnarled pile, and would benefit from a rewrite and 95% reduction in mass.

8. What do you like most about using mp-wp?

It's as little as I've found to solve the problem. I'd take less.

By the way, thanks for the offer of BTC. I don't mind taking the time to respond to this; feel free to forgo the payment in my case.