NodeBB-ActivityPub Bridge Test Instance

@julian said in Lemmy and NodeBB:

Seems like a bug or restriction on their part.

Yeah, at the very least it's not how people seem to expect it to work, but a lot about ActivityPub doesn't work the way people have been accustomed to. So I can understand that.

Personally, I have complicated feelings about whether a site even should be hosting groups for non-local users. I guess I can see a use-case for such a thing, but this whole endeavour feels like it needs to be local-first to me, rather than LARPing as homogeneous centralized social media.

The difference appears to be whether the OP is on lemmy.world (LW; the site that hosts the community) or not. Posts made by LW users do not include the tag or media, while posts made by off-site users do contain the tag and media.

It's happening!

Almost everything here in the attached image is coming from comicstrips@lemmy.world, a Lemmy community (Christine Lemmer-Webber excepted). So, that's exciting! There's some inconsistencies with regards to whether the attached images are coming through, and whether community is being tagged or not, but that's just rough edges. Image-based communities aren't as much of a forum thing anyway.

I was worried that forking just wouldn't be supported on federated topics, or that if a posted was forked, it would break federation. So, this is incredible. This is what I've been waiting 2 and a half years for.

Hmm, ok. Unexpected and unintended interactions (or lack there of) it is, then. Fun!

No, I understand, it's just that I am following the group actors. I'm following the Lemmy communities from here, but new posts from them aren't arriving. I'm following the nodeBB topics from Lemmy, but nodeBB user comments aren't showing up there.

@julian said in NodeBB v4.0.0 Beta:

whether a user from lemmy.ca follows a user here

Hmm. That's going to be a big issue for Lemmy federation, then, because Lemmy doesn't even allow you to follow users, only groups. If that's the case, this seems like a deeper compatibility issue, and probably is probably more of a feature update than a bug fix.