FediBoost vs PostCaster

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: Automatic boosting of new posts to connected Mastodon accounts Seamless integration with the ActivityPub plugin No additional configuration required after setup Requirements: The ActivityPub plugin must be installed and configured A connected Mastodon account via ActivityPub Developer Hooks 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. fediboost_should_boost_post Control whether a specific post should be boosted. Return false to skip boosting for the given post. Default: true. Parameters: $should_boost (bool) — Whether the post should be boosted. $post (WP_Post) — The post object being published. Example: 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 ); fediboost_boost_delay 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: $delay (int) — The delay in seconds. Example: add_filter( 'fediboost_boost_delay', function( $delay ) { // Wait 2 minutes after federation before boosting. return 120; } ); fediboost_fallback_delay 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 activitypub_outbox_processing_complete hook. If the federation hook fires first, the fallback is cancelled and fediboost_boost_delay is used instead. Default: 300 (5 minutes). Parameters: $delay (int) — The fallback delay in seconds. Example: add_filter( 'fediboost_fallback_delay', function( $delay ) { // Wait 10 minutes in the fallback path. return 600; } ); fediboost_manage_capability 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: $capability (string) — The required capability. Example: add_filter( 'fediboost_manage_capability', function( $capability ) { // Allow editors to manage FediBoost settings. return 'edit_others_posts'; } ); fediboost_max_accounts Maximum number of connected Mastodon accounts. Default: 10. Parameters: $max (int) — The maximum number of accounts. Example: add_filter( 'fediboost_max_accounts', function( $max ) { // Allow up to 25 connected accounts. return 25; } ); External Services 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: FediBoost registers an OAuth application on your Mastodon instance and performs an authorization flow so it can act on your behalf. When a post is published: FediBoost searches for the post on your Mastodon instance and performs a reblog (boost) via the Mastodon API. Data sent to your Mastodon instance: Your instance URL OAuth authorization codes Search queries to locate your posts Reblog (boost) requests Data stored locally on your WordPress site: Encrypted OAuth tokens Your Mastodon username Your Mastodon instance URL Each Mastodon instance has its own privacy policy and terms of service. You can find a list of instances and their policies at joinmastodon.org/servers. This plugin does not send data to any third-party service other than the Mastodon instance(s) you explicitly configure.

PostCaster publishes WordPress posts to Bluesky and Mastodon when a post goes live. It supports both site-wide accounts and personal author accounts, with previews, test posts, and per-post overrides on the post edit screen. This plugin is intended for editorial sites that want social posting to stay close to the WordPress publishing workflow. Key capabilities: Publish automatically when a post moves from unpublished to publish Use site-wide accounts in PostCaster > Global socials Let authors use their own accounts in PostCaster > My socials Preview the exact text before publishing Override the text per article Choose featured-image behavior per network Re-publish manually from the post edit screen when needed Quick start: Activate the plugin. Enable PostCaster in PostCaster > Settings. Choose which post types may be published automatically. Configure one or more site-wide accounts in PostCaster > Global socials. Send a test post for each configured network. Publish a test article and confirm the result on the target network. Supported networks: Bluesky Mastodon Permissions and publishing model: Editors and administrators can publish through configured global accounts. Authors can publish through their own personal accounts when personal publishing is enabled for them. A user who has access to both global and personal targets can choose which targets to use during manual publishing. If Co-Authors Plus is active, linked co-authors are also recognized for personal publishing. Templates and previews: The default message template is based on post title and URL. You can set a general template, network-specific templates, and post-specific overrides. The post edit screen shows previews for the currently available publish targets. If the final message is still too long for a network, PostCaster skips that target and stores an error on the article. For template details and examples, see docs/templates.md in the plugin repository. Troubleshooting highlights: Always use the built-in test-post buttons after changing credentials. If a network is enabled but not posting, first check credentials and article-level errors. If encrypted credentials can no longer be read, re-save them in Global socials or My socials. Publishing runs through Action Scheduler in the background; low-traffic sites still benefit from a real server cron job or scheduled task for reliable timing. External services: PostCaster connects to external social networks only after an administrator or user explicitly configures that network and saves the required credentials. When configured, PostCaster may send: text rendered from post fields and templates featured image bytes and alt text the configured account identifiers required by that network Relevant service documentation and terms: Bluesky developer docs: https://docs.bsky.app/ Bluesky terms: https://bsky.social/about/support/tos Mastodon API docs: https://docs.joinmastodon.org/api/ Privacy note: PostCaster does not send usage analytics or telemetry to the plugin author. Network requests are only made to the configured social networks for test posts and actual publishing.