Tag: Meta

You should keep an eye on the Posted Today page; today this post popped up and it’s still a good glimpse into the life story of my brain.

I’m mute on social for Blackout Tuesday, but since my blog is my own space I’ll be posting here — however I’ll be focused on linking black voices supplemented by ancillary material, and refraining from saying anything of my own. (Soundtrack: have you opened Apple Music?)

If you read the blog through RSS, you’ll be missing some things for awhile, as I haven’t yet figured out how to get my post addenda to show up along with posts in my RSS feed. This doesn’t even reach the fact that I can’t customize my JSON feed at all.

Using Comments As Post Updates Instead Of As Comments

At long last, my blog has a functionality I’ve long wanted but for some reason no one ever bothered to develop. It really should be its own thing, but since it isn’t: given that my blog doesn’t have comments, I’ve turned native, internal WordPress comments into a system for posting addenda on posts, rather than manually adding them to the post body itself. Now any time I want to add something to an existing post, on the backend at least each update will have its own timestamp. I’ll worry later about whether or not I want to include those timestamps on the public addenda themselves. For now, I’m just satisfied that I figured out how to get this displaying the way I wanted it to, after much consternation trying to get template tags to work the way I thought they were meant to be working.


  1. For the purposes of demonstration, this is my first official addendum using WordPress comments instead of editing the post itself.
  2. What I'm not going to even think about tonight is that for this to work I also need them displayed on index pages and anywhere else the full text of blog posts appear, e.g. on tag, date, and search pages.
  3. Oh, I also seem to have a markup problem, in that the comment text is wrapped in p tags inside the li tags of the list, whereas that doesn't normally happen in lists. Another issue for Sunday daytime.
  4. Went ahead and found the solution to that last one before I go to bed: using echo get_comment_text(); instead of comment_text();.

Next up: crowdsourcing some post discovery by adding a Reader Picks page to the blog. I’ve got some stuff to sort out first with the Links Manager which for some reason disappeared from default WordPress and which one of my plugins reenabled.

Late-night accomplishment: I don’t know when we will hit a day when my Posted Today page will show posts, but I got my total post count included and figured out how to get it formatted with the damned comma.

‪I’m abandoning the entire idea of self-references to build context over time in the blog until someone codes a plugin expressly for this. The entire process today was nothing but dashed hopes upon which I wish to spend not one jot more of my time and wherewithal.‬ This is a no-brainer blogging feature and the fact that it still doesn’t exist even a decade or more after I last was using WordPress this extensively is ridiculous.

I’m at a loss. Anyone know how to do this photos page approach using WordPress? Really, I just need pointers; my google-fu is completely failing me.

Well, blog posts now should include any links to later posts which reference them, except that there seem to be some gaping holes where the self-pings did not send when I bulk updated old posts. Something around 75 self-pings did send, but others most certainly did not. I’m not sure if they got throttled by the sheer system load, or blocked as an attack, or what. I’m not sure how to get that solved, exactly, but at least it should be working from here on out for any future posts referencing past posts.


  1. Although now I’m unsure on that last part, as I went into a recent post that didn’t seem to send a self-ping to an older post during the bulk updating and it still did not send a ping to that older post. I’m not sure what’s happening here.
  2. I feel like there ought to be a simpler solution here, like a plugin that searches your posts for links to other local posts and directly injects a ping into the database.
  3. This has been disabled, as I made a change that broke it, then undid the change, and somehow it remained broken and WordPress would error out.

Micro.blog did this nifty thing to make a Photos page (or, it still does; I’m just not blogging there anymore) by looping through all your posts with JPGs in them (under the idea that PNGs probably were screenshots, not photos), grabbing the first photo from each post, and making a gallery out of them; each photo linked to its corresponding blog post. Today’s project: explore how to do something similar in WordPress, especially if I somehow can get it to use Jetpack’s tiled gallery format.

I’ve managed to get an “on this day” feature working, although because I like to be difficult mine is called Posted Today. It’s powered by a plugin by Alan Levine which I slightly hacked, and which I found from this Chris Aldrich post. I think the fix I added to prevent the current “sticky” post on my front page from inappropriately appearing also will prevent a “sticky” post that happens to actually be from the current day from appearing, so it’s not quite yet a settled matter, but it will do for now.

Now I’m wondering how I can make an On This Day section on my WordPress archives page?


  1. How can I use this plugin on a page instead of as a widget? I don’t have sidebars.
  2. I’m going to tinker with this one instead.

Glory be: with some jiggery-pokery using a couple of different plugins, I’ve now got a no-maintenance blogroll page.

My Annoying Weblog Comments Use Case

It’s not bad enough that I want internal-only webmentions so I can automatically build a web of self-references — one that’s useful rather than garbage SEO-bait linkback bullshit. Now I also want a plugin that effectively creates a riff on Submit.as, wherein I’d use the native WordPress comments functionality to take comments, but rather than publishing them there’d be a workflow by which I could respond to any given comment by making a new blog post. Think of it more like a letter-to-the-editor function built atop the comments function.

What’s more, had I both these features, if someone submitted a comment-letter on one of my reply-to-comment posts, when I replied to that in a new post that new post would reference-link the previous one, creating a bidirectional chain of letters and responses.

This is the problem with my return not just to blogging but to blogging via WordPress: I’m back on my horse of seeing all sorts of features — some of which (e.g. my original unsupported use case) I originally thought about a decade or more ago — that seem like no-brainers to me but that don’t seem to exist.

I’ve added a blogroll page, but currently it’s empty. I’m hoping that the makers of the Sync OPML to Blogroll plugin will be able to support JSON files, as Feedbin’s access to one’s subscriptions via their API comes in JSON not OPML. I’d rather find such an automatic process than need to regularly update a list here.


  1. It turns out that the Feedbin API does provide an OPML list, by changing .json to .xml, making this possible.