Brandon Kraft

FediBoost extends the ActivityPub plugin by automatically boosting your WordPress posts on your connected Mastodon accounts when they are published.
When you publish a new post on your WordPress site, FediBoost will automatically boost (reblog) that post on your linked Mastodon account, helping increase visibility across the fediverse.
Features:
<ul>
<li>Automatic boosting of new posts to connected Mastodon accounts</li>
<li>Seamless integration with the ActivityPub plugin</li>
<li>No additional configuration required after setup</li>
</ul>
Requirements:
<ul>
<li>The <a href="https://wordpress.org/plugins/activitypub/" rel="ugc">ActivityPub plugin</a> must be installed and configured</li>
<li>A connected Mastodon account via ActivityPub</li>
</ul>
<h3>Developer Hooks</h3>
FediBoost provides several filters that allow developers to customize its behavior. All filters follow WordPress coding standards and can be added to your theme’s functions.php file or a custom plugin.
<h4>fediboost_should_boost_post</h4>
Control whether a specific post should be boosted. Return false to skip boosting for the given post. Default: true.
Parameters:
<ul>
<li><code>$should_boost</code> (bool) — Whether the post should be boosted.</li>
<li><code>$post</code> (WP_Post) — The post object being published.</li>
</ul>
Example:
<pre><code>add_filter( 'fediboost_should_boost_post', function( $should_boost, $post ) {
 // Don't boost posts in the "internal" category.
 if ( has_category( 'internal', $post ) ) {
 return false;
 }
 return $should_boost;
}, 10, 2 );
</code></pre>
<h4>fediboost_boost_delay</h4>
Delay in seconds after ActivityPub federation completes before the boost is executed. This delay is only used when the federation completion hook fires successfully. Default: 30.
Parameters:
<ul>
<li><code>$delay</code> (int) — The delay in seconds.</li>
</ul>
Example:
<pre><code>add_filter( 'fediboost_boost_delay', function( $delay ) {
 // Wait 2 minutes after federation before boosting.
 return 120;
} );
</code></pre>
<h4>fediboost_fallback_delay</h4>
Delay in seconds before a boost is executed when the ActivityPub federation completion hook does not fire. This acts as a safety net for older versions of the ActivityPub plugin that do not support the <code>activitypub_outbox_processing_complete</code> hook. If the federation hook fires first, the fallback is cancelled and <code>fediboost_boost_delay</code> is used instead. Default: 300 (5 minutes).
Parameters:
<ul>
<li><code>$delay</code> (int) — The fallback delay in seconds.</li>
</ul>
Example:
<pre><code>add_filter( 'fediboost_fallback_delay', function( $delay ) {
 // Wait 10 minutes in the fallback path.
 return 600;
} );
</code></pre>
<h4>fediboost_manage_capability</h4>
WordPress capability required to manage FediBoost settings. Default: ‘manage_options’. Note: a floor of ‘edit_others_posts’ is enforced regardless of this filter’s return value, so you cannot lower the requirement below that capability.
Parameters:
<ul>
<li><code>$capability</code> (string) — The required capability.</li>
</ul>
Example:
<pre><code>add_filter( 'fediboost_manage_capability', function( $capability ) {
 // Allow editors to manage FediBoost settings.
 return 'edit_others_posts';
} );
</code></pre>
<h4>fediboost_max_accounts</h4>
Maximum number of connected Mastodon accounts. Default: 10.
Parameters:
<ul>
<li><code>$max</code> (int) — The maximum number of accounts.</li>
</ul>
Example:
<pre><code>add_filter( 'fediboost_max_accounts', function( $max ) {
 // Allow up to 25 connected accounts.
 return 25;
} );<h3>External Services</h3>
</code></pre>
FediBoost connects to external Mastodon instances that you configure (e.g., mastodon.social). This communication is essential for the plugin to function and is initiated only with the instance you explicitly provide.
During setup:
<ul>
<li>FediBoost registers an OAuth application on your Mastodon instance and performs an authorization flow so it can act on your behalf.</li>
</ul>
When a post is published:
<ul>
<li>FediBoost searches for the post on your Mastodon instance and performs a reblog (boost) via the Mastodon API.</li>
</ul>
Data sent to your Mastodon instance:
<ul>
<li>Your instance URL</li>
<li>OAuth authorization codes</li>
<li>Search queries to locate your posts</li>
<li>Reblog (boost) requests</li>
</ul>
Data stored locally on your WordPress site:
<ul>
<li>Encrypted OAuth tokens</li>
<li>Your Mastodon username</li>
<li>Your Mastodon instance URL</li>
</ul>
Each Mastodon instance has its own privacy policy and terms of service. You can find a list of instances and their policies at <a href="https://joinmastodon.org/servers" rel="nofollow ugc">joinmastodon.org/servers</a>.
This plugin does not send data to any third-party service other than the Mastodon instance(s) you explicitly configure.

FediBoost


This plugin solves a core frustration in the fediverse: Sites have their own identities, but most of us already have separate identities in the fediverse, too. FediBoost automatically boosts posts from your site’s identity from your own identity in the fediverse.



It does what it says on the label, and it even works with custom post types if ActivityPub is enabled for them. It has wp-cli support, too.



If you federate your blog posts with the ActivityPub plugin and want to automatically boost them from your main account, give it a try!


Does what it says on the label

Automatically boost WordPress posts on connected Mastodon accounts when published via ActivityPub.

jdormit

Pterotype expands your audience by giving your blog an ActivityPub stream, making it a part of the Fediverse. Users of Mastodon, Pleroma, and other Fediverse services will be able to follow and share your posts from the platform of their choice.

Pterotype

Pterotype expands your audience by giving your blog an ActivityPub stream, making it a part of the Fediverse.

FediBoost vs Pterotype