Installing the Disable Emoji plugin seems to have remedied the issue. Hopefully without causing any other issues.
If you’ve been following this idea here, it’s time to update your feed.
I must admit that with a tiny amount of research and set up, I’ve now got something that even John Locke could be jealous of.
For my future self or others interested, I’m using Multi-column Tag Map which has a variety of short codes for implementing various forms of output. Sadly it wasn’t tagged with the word index, so it took some time to find it.
I’ve always had my own administrative interface for this data as well as search and even programmatic tag completion which makes writing and posting easier. However since a lot of what I do is in the public, perhaps it will be useful for readers to have access to the same full list instead of the abbreviated ones that appear as tag clouds or in various sidebars on the site?
Currently I’ve got over 9,000 different tags on the site. Perhaps displaying them publicly will help motivate me to curate and manage them a bit better. I already see a handful of repeated versions based on spelling, spacing, or typos that could be cleaned up. Let’s go crazy!
Hopefully the changes are a well-balanced solution for both my readers and me. One that allows readers to get what they’d like what they’d like and when, and for me to be able to own the relevant data and relationships rather than selling it off or heavily farming it out to one of the newsletter silos like Substack. Hopefully it also cuts down on the manual portions of the problem that I’ve had in the past.
Part of my concern is that, depending on the day, I can be posting just a few items to my website while other days will see 50 or more posts. (It’s amazing how many posts you have when you try to own everything that you post publicly to the web.) Naturally not everyone may be interested in all of my content, and people will have different preferences on how often they receive updates.
To kick off some new options, I’ve updated the email sign up process to allow people to choose some broad categories of content and types they may be interested in receiving. Most of these categories only have a smaller handful of updates within a month, so those indicating some of the specific categories as a preference will only receive them on a monthly basis.
If you’re subscribing to everything, the status updates, the link blog, or portions of the social stream those will be delivered in a weekly newsletter, so readers will get as much as possible without missing out on anything.
I’m starting to collect the preference data for the future, but I’ve also got a beta section of the sign up form to specify the frequency with which you’d like to receive updates. (Note: this isn’t fully functional yet as there are some plumbing issues to handle.)
Folks who are subscribed should start seeing the changes propagate to their subscriptions within the next month.
I’ve been receiving less interaction from those who had previously subscribed to my old WordPress.com website over a decade ago, so I’m leaving those subscribers behind (you should receive an email about this separately). If you find you’re in that old group, just sign up and select the content categories or types you’d like to receive from the new system.
I’m sure there will be some initial bumps and bruises in the transition, so bear with me and don’t hesitate to send your feedback in a way that makes you most comfortable. I’m sure some of my custom posts may not work as well with the newsletter, and hopefully I’ll get those sorted out shortly too.
If you’d like to change your preferences at any time, know that there’s a link at the bottom of the newsletter for changing them. If you would prefer some other custom newsletter with specific categories, content types, or frequency, feel free to email me, and I can set you up with something that most closely meets your specific needs.
Eventually I hope there will be a more streamlined system that will allow people to choose categories, post kinds, and frequency options (daily, weekly, monthly) to suit their specific needs.
I’m still providing a number of different ways (RSS, email, etc.) of helping people to subscribe to what they’d like to receive, so take a look at all of those if you have other needs. If you have questions or need some custom help for receiving exactly what you’re looking for, don’t hesitate to reach out.
As always, thanks for reading!
To sign up/subscribe, visit our subscription page.
I’ve updated my footer so the copyright dates include 2021. I’ve also updated the Webmention button so that it now points at my standalone endpoint for those who may not see or want to use the input box on individual posts. Finally I modified the text that appears on both the standalone endpoint as well as the individual post boxes on each post so that the same text works to properly describe both cases.
I also spent some time trying to fix my fragmention/fragmentioner, but I’m not quite there yet.
My poor little website passed 23,000 comments/replies/reactions yesterday. This is in tremendous part due to webmentions and the ability to collect the conversation about my content across social spaces.
I’m wondering when comments will pass the number of posts (currently 27,648)?
I still have control of the separate @c account, but don’t plan on posting there actively. Maybe I’ll use it with another site?
It’s metacrap–I know, I know–but I’ve been thinking about easy ways to use Open Graph Protocol meta data to add contextual Twitter cards to some of my content when syndicating posts to Twitter. My goal is to leverage the speed and ease-of-use of Micropub clients while doing as little as possible manually, but achieving as much parity between posts on multiple sites.
I’m particularly keen to do this to syndicate/share more of the articles I read and post about on my site without adding additional manual work on my own part.
The Post Kinds plugin for WordPress parses URLs for me and pulls in data to create reply contexts for a variety of posts like bookmarks, reads, watches, listens, etc. Since Post Kinds doesn’t display featured images (yet), I’ve also been using the External Featured Image plugin to display the featured images from the original to add to the reply context of my posts as well.
In addition to all these I’ve been using the All in One SEO plugin to easily add an SEO layer to posts without having to do much thinking about it. AIOSEO recently upgraded their UI and features in the last year, and yesterday I upgraded to the newest v4.0+. One of the new features it’s got is the ability to add default fields or pull in pre-existing custom fields to output OGP meta data.
So I got the idea that since Post Kinds and External Featured Image plugins are pulling in and displaying the sort of data I’d like to show in Twitter cards, I figured why not use them? While metacrap is a DRY violation, the fact that it’s automated for me and is based on data I’m actually showing visually on my website makes it feel much less dirty. It also has the benefit that it helps make some of my syndicated content look and feel on Twitter, more like it does on my website. This is also a problem since Twitter hampers how much data I can syndicate in a single post.
I’ve still got some issues about how to deal with the Post Kinds data, but after a bit of digging around, I discovered the image URL for External Featured Image plugin is hiding in the _dcms_eufi_img field. So I can make the default Twitter settings in AIOSEO pull the external image by setting Default Post Image Source to Image from Custom Field and set the Post Custom Field Name to _dcms_eufi_img.
Since a lot of my posts are reads, bookmarks, etc., this works well, but I can easily override the settings for articles or other custom posts which I make less frequently.
Hopefully I can figure out the settings for Post Kinds to get the rest of the default fields to map across. I’m happy to hear ideas on what field names I’d need to use to get the Post Kinds Name and Summary/Quote fields to map over for the og:title and og:description respectively. Ideally I can manage to get it done without needing to get a subscription to the pro version of AIOSEO which also has support for custom taxonomies which is how Post Kinds works.
Since my theme has relatively solid microformats support, and I have plugin infrastructure to allow easy syndication from my website to Twitter through micropub clients, this last bit for creating Twitter reply contexts helps close some of the loop for me in my syndication workflow while keeping as much context across platforms.
Here’s a visual example of a native post on my site and the corresponding syndicated copy on Twitter. There are some differences, mostly because I don’t have as much control of the appearance on Twitter as I do on my own site, but they’re about as close as I can get them with minimal work.
Hooray for one less plugin in the stack!
I was trying to syndicate from my website so that the post on Mastodon would credit my website for the post and link back to my homepage as the application that made the post. You’ll notice at the bottom of the post there’s the post date and a globe icon, which indicates the post is public, followed by my website name ‘BoffoSocko.com’ and details about replies, reposts, and favorites.
I assuredly won’t release a public plugin for WordPress that does this. But since some have asked how I did it, I thought I’d share some of the internals of a few WordPress plugins that one can quickly modify to achieve the same thing.
That I can currently see, there are three plugins in the repository that will allow one to syndicate content to a variety of Mastodon instances. They are Mastodon Autopost, Mastodon Auto Share, and Share on Mastodon. The first two are closely related and essentially replicate the same codebase.
Similar to using Twitter’s API to crosspost, Mastodon is looking for two bits of information when an application is registered: a client name and a website URL.
Mastodon Autopost and Mastodon Auto Share, both have a file called client.php which define these two variables.
public function register_app($redirect_uri) {
$response = $this->_post('/api/v1/apps', array(
'client_name' => 'Mastodon Share for WordPress',
'redirect_uris' => $redirect_uri,
'scopes' => 'write:statuses write:media read:accounts',
'website' => $this->instance_url
));
You can edit this file with a text editor to change the 'client_name' from 'Mastodon Share for WordPress' to 'Anything You Want'. If you’re in a joking mood, maybe change it to 'Twitter'?
To change the URL so that the link on the client_name directs to your website, you’ll want to change the line 'website' => $this->instance_url.
In particular change $this->instance_url to 'https://example.com' where example.com would be your website. I’ll note that $this->instance_url on this line in the original plugin is a bug. If left alone, it points the URL to your home Mastodon instance instead of to the more logical https://wordpress.org/plugins/autopost-to-mastodon/ where the plugin lives.
If you prefer using Jan Boddez‘ excellent plugin, you’ll want to do something similar, except in that case you’ll want to change a file named class-options-handler.php in the includes folder.
Here you’ll want something like:
'client_name' => __( 'Example.com' ),
But note that Boddez doesn’t have a similar bug, so the website line
'website' => home_url(),
is already correctly defined so that your website will automatically be linked without any changes to it.
If you’re already using one of these plugins and manually modify them, note that you’ll probably need to re-authorize the plugin so that the changes propagate.