# ActivityPub Plugin **URL:** https://meta.discourse.org/t/activitypub-plugin/266794 **Category:** Plugin **Tags:** experimental, activitypub **Created:** [May 31, 2023, 5:21pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794 "2023-05-31T17:21:52Z") **Posts on this page:** 1 **Showing post:** 394
### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus) #### Post date: [February 10, 2025, 10:26am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/394 "2025-02-10T10:26:03Z")
> [@Jagster](#): > > one account is `@ScienceScholar@mastodon.social` The reason you can’t currently follow that account is because it’s a bot. We haven’t added follow support for bots yet. > [@Jagster](#): > > Other example could be `@GetCarter@mastodonapp.uk` This seems to be due to Mastodon’s Authorized fetch being enabld on `mastodonapp.uk`. I’ll look at that again in the next day or so. > [@Jagster](#): > > If a category could follow (hash)tags from Mastodon… that would be real game changer I’d note that when you follow a hastag on Mastodon it’s only going to show you posts with that hastag that are already on the server you’re on. If there are posts with that hastag on another Mastodon server you’re not going to see them. To put it another way, Mastodon has not added primary ActivityPub support to their hastags (e.g. they haven’t made them Actors like the Discourse Plugin does for Discourse tags). See the [docs](https://docs.joinmastodon.org/spec/activitypub/#extensions-not-defined-by-activitystreams) and the discussion [here](https://socialhub.activitypub.rocks/t/user-being-able-to-follow-to-remote-server-hashtag/4277). It may still be possible to do, but it will require some kind of relaying or perhaps polling. > [@Jagster](#): > > What is this: > > discourseactivitypub::AP::Handlers::Warning You’ll need to share the message itself for me to tell you more (i.e. not just the backtrace). When you have verbose logging enabled the plugin will log failures to process incoming objects. There can be many reasons for a failure to process, many of which are not related to Discourse. The fediverse has a lot of objects flying around all of the time. I may change the log level of these failures to process to just “info” as I think they suggest to people a problem with the plugin itself when in most cases there isn’t a problem on the Discourse end of things. > [@Jagster](#): > > So I thought if that topic/message originally from Mastodon gets comments, those will be sended as replies to Mastodon. Yes, they should appear as replies on Mastodon. Specific examples are always best as I can analyse what has happened and can address anything that needs to be addressed (if anything does need to be addressed). > [@TedJohnson](#): > > Can I have a category in Discourse that shows all of the organization’s posts to Mastodon? > > [https://discourse.example.org//c/fediverse/67](https://discourse.example.org//c/fediverse/67) > > And any interactions with those posts (Favorite or Reply) on Mastodon will be represented in the Discourse posts in that category? > > And any interactions with those posts in Discourse will be visible in Mastodon? Yes, that is how the “Full Topic” setting works. See further > [@Setting up an ActivityPub Actor](https://meta.discourse.org/t/setting-up-an-activitypub-actor/314578): > > This topic covers setting up an ActivityPub Actor in Discourse with the Discourse ActivityPub Plugin. If you’re not sure what this means, head on over to the [Discourse ActivityPub Plugin](https://meta.discourse.org/t/activitypub-plugin/266794) topic first. Next Step Instructions To create an ActivityPub actor: Go to Admin \> Plugins \> ActivityPub. Click “Add Actor”. Fill out the Add Actor form (the settings are explained below). Click “Save Actor”. When you save the Actor, other Actors in the fediverse can start following it. You can disable an… --- _[View the full topic](https://meta.discourse.org/t/activitypub-plugin/266794)._