Darkscribes Community

@[email protected]

> 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

@[email protected] 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.

@[email protected] 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.

@[email protected] I've gone ahead and filed a bug report, maybe @[email protected] 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...

@[email protected] 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.

@[email protected] 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

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!