WordPress, MovableType

Kara Swish­er inter­viewed Matt Mul­len­weg on Recode Decode! It’s extreme­ly sad how excit­ed I was to see this in my pod­cast feed (and that I’m already writ­ing about it before the post has actu­al­ly gone up on Recode, itself.)

We Called it Guten­berg for a Rea­son

They dis­cussed Mov­able­Type briefly, which was revived in 2013 and now has a 50% Japan­ese lan­guage user­ship, and I’d real­ly like to know how that hap­pened.

Also, I had no idea his and Word­Press’ com­pa­ny, Automat­tic owned Lon­greads and Atavist. Hilar­i­ous­ly, I also found out his old blog themes are now avail­able in the Word­Press theme direc­to­ry. Unfor­tu­nate­ly, I had to wait a whole darned week for a “light­ly-edit­ed tran­script” [local back­up] of this episode, but frankly, I’m just glad they decid­ed it was worth tran­scrib­ing at all, con­sid­er­ing Word­Press’ out-of-the-excitable-for-dab­blers sta­tus. I mean… it was prob­a­bly a bit cru­el to place Mullenweg’s episode in direct fol­lowup to Kara Swisher’s inter­view with Mark Zucker­berg the pre­vi­ous week, which — for obvi­ous and entire­ly-jus­ti­fied rea­sons — will sure­ly be the most-lis­tened-to Recode Decode episode by far in its recent his­to­ry, at least. 

I’ve been doing Word­Press for 15 years and I’d like to do it the rest of my life.”

Yiokes! Ya know? You’re damned right, “oof.”

I think every tech com­pa­ny should have an edi­to­r­i­al team.”

Out of sign­f­i­cant and near­ly-unbear­ably heavy bias, I must agree whole­heart­ed­ly with this state­ment — and Mullenweg’s req­ui­site elab­o­ra­tion — and I must leave you with the expres­sion of one final wish: that Zucker­berg had been inter­viewed post-Matt, instead, and Kara Swish­er would’ve brought this up with him.

Extreme Composition Meta

My new col­umn about Ever­note, Drop­box Paper, and the sig­nif­i­cance of mod­ern word pro­cess­ing was stretched near­ly to 7000 words thanks to my gen­er­ous fiance’s Leno­vo ThinkPad (my Spec­tre has yet to be fixed, though its new charg­ing port arrived today,) which is even more of a rad machine than I could’ve imag­ined — supe­ri­or to my lithe, enduser-as-hell Hewlett Packard in many writ­ing-spe­cif­ic con­ve­niences like seg­ment­ed nav­i­ga­tion keys. Win­dows 7 is even bet­ter than we’ll all remem­ber it, though I’ll be glad to go back to a high-res­o­lu­tion dis­play.

Con­sid­er­ing that this blog, itself exists sole­ly because I want­ed to explore as many forms of word pro­cess­ing as pos­si­ble for this piece, acknowl­edg­ing its exis­tence would be painful­ly, even vul­gar­ly meta, so here’s a pull quote:

This is where Word­Press should out­shine just about every­thing else as a pure, open-source Con­tent Man­age­ment Sys­tem for any and every use by any and every folk with serv­er space, so I thought I’d try out my own fresh, ultra-con­nect­ed install to see how its expe­ri­ence has changed. In word pro­cess­ing terms, its iOS and Win­dows clients are lightyears ahead of where they were a few years ago, but to take full advan­tage of them, one must allow Word­Press’ own soft­ware access that’s not Open Web at all.

Shife's External Content
5/6 of this lit­tle blog’s con­tent sources are not my serv­er.

Of course, the soft­ware I’m refer­ring to here is Automatic’s Jet­pack, which is nec­es­sary — as far as I can tell, any­way — in order to pub­lish remote­ly and par­tic­i­pate in the greater Word­Press dot com com­mu­ni­ty and its “bil­lions of posts,” and is no doubt respon­si­ble for this tee­ny tiny lit­tle site’s already piti­ful­ly glut­to­nous depen­dence on exter­nal con­tent. The “Read­er” func­tion with­in a Jet­pack-enabled Dash­board is prob­a­bly its most bewil­der­ing fea­ture. I sup­pose I’m just too young to tru­ly under­stand the his­to­ry of blog­ging, but I believe in The Open Web, okay? I real­ly do.

After this evening, I actu­al­ly have a few revisions/additions which I may or may not get around to address­ing in the next few days, depend­ing on whether or not I’m able to fix my lap­top tomor­row:

  • I for­got about mass email clients and TinyLet­ter — MailChimp’s aging spin­off.
  • I also for­got to men­tion write.as — a beau­ti­ful and intrigu­ing plat­form that’s not quite like any­thing else.
  • I didn’t both­er to check out Evernote’s in-brows­er expe­ri­ence first. Turns out, it’s a lot bet­ter than the app.

For bet­ter or worse, I’ll cer­tain­ly have knocked this top­ic off the wall for a good while when I can final­ly feel done with this.

My Tedious Analog Journey Continued

The bizarre redun­dan­cy of dis­patch­ing to a Word­Press instance via furi­ous tap­ping with­in the iOS app con­tin­ues to occu­py my thoughts. Hel­lo, you ancient old bitch of a plat­form. What’s shakin’? Why are mod­ern, com­plete­ly Word­Press-inde­pen­dent pub­li­ca­tions like The Out­line still send­ing con­tent your way? Please warn me thor­ough­ly and very far in advance if you plan to answer ver­bal­ly, so that I may be spared imme­di­ate and vio­lent car­diac arrest.

I have been with­out a work­ing desk­top-class plat­form for a week now (my Spectre’s port is still bro­ken and my desk­top is in stor­age,) “reduc­ing” me to iOS word pro­cess­ing like this, hand­writ­ing, and my fiancé’s old elec­tric type­writer, all of which has inspired more opin­ing for my upcom­ing State of Word Pro­cess­ing col­umn than I would’ve expect­ed. My pri­ma­ry goal is to have the port fixed or replaced by next week­end so that I can resume the newslet­ter, writ­ing full-chat, and in prepa­ra­tion for the 24 Hours of LeMans.