@eeeee no problem, what seems straightforward for me isn't always the case for others!

Below the category description, there is a bar that contains buttons for sorting the topic list. The first of those buttons controls whether you are watching or tracking the category. It usually corresponds to whether you see topics from that category in your unread and recent pages.

For remote categories, this controls whether or not you are following the category. If you are following the category, then topics posted in that category will show up in your unread page.

@trwnh@mastodon.social in general, if NodeBB discovers a group, it will create an (initially) empty category in order to house topics.

If in the course of that category's life, no topics actually make it in (i.e. if nobody addresses anything to it, nobody follows it, etc.) then it'll be pruned out as normal.

So if an as:Group contains users, and doesn't share or send creates, then it'll just be a little stub that goes nowhere, that's all.

I would be remiss if I didn't also mention that while this theoretically works with software like PieFed and Mbin, it has only really been tested against NodeBB (of course) and Lemmy.

@andrew_s@piefed.social @rimu@mastodon.nzoss.nz @melroy@kbin.melroy.org

Some interesting bugs atm

All the ActivityPub groups I was following prior to this update were successfully migrated to become remote categories (good!), but now that they are no longer treated as remote users, this has left behind a bunch of "guest" users in my /following page.

Also due to the migration, a bunch of topics that used to be categorised under @activitypub, were automatically moved to [[@activitypub](https://community.nodebb.org/category/30/activitypub )@forum.wedistribute.org](https://community.nodebb.org/category/activitypub@forum.wedistribute.org )!

I presume this happened because [[@activitypub](https://community.nodebb.org/category/30/activitypub )@forum.wedistribute.org](https://community.nodebb.org/category/activitypub@forum.wedistribute.org ) is set to mirror @activitypub. I'm guessing that since the group actor was sharing all these posts, once NodeBB recognised it as a remote category instead, it began to treating those share activities as move actions.

Seeing how NodeBB does not have a notion of topics belonging to multiple categories, you might want to revisit how you handle remote categories that follow and mirror local categories.

@AltCode thanks for reporting! I'll take a look at those tomorrow.

The topics being moved out is a byproduct of the migration. Looks like some tweaking is in order! Perhaps I'll only move topics whose main post is on the same domain.

@AltCode I've moved those topics back to the proper category

Edit: updated as had to click into category to follow

@julian@community.nodebb.org

I can confirm it works with Mbin, look at my instance: https://kbin.melroy.org/m/activitypub@community.nodebb.org/p/286459/Happy-Tuesday-Today-we-ve-updated-the-NodeBB-community-forum-onto#post-comment-413326

@julian @activitypub Makes sense. Were NodeBB's own federated categories represented as users prior to this change? Do you assume that all groups are FEP-1b12 groups?
There was an interesting discussion on SocialHub on identifying FEP-1b12 groups and nutomic made a compelling argument that we should just assume that Group supports FEP-1b12 if there is no other indicator:

FEP-1b12: Group federation

Internet forums are probably the oldest form of social media. They can be implemented with the Activitypub protocol, but such implementations may not necessarily be compatible with each other. This document defines a com…

SocialHub (socialhub.activitypub.rocks)

@AltCode the two bugs you identified have been resolved, can you confirm the latter? The former I manually moved them back already to the right category.

Confirmed working with:

• PieFed Communities: PieFed Meta
• Flipboard Magazines: [Gear by @engadget@flipboard.com ](https://community.nodebb.org/category/gear-engadget@flipboard.com )

However, while Flipboard magazines send Announces as per 1b12, and the items are added to the outbox, the objects themselves do not address the magazine at all, and so a backreference is missing. When they come into NodeBB, there's no pointer back to the group, and so it is slotted into the "uncategorized" bucket.

cc @mike@flipboard.social

tl;dr — can this object https://flipboard.com/users/Engadget/statuses/uva9misBSrqjCSR6mtzV6g:a:3199686 please include https://flipboard.com/@engadget/gear-nv6v86arz in its to or cc property?

@julian Yes, I can confirm that the other bug has been fixed! There's no more guest accounts in my /following page.

@julian not sure. Cc’ing @jaonculverhouse

@silverpill@mitra.social I read back a bit to get a fuller context (not all the way, though, there's a damn lot of bikeshedding in that topic.)

Basically Nutomic is advocating against multi typing because it is poorly supported (true), and because Lemmy has first-mover advantage (also true.)

Requiring a multitype or boolean flag for 1b12 would be quite difficult to do because you'll never have 100% adoption and end up needing backwards compatibility with 1b12-classic anyway — cat's already out of the bag.

@scott@loves.tech can you share an example of a group actor from Hubzilla? Would be interesting to see how that's handled. Likely it wouldn't work properly because categories in NodeBB don't author posts.

Do your group actors send creates on behalf of regular users? That might work ok.

Lastly, there's no requirement that a NodeBB category be mentioned. It only needs to be addressed. A mention is the easiest way to do that because you addressing is abstracted out of the Mastodon UI.

But for things like PieFed, Lemmy, Mbin, and likely Hubzilla, you're able to change addressing based on where you create the post.

But for things like PieFed, Lemmy, Mbin, and likely Hubzilla, you're able to change addressing based on where you create the post.