FediBoost

No, FediBoost requires the ActivityPub plugin to be installed and properly configured. FediBoost extends ActivityPub's functionality to add automatic boosting capabilities.

Yes, by post type. Under Settings > FediBoost, choose which post types are boosted when published. Only post types the ActivityPub plugin federates are listed, and all of them are selected by default. Developers can use the fediboost_should_boost_post filter to programmatically control which posts are boosted. See the Developer Hooks section below for details.

When FediBoost boosts a post, Mastodon sends that boost back to your site, and the ActivityPub plugin would normally record it as a "repost" on the post. Since that's just your own account boosting your own post, FediBoost discards reposts that come from any of your connected Mastodon accounts. Reposts from everyone else are recorded as usual. Developers can turn this off with the fediboost_ignore_self_boosts filter. Reposts recorded before this was added can be removed with WP-CLI: wp fediboost cleanup-self-boosts --dry-run lists them, wp fediboost cleanup-self-boosts moves them to the trash, and adding --force deletes them permanently. Only accounts still listed on the FediBoost settings page are matched, so run the cleanup before disconnecting an account.

FediBoost encrypts OAuth tokens using your WordPress authentication salts (defined in wp-config.php). If these salts are changed — for example, by a security plugin, during a security incident response, or by manually editing wp-config.php — all stored tokens will become invalid. You will need to reconnect your Mastodon accounts under Settings > FediBoost after any salt change. This is standard behavior for WordPress plugins that encrypt sensitive data using the built-in salts. The OpenSSL PHP extension is required for token encryption. If OpenSSL is not available, FediBoost will not be able to store account credentials securely and will display an admin notice.