Testing Federation
-
Oh, @icaria36@the.socialmusic.network is running Discourse. Well, all bets are off then
-
Oh, @icaria36@the.socialmusic.network is running Discourse. Well, all bets are off then
@julian@community.nodebb.org Yeah, I'm just trying to debug what's happening. The ActivityPub Rocks forum is also using Discourse with the same plugin, and it seems to work seamlessly without any problems. So, I'm just trying to decipher what's different here.
Edit: and yes, I'm using category sync.
-
We're testing federation with The Social Music Network, in hopes of building a collaborative community between them and ourselves. If you can see this message on the other side, say hi!
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
-
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.
-
@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...
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?
-
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 -
@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/e9a2dbe246a6064329b37247d620bab1deadsuperhero@forum.wedistribute.org you can use the latest master or develop branch commits if you want to try out the fix ahead of time.
-
hey @icaria36@the.socialmusic.network, we just upgraded our NodeBB, it looks like everything should be working now!
-
We're testing federation with The Social Music Network, in hopes of building a collaborative community between them and ourselves. If you can see this message on the other side, say hi!
Great! Let's see. Testing a plain reply here (this was working already).
And now I will create a new topic (which didn't work on your end).
-
We're testing federation with The Social Music Network, in hopes of building a collaborative community between them and ourselves. If you can see this message on the other side, say hi!
@deadsuperhero the "old" problem persists:
Testing federation of new topic with We Distribute
This is just a test that will be deleted in a few days. To discuss this testing, please go to Testing Federation with We Distribute
The Social Music Network (the.socialmusic.network)
