I wonder whether it’s related to the fact that, even after re-following and getting listed here, I didn’t see this post, made about an hour ago, show up in my mastodon feed:
[Edited] Similarly, I didn’t get any of the 30 July 3.2.5, 3.3.0beta5, or 3.3.0 release note announcements from announcements either, even though I do show up in the list of followers.
Angus, when my post goes to mastodon, people respond and the post appears on my forum. But is it not possible to respond to the person who responded to me, directly through my forum?
Hey David, it should be possible to do that. Please check your logs for any warnings when the reply is made. It’s also possible Mastodon isn’t accepting it for some reason.
Sorry Angus. It was worked fine now.
and sorry for asking that, but do you have any news about the adaptation with Lemmy? I’m very anxious for this
I’m glad it’s working.
Full Lemmy support is on the agenda, but I don’t have an ETA for you at the moment. I’ll let you know.
Thank you. I just checked it one more time, its publishes the post from my forum to Mastodon, but its dont tag correctly:
So I guess the person doesn’t know they’ve been answered?
Hi there. Congratulations on the release of the ActivityPub plugin.
I am having some issues though. I recently set up a new Discourse site on a new server and installed the AP plugin. All up-to-date with the latest versions
I have set up the actor for ‘General’ category, and it is enabled.
On Mastodon, I can see the account @general@forum.39.ie but when I go to ‘Follow’ it and refresh the page, it indicates that it is waiting to be accepted as a follower (like a Private Profile)
The account doesn’t appear in the ‘Followers’ page within General category > Federation
In the logs, it shows the following:
[Discourse Activity Pub] POST request received by https://forum.39.ie/ap/actor/899d0b715d05d8360ff7fcb114c9c818/inbox failed: 401 Actor not found for key https://mastodon.ie/users/padraig#main-key
Whenever I post in the General Forum and wait the 5 minutes, the AP logo still has a strike through it stating: “Note was not published via ActivityPub.” even though that AP is enabled.
It gives me the AP link https://forum.39.ie/ap/object/22b6a43c4d8ff6347360fa332ffffacf
Within the logs, I do see the following:
[Discourse Activity Pub] GET request received by https://forum.39.ie/ap/object/fb7a31ae2fd15df4ee8a46644d4dbebb failed: 400 Bad request
[Discourse Activity Pub] https://forum.39.ie/ap/actor/899d0b715d05d8360ff7fcb114c9c818 failed to schedule https://forum.39.ie/ap/activity/1e68cf435ea927f3d828bc9f063f8bad for delivery: no recipients
Which would make sense, no point in publishing if no one is following, but if I can’t follow the category successfully.
Have I perhaps missed a step, or would something be getting in the way?
If there is anything else that is needed, please let me know. 
Is there still a federated stream from any meta tag/category available? The handle @feature… does not seem to work anymore? (Or has anybody a good alternate discourse instance publishing a feed for test purpose)
That should still be working, yes. The handle is feature@meta.discourse.org and I see it in my Mastodon instance:
There is also announcements@meta.discourse.org, that should be working as well.
I found the handles and the Federation tab but when I use the “go to profile” in the Mastodon search result on my own server it prevents a 404 (strange enough against my own server). Normally the search redirect works - will try later with some better diagnostics - what’s the expected profile url on meta?
I didn’t see yesterday’s announcement in my Mastodon timeline either. So the problem persists. Are logs still around to investigate why it is broken for me?
The release note announcements don’t get published automatically because we write them in a shared draft and that process doesn’t work out-of-the-box with the AP plugin. It is a known limitation.
I manually scheduled publishing for a few topics now, just to make sure that the rest of the integration still works.
So I’ve still never seen any posts at all from either @feature@meta.discourse.org or @announcements@meta.discourse.org even thought I unfollowed and refollowed.
I looked into the problem I’m seeing a little more. I followed @feps@socialhub.activitypub.rocks and it gets all three levels of domain and displays the follow properly.
Whereas it is still broken here on meta:
I still have seen nothing from following @feature@meta.discourse.org
So it looks like whatever is breaking meta is specific to meta, but it’s definitely broken.
In case it helps for looking at logs, I again “tried turning it off and back on again” by un-following and re-following both federated categories. It still shows the wrong name for me. Because this doesn’t affect me on socialhub.activitypub.rocks I’m guessing that this is a data bug from me being one of the earliest adopters of trying to follow here in the first place, so I have a broken entry in the database on meta.
@pmusaraj I don’t suppose someone at CDCK could rails c and fix this up, since “turning it off and back on again” failed to solve it?
@JammyDodger - you don’t think that this might be due to some of the settings that were changed with our testing last week?
Hmm. I don’t think so. But I have trashed a few settings by accident more than once so it’s probably worth a check…
Everything seems to be in order for feature, from what I can see. 
I’ll have a look with fresh eyes in the morning and see if I’ve overlooked anything.
I’m reasonably confident that our work with the pavilion federation didn’t touch any existing setup.
This isn’t recent in any case. It was late July when I unfollowed and refollowed the first time.
I followed from @mcdanlj@mastodon.cloud and do see @feature@meta.discourse.org content in my timeline there, but the same post is not visible in my @mcdanlj@social.makerforums.info timeline. Hopefully the difference between those two follows can make it clear what the problem is?
Why is this the case, out of curiosity?
It feels like it’d make more sense if every Discourse user was an ActivityPub actor, and forum categories were ActivityPub groups that reposted each user’s posts in that category. This is also how Lemmy works, I believe.
Right now if I follow a category on Mastodon there’s no indicator of who posted what, which is pretty undesirable for my community because anyone on the internet can post arbitrary content to an official looking ActivityPub account on our domain.
