@julian@community.nodebb.org could not run it in dev mode directly because of docker compose, but did set NODE_ENV to development and got verbose logs. Only thing that shows up is:

2025-05-03T19:35:59.553Z [4567/53] - warn: Route requested but not found: /category/activitypub@community.nodebb.org

So, this URL does work: https://forum.agnos.is/category/nodebb-development@community.nodebb.org

Maybe it has something to do with the activitypub category being a sub-category of nodebb development?

@projectmoon@forum.agnos.is no, that didn't matter. There is no concept of nested categories in ActivityPub yet.

But the issue seems legitimate, I can't access the ActivityPub category from a test Mastodon server either.

@julian@community.nodebb.org I was able to access it from a Lemmy instance. So it is federating, at least partly. But interesting to know that Mastodon has issues with it...

One thing that might be helpful is that NodeBB gives an invalid ID error when trying to follow the category via the sync function in admin settings. Stack trace shows it's the error being thrown when trying to follow (activitypub.js line 43).

@projectmoon@forum.agnos.is thanks, can you try again? For whatever reason the handle-to-cid association was lost, and I'm not sure why. I've manually restored it now.

Yep, shows up now on my end. Maybe check other categories too?

Were there other categories breaking?

@julian@community.nodebb.org Yes, maybe? https://forum.agnos.is/category/bug-reports@community.nodebb.org for example. Maybe it's not federated? Since I don't see anything about what fediverse handle to use like in the ActivityPub forum.

That's correct, that category wasn't federating, but it is now

@julian@community.nodebb.org Cool, I can now load it. Another question: I have a bunch of lemmy communities (and also a few "null" entries) stuck on "pending" in the category synchronization settings. Pressing remote/delete doesn't do anything. Is there an easy way to get rid of them by editing the database?

Also, are there plans to merge the federation synchronization and new remote category following stuff together into one cohesive set of functionality?

@projectmoon@forum.agnos.is said in Updates to the world page:
>
>
> Also, are there plans to merge the federation synchronization and new remote category following stuff together into one cohesive set of functionality?

Yes... the remote category functionality supercedes the category sync functionality in some ways, but there is still a use case for it.

Most likely I will need to develop proper support for cross-posting (at least locally), and that would work well with the remote category functionality, so that topics are cross-posted to the synchronized category, instead of moved.