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)
  • replies is now populated and responds with an OrderedCollection of direct replies (see the post about that)
  • Proper sharedInbox support
  • Better indicators for content that comes from non-local (aka “remote”) users
  • Conversational context synchronization 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
  • Kichae@community.nodebb.org
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 month ago

    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.

    • julian@community.nodebb.orgOP
      link
      fedilink
      arrow-up
      1
      ·
      1 month ago

      @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!

    • julian@community.nodebb.orgOP
      link
      fedilink
      arrow-up
      1
      ·
      1 month ago

      @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.

      • Kichae@community.nodebb.org
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        @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.