I added some additional text from the newsletter to the title field, to call attention to the bit that people might be interested in.

What I’m excited about is that they seem to be designing groups in a way that properly connects the Threadiverse to the Mastodon/ microblogging side.

This release also lays groundwork for federating groups: starting with better interop with remote groups and threadiverse apps. Federated groups remain our biggest priority, and we’re designing them in the open with the W3C groups task force.

The next step for groups is opening public groups to the wider fediverse, compatible with how some apps already federate groups. People on Lemmy, PieFed, Mbin or NodeBB will see a Bonfire group as a native community in their own app, where they can join, post, and reply the way they already do, while on Mastodon and similar apps a Bonfire group will behave more like the discussion groups you may know from FediGroups (and previously Guppe): follow the group, mention it to post, and all posts in the group reach your feed as boosts.

Alongside that, we’re working on moderation tools made for groups whose members arrive from across the network: one inbox for group moderators to review join requests, posts awaiting approval, and flags.

Private groups and the full cross-instance group experience will come later, because they need interoperable specs the fediverse hasn’t agreed on yet. We’re actively doing our bit to push that forward, drafting proposals from our implementation experience in the W3C groups task force mentioned above.