# Setting up an ActivityPub Actor
**URL:** https://meta.discourse.org/t/setting-up-an-activitypub-actor/314578
**Category:** Administrators
**Tags:** video, activitypub
**Created:** [July 2, 2024, 8:09am UTC](https://meta.discourse.org/t/setting-up-an-activitypub-actor/314578 "2024-07-02T08:09:48Z")
**Posts on this page:** 1
**Showing post:** 7
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [December 19, 2024, 1:21pm UTC](https://meta.discourse.org/t/setting-up-an-activitypub-actor/314578/7 "2024-12-19T13:21:29Z")
Unless you have a specific reason not to do so, it’s recommended to use the `tests-passed` branch of Discourse. See further:
> [@What is the best branch of github.com/discourse/discourse？](https://meta.discourse.org/t/what-is-the-best-branch-of-github-com-discourse-discourse/158656/3):
>
> We recommend running tests-passed and updating when [beta releases](https://meta.discourse.org/tag/release-notes) are available. This gives you the flexibility of updating when you want/need to. Stable isn’t recommended except in select cases… like extensive customization (99% of the sites we host aren’t in this category). There are months between stable releases, and we only backport critical or security related bugs… so if there’s a minor bug in stable you may have to live with it for quite a while. There’s some more relevant discussion h…
Furthermore, you can assume that plugin or customisation with the #experimental tag (as the ActivityPub plugin doees) only works reliably on the latest version of Discourse.
More specifically to your implicit questions about version management, in Discourse plugins this handled via the `.discourse-compatibility` file which you can read about here:
> [@Introducing .discourse-compatibility: pinned plugin/theme versions for older Discourse versions](https://meta.discourse.org/t/introducing-discourse-compatibility-pinned-plugin-theme-versions-for-older-discourse-versions/156971):
>
> Hey everyone wave , I just merged a new feature that will help plugins and themes pin certain versions when installed on older Discourse instances. You can now include a .discourse-compatibility file at the root of a plugin or theme repository, that designates what to checkout when installing on older Discourse versions. Rationale It sucks to remember which plugins and themes are compatible with which Discourse versions. As an admin, it should be possible to easily scan those changes and fi…
See the ActivityPub plugin’s compatibility file here:
>
As the ActivityPub plugin is still #experimental, ensuring backwards compatibility has not been a focus, nevertheless I will investigate adding explicit `3.3.2` support to that file early next week.
But as mentioned above, unless you have a good reason not to, I’d suggest using `tests-passed`.
---
_[View the full topic](https://meta.discourse.org/t/setting-up-an-activitypub-actor/314578)._