Frequently Asked Questions
Yes, also when you're scheduling content to get published later, your content will get shared to Mastodon, as soon as your content gets published.
By setting the "Content type for toots" (on admin/config/services/mastotoot) to "- None -", you can stop sharing your posts site-wide. This has no effect on previously shared posts.
As long as your posts are still unpublished or when creating new content, there's a checkbox in the content form's publishing actions section to prevent sharing for this one node. This also works for scheduled publishing (when the node gets published on cron run).
You can delete remote posts in two ways: either by deleting them remotely (on Mastodon), or by unpublishing that content on your Backdrop site. It's not necessary to delete the local content, unpublishing alone does the trick. If you delete content in Backdrop, the remote toot will get deleted, too.
No, old and already published content isn't touched. Only if you publish an old and previously unpublished node, it will get shared.
No, this module really only works with nodes.
No, this module is very simple and doesn't handle media files at all. At least, for now.
Depending on how your cron job for Backdrop CMS runs, it can be necessary to override the base URL. Mostly, if you run cron directly with Bee. In that case, Backdrop doesn't "know" what the public URL to your site is. If you run cron the usual way (like described on admin/config/system/cron), this setting shouldn't be necessary.