{"id":2003,"date":"2022-11-19T20:57:15","date_gmt":"2022-11-19T20:57:15","guid":{"rendered":"https:\/\/opendna.com\/blog\/?p=2003"},"modified":"2024-10-13T18:14:49","modified_gmt":"2024-10-13T18:14:49","slug":"getting-started-with-mastodon-x-wordpress","status":"publish","type":"post","link":"https:\/\/opendna.com\/blog\/2022\/11\/19\/getting-started-with-mastodon-x-wordpress\/","title":{"rendered":"Getting started with Mastodon x WordPress"},"content":{"rendered":"\n

If you have a WordPress<\/a> blog and a Mastodon<\/a> account, the three things you’re going to want to do are verify your identity<\/a><\/strong>, embed toots<\/a><\/strong>, and syndicate your blog<\/a><\/strong> on the fedirverse<\/a>.<\/p>\n\n\n\n<\/a>

Verifying Mastodon Identity<\/h2>\n\n\n\n

Identity verification in the fedirverse is based upon controlling a property elsewhere on the web.<\/p>\n\n\n\n

The most basic version of this is running a Mastodon instance: @textfiles@mastodon.archive.org<\/a> is certainly Jason Scott at the Internet Archive. (Hosting a Mastodon instance is beyond scope of this post.)<\/p>\n\n\n\n

As an alternative, @reuters@newsie.social can prove<\/a> they are an authorized account of Reuters news service by inserting code on Reuters.com<\/em>. There are three ways to do this.<\/p>\n\n\n\n

Option 1: Edit Theme Metadata<\/h3>\n\n\n\n

Insert <link rel=\"me\" href=\"https:\/\/{host}\/@{user}\"><\/code> between the <head><\/head><\/code> elements in header.php<\/em>. This method is not available to WordPress.com-hosted sites.<\/p>\n\n\n\n

Option 2: Social Media Link Blocks<\/h3>\n\n\n\n

“Mastodon, WordPress, and Verification<\/a>” by @TindrasGrove@infosec.exchange<\/a> demonstrates a step-by-step to using post-Gutenberg blocks<\/a> to add a Mastodon verification link. This method should<\/em> be compatible with WordPress.com-hosted sites using modern themes.<\/p>\n\n\n\n

Option 3: A Verification plugin<\/h3>\n\n\n\n

I didn’t see a plugin for mastodon verification so I wrote one. It’s on github: simple-mastodon-verification<\/a> and wordpress.org: simple-mastodon-verification<\/a>. It makes Option 1 accessible to WordPress.com-hosted sites by inserting a form field on the General Settings<\/em> menu. This method should be compatible with WordPress.com-hosted sites, but free plugins require a “Business Plan” upgrade.<\/p>\n\n\n\n<\/a>

Embed Toots in Blog Posts<\/h2>\n\n\n\n

@jynersolives@mastodon.social<\/a> and @ThetaSigma@fandom.ink<\/a> asked “is there a good way to embed Toots on a WordPress<\/a> website?” Short answer: no. Either use screenshots and link to the source, or embrace @Gargron@mastodon.social<\/a>‘s “no quote tweets” philosophy<\/a>.<\/p>\n\n\n\n

The “WordPress Way” is to take the public URL of the Toot provided (not the one loaded from your<\/em> own Instance) and paste into a Block to take advantage of WordPress’ built-in iframe wrap: click Share<\/em> >Copy Link<\/em> and paste into WordPress. You’ll be rewarded with a 1000px-tall iframe and Console errors about violating the Content Security Policy directive about unsafe inline content<\/a>.<\/p>\n\n\n\n

The WordPress kludge is to use an HTML block. If you are logged-in to Mastodon, you can get iframe embed code by clicking the More option (“…”) at the bottom right of a toot and selecting “embed”. While the supplied iframe code will be accepted by WordPress, and the dimensions of the embed code can be changed, it will return a “This block contains unexpected or invalid content” error.<\/p>\n\n\n\n

The long and short of it is that iframes are dangerous so WordPress has a list of approved sites for embeds<\/a>. Because of the federated nature of Mastodon \u2014 and the fediverse \u2014 few (if any) instances will ever be on that list. The dimensions of the iframe are hard-coded in the WordPress Core; while a plugin or JS hack could correct them, neither presently exist (nor should they).<\/p>\n\n\n\n

If you feel compelled to embed Toots, I suggest using screenshots and link to the source. Remember: your embeds will 404 when instances shut down, and when users auto-purge their timelines. (Just don’t forget the alt-text.)<\/p>\n\n\n\n<\/a>

Syndicate Your Blog on Mastodon<\/h2>\n\n\n\n

@pfefferle@mastodon.social<\/a> published the ActivityPub plugin<\/a>, which implements the protocol for WordPress blogs. When enabled (some .htaccess modification<\/a> may be required), WordPress will respond to Webfinger<\/a> requests for users (user@domain) and be discoverable and followable by Mastodon users. It’s worth noting that the ActivityPub feed is per-user<\/em> (using Author pages<\/a>), not sitewide, so @blog<\/a> does not report everything published by all users on opendna.com. (This has some interesting potential for using WP authors to create topical feeds, or only advertise some posts.)<\/p>\n\n\n\n

(Note: There is a known glitch<\/a> with following a WordPress x ActivityPub site, in which results in “request pending” for Follow requests<\/em>.)<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

If you have a WordPress blog and a Mastodon account, the three things you’re going to want to do are verify your identity, embed toots, and syndicate your blog on the fedirverse. This post briefly describes how to do all three.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"webmentions_disabled_pings":false,"webmentions_disabled":false,"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":3,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"federate","footnotes":""},"categories":[190],"tags":[205,206,138,627,207],"class_list":["post-2003","post","type-post","status-publish","format-standard","hentry","category-builds","tag-diyhost","tag-fediverse","tag-howto","tag-mastodon","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/posts\/2003","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/comments?post=2003"}],"version-history":[{"count":25,"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/posts\/2003\/revisions"}],"predecessor-version":[{"id":2331,"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/posts\/2003\/revisions\/2331"}],"wp:attachment":[{"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/media?parent=2003"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/categories?post=2003"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/opendna.com\/blog\/wp-json\/wp\/v2\/tags?post=2003"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}