I’ve added a plugin, Mastodon Autopost, to crosspost from this blog to my Mastodon instance.
This won’t bring back any reactions to this blog, unlike Twitter reactions which do get back to this blog through Webmention. For that I would need to use Bridgy Fed. However that has as a disadvantage that it would turn my blog into a separate ActivityPub account, an activitypub user in its own right.

For now I’d rather have a separate Mastodon account (on my personal instance). Not everything I post on my blog I want to post to Mastodon, and not everything I post on Mastodon I want to have in my blog (e.g. responses to or reposts of others). I can definitely see me using this blog as the one and only hub for my online communications, but for that to work, I want to be able to keep ephemeral postings outside my regular site and my rss feeds, and more importantly be able to determine intended audiences per posting. Another requirement is that I can post tweets about a blogpost without that tweet being a separate blogpost (now I use the post excerpt for that and send it to twitter)

Currently I have my Mastodon (and my first Twitter account) set to me needing to approve every follower. My audience for a message is somewhat known to me that way, and I can shape a message accordingly. We all talk differently to different people and have conversations in different settings and contexts. This is true for online conversations just as much as for offline conversations. My microblog account does post everything from my blog but I also interact there independently from my blog.

With this plugin, for each posting I can determine if it is cross posted to Mastodon. I already had a similar setting for Twitter (and Flickr, which I don’t use). See the images.

It works as intended. I set the excerpt of this posting to “If all works as intended, this blogpost should show up in my Mastodon instance #wordpress #activitypub”, and set the plugin to post title, excerpt and URL.


I have a ‘recent posts’ and ‘recent comments’ section in the sidebar. This seemed to create problems with the processing of webmentions, specifically with Aaron Parecki’s Xray library for grabbing structured info from any URL. It would find an apparently improperly micro-formatted link in the sidebar and take that as the URL of the posting referred to. This would create faulty likes on other people’s sites, which then would send webmentions to the wrong postings.

As recent posts and recent comments are only a navigational aid when you’re looking at things like the front page, search results and archive pages, I looked into if I can show them on those pages only. Because if those sections aren’t present on the pages of individual postings, they cannot cause problems when parsed for structure. This being a WordPress site, of course there’s a plugin for it, Widget Context. I installed it, removed the offending widgets from individual pages, and it looks like the problem has been solved.

Ja, ich merke immer wieder das ich immer wieder die unterschiedlichen Schichten der ganzen Lasagna auseinander ziehen muss: WordPress, WordPress Thema, Indieweb, andere Plugins, was im Database ist, und wie was gezeigt wird usw. Übrigens habe ich mittlerweile Jetpack ganz ausser Betrieb gestellt. Früher habe ich das für Besuchsstatistik verwendet. Aber da die meisten Funktionen von Jetpack über XML-RPC laufen, und XML-RPC blockiert wird von meinem Hoster wegen Sicherheitsrisiken, habe ich das Plugin abgestellt.

Replied to a post by Heinz WittenbrinkHeinz Wittenbrink

Danke, Ton! Ich stehe noch ganz am Anfang, obwohl ich die IndieWeb-Plugins schon lange installiert habe. Ich würde dieses Gebiet gerne mit dir und deinem Netzwerk zusammen entdecken. Ich muss jetzt erst einmal die Probleme, die ich lösen muss, in eine Ordnung bringen. Zum Teil hängen sie damit zu…

Goed te horen dat je naar WP bent overgestapt Frank! Dat maakt dat we met de hobbels die we tegenkomen wat meer samen kunnen optrekken, want ik gebruik ook WP.

Over die webmentions: in plaats van importeren in de WP database, kun je ze toch ook allemaal opnieuw sturen naar jezelf? Je hebt zeg je de database van webmentions die je op je Jekyll blog hebt ontvangen. Wat je daarvan nodig hebt is de webmention source (url van de bron van de link) en de webmention target (url van jouw posting die genoemd wordt) Die kun je ‘voeren’ aan je eigen webmention endpoint, precies zoals het formulier dat onder iedere WP posting van je staat voor het handmatig indienen van een webmention doet (waarbij de target al is vastgesteld). Het is immers niet zo dat alleen de site die jou noemt een webmention daarvan kan sturen. Iedereen kan dat naar jouw endpoint, en dus ook jij zelf. Dat is het mooie van webmentions. Webmention is je importer. Ik gebruik het wel om webmentions toe te voegen van sites die dat zelf niet versturen. Jouw WP ziet ze dan als nieuwe mentions binnenkomen en plaatst het in de eigen database, en verwerkt ze verder t.a.v. opmaak. Et voila, geïmporteerd.

Replied to Een nieuwe start by an author

..ik wilde al langer overstappen van Jekyll naar WordPress. Niet omdat Jekyll nu zo verschrikkelijk is, maar omdat ik merkte dat ik tegen iets teveel hobbels liep in Jekyll. Hobbels die vaak in WordPress al wel goed zijn genomen. …