Ok, so TSMN is following We Distribute correctly. What about the other way around?

Very good! Replies from TSMN to We Distribute work: https://forum.wedistribute.org/topic/15/testing-federation

Let me try to start a new test topic from TSMN again.

@icaria36@the.socialmusic.network We can see your reply on our end, and it looks like the actor is showing up on our side now...

Will continue to test

Yes, but something seems to prevent that new topics are created on We Distribute by the TSMN federation... https://the.socialmusic.network/t/testing-we-distribute-tsmn-federation-take-2/471

No errors in our logs...

Ah, no, wait, still scheduled to be federated.

Mmm, topic creation from TSMN to WD doesn't seem to work.

Also, I edited the post above a couple of times, and the federated post on WD isn't being updated. For what is worth, Discourse posts federated on Mastodon are updated.

Ok, interesting but there is room for improvement.

@icaria36@the.socialmusic.network Yeah, not totally sure what's happening there. I need to get ready to go to class (Final Exams FTW), but I will take some time to debug this when I get back.

@icaria36@the.socialmusic.network I've gone ahead and filed a bug report, maybe @julian@community.nodebb.org can shed some insight on how to progress on our side. https://github.com/NodeBB/NodeBB/issues/13392

It's strange because federation with activitypub.rocks was pretty seamless, so I suspect it may have been something I did...

@deadsuperhero@forum.wedistribute.org @icaria36@the.socialmusic.network are the two of you using v4.3.1? That's the latest version, although the very latest includes some important fixes that might actually be related to these issues you're seeing.

For now I also want to make sure neither of you are using the category sync feature.

Oh, @icaria36@the.socialmusic.network is running Discourse. Well, all bets are off then

I can see this post from completely different software (Mbin), so that's cool, but I don't see replies from "social music network", and for some reason it thinks that fedimusic community is on forum.wedistribute

@fitik@fedia.io FediMusic is on We Distribute's forum. NodeBB has a sync feature that allows a category to reflect remote, federated content into it, even if it comes from different federated Group Actors.

Is this bug report related to this issue?

I did a third test, and it was unsuccessful as well: https://the.socialmusic.network/t/third-test-federating-a-new-topic-from-tsmn-to-wd/472

I have noticed that our #general category is followed by @deadsuperhero's account on We Distribute. Shouldn't there a follower by the category actor? Sorry, I don't know how the NodeBB federation works and this might make no sense.

Also, you say that federation with https://socialhub.activitypub.rocks/ (also a Discourse) works. Which We Distribute category is federating with which SocialHub category?

@icaria36@the.socialmusic.network

> Is this bug report related to this issue?

I think it might be, that's what I'm hoping to test. NodeBB upstream has a fix for this; once they make a new release, we'll give it a shot.

I suspect the fix will be: once we pull in this change, we'll be able to rescind the pending follow and resend it.

> Also, you say that federation with https://socialhub.activitypub.rocks/ (also a Discourse) works. Which We Distribute category is federating with which SocialHub category?

Just checked this, we're following their ActivityPub category specifically. For some reason, their Actor shows up as https://socialhub.activitypub.rocks/ap/actor/e9a2dbe246a6064329b37247d620bab1

deadsuperhero@forum.wedistribute.org you can use the latest master or develop branch commits if you want to try out the fix ahead of time.