Last friday I quietly tagged a commit on the activitypub branch with v4.0.0-beta.1, which signals that the ActivityPub integration is now ready for beta testing.
For the most complete (yet readable) list of new functionality from the alpha, check out the “Road to Beta” project page.
tl;dr — some new features and a lot of fixes
- Editing a category now issues an
Update(Actor) repliesis now populated and responds with an OrderedCollection of direct replies (see the post about that)- Proper
sharedInboxsupport - Better indicators for content that comes from non-local (aka “remote”) users
- Conversational
contextsynchronization mechanic (corresponding post for that) - Moving a topic out of the “uncategorized” category will now federate out an
Announce
By and large most incompatibilties have been resolved, although if you do find some issues, please do let me know in the corresponding bug report thread.
I’m looking to wrap up the year with some of the more difficult projects I’ve put off
- Object Integrity Proofs, which will also enable Inbox Forwarding
- Better handling of “Open in App” signals from third-party instances
- Post visibility support (or at least better handling so non-public messages aren’y unceremoniously dropped!)
- Ongoing integration with FEPs 400e and 7888
I’ve been playing around with community.nodebb.org, in anticipation of 4.0’s launch, and I’ve noticed that the Lemmy groups I’ve followed don’t appear to be showing up. I can see posts from Mastodon (and whatever else) users that I’ve followed in World, but not Lemmy groups.
Is this expected or intended? Following nodeBB topics from Lemmy has worked OK, so I thought it would be bidirectional.
Though, now that I’m comparing this post on lemmy.ca to that on the mothership, I see that replies from nodebb.org users aren’t showing up on the remote instance, either. Just those from off-site users. I’m caught somewhat off guard by that, too. Is that behaviour expected?
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.
@[email protected] whether replies from here appear on lemmy.ca depends on whether a user from lemmy.ca follows a user here. Perhaps that isn’t the case? (Hopefully you see this reply now 😅)
Still need to debug Lemmy federation. Might be a regression.
@julian said in NodeBB v4.0.0 Beta:
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.
@Kichae @[email protected] That’s an issue with all software federating via ActivityPub. If there isn’t an existing follow relationship then the content isn’t pushed to that user.
That’s greatly simplifying it, of course. There’s quite a bit more that actually goes into how it works.
In the case of the referenced topic, NodeBB automatically boosts replies that it receives from the category actor. When replies are made by NodeBB users, they are also addressed to everybody who has participated in the topic.
So given that, lemmy.ca should have received everything, at least since you started posting in it. In reality, there might be a connection issue between NodeBB and Lemmy, and that’s what I’d want to verify first.
Hmm, ok. Unexpected and unintended interactions (or lack there of) it is, then. Fun!
Edit: This comment, FWIW, showed up in Lemmy right away. So, whatever the issue with on-site comments not federating out seems to have been resolved. If no active intervention was taken, it may have been an issue with Lemmy 0.19.3 (lemmy.ca just updated the other day to 0.19.7, IIRC), or it may have just been federation queue issues.
Edit Edit: I love that federated comment chains can be forked without breaking federation. That’s awesome.
@Kichae With regard to some responses showing up and others not, it seems Lemmy does not process activities for communities if it has no followers.
So let’s say you search for a remote community on Lemmy and make a post to it, and it crosses over to NodeBB. If that community has no local followers then even though you posted to it, any replies will not be accepted by Lemmy.
Seems like a bug or restriction on their part.
@julian said in Lemmy and NodeBB:
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.
@[email protected] image attachments should be better handled by NodeBB now
@Kichae the forking is local only. There’s no standard way to communicate a fork action across to other instances.
We’ll try to be pioneers and come up with a way though!
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.
Lemmy only supports following group actors. So, Lemmy communities, gup.pe groups, PeerTube channels, NodeBB topics, etc. If NodeBB’s federation is reliant specifically on following users, that represents a fundamental difference in the federation models between the platforms.
@Kichae said in Lemmy and NodeBB:
At least in my limited (and definitely not exhaustive) testing, bi-directional posting does seem to work.
@Kichae no the group actors are fine too. We implement the same sharing system that Lemmy implements.
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.
@Kichae yeah let’s say a topic is forked in NodeBB. The baseline expectation is that federation doesn’t break, but the ideal is that the fork is also federated so Lemmy (for example) would also fork the topic on their end, so it looks the same on either end.
Something we’d want to work on with ForumWG (specifically @[email protected])
It’s happening!
Almost everything here in the attached image is coming from [email protected], 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.
@Kichae hmm they ought to work the same though, so inconsistencies should be addressed. Thanks for letting me know. I’ll take a look today, time permitting.