Chebucto Regional Softball Club

[@angus@socialhub.activitypub.rocks](https://community.nodebb.org/user/angus%40socialhub.activitypub.rocks) will do. There has been some movement on this recently and I'd love to keep it going (and keep Mastodon in the loop). [@renchap@oisaur.com](https://community.nodebb.org/user/renchap%40oisaur.com), not to worry, I don't plan on making a PR without running it by your team first. I know these things take discussion I have my own thoughts on Jonny's reply collection backfill, although I will put those thoughts to paper later on.

Silverpill, thanks for sharing that it works. It's odd because it doesn't work with NodeBB (I woke up this morning missing 4 replies); pulling one should've gotten all of them but I had to pull them one by one (and one of [@trwnh@socialhub.activitypub.rocks](https://community.nodebb.org/user/trwnh%40socialhub.activitypub.rocks)'s still can't make it in). Sounds like an issue with me, but I'll take a closer look this morning.

Ah, that's unfortunate. When NodeBB sends a chat message out, it is just a regular Note with the recipients directly addressed, with no `as:Public` pseudo-user. So as long as PieFed handles mentioned-only notes the activity should be processed...

[@freamon](https://community.nodebb.org/user/freamon) `Create(ChatMessage)` is not part of ActivityPub. From my light research online it is something added by a Pleroma extension and possibly supported by Lemmy. NodeBB will automatically slot received non-public notes as chat messages.

[@josef](https://community.nodebb.org/user/josef) mm the whole idea is your admins should be trusted users

@Марк-Дакаскос they are not errors, you can ignore them.

> a PR to Mastodon [@angus@socialhub.activitypub.rocks](https://community.nodebb.org/user/angus%40socialhub.activitypub.rocks) I would hold off on that in favour of a PR to introduce `context` serving and consumption (a la [7888](https://community.nodebb.org//w3id.org/fep/7888)). There are still some issues to work through, but I intend to have it upstreamed (via [@frequency@frequency.app](https://community.nodebb.org/user/frequency%40frequency.app)) once we settle on a semi-final implementation.

I have updated NodeBB (`develop`, so v4.1 whenever it drops) so that it conforms with 1b12 per spec: * Only activities will be `Announce`'d * The plain object will be `Announce`'d if the activity is of type `Create`, and it is the top level post

@Марк-Дакаскос widget-essentials is packaged with NodeBB and is compatible. Its version is also pinned to the NodeBB version, so you do not need to update it unless you are upgrading NodeBB versions.

[@rikudou](https://community.nodebb.org/user/rikudou) thanks, can you file an issue on the GitHub repo? https://GitHub.com/NodeBB/NodeBB/issues/new

[@joshb@masto.2tonwaffle.com](https://community.nodebb.org/user/joshb%40masto.2tonwaffle.com) :wave2:

[@xbermusic@mastodont.cat](https://community.nodebb.org/user/xbermusic%40mastodont.cat) can you try renaming the handle to something else and back again?

[@Kichae](https://community.nodebb.org/user/kichae) the github issue is here: https://github.com/NodeBB/NodeBB/issues/13172 I think I found the source of the problem and fixed it. Try updating to the latest `master` or `develop` commit and see if it still happens.

[@xbermusic@mastodont.cat](https://community.nodebb.org/user/xbermusic%40mastodont.cat) are you still unable to find categories?

[@angus@socialhub.activitypub.rocks](https://community.nodebb.org/user/angus%40socialhub.activitypub.rocks) the other side of the coin is that Mastodon simply doesn't get the replies to a conversation, which decreases the utility of following a category, no? Rock and a hard place. Ironically this helps my case that Mastodon should implement conversational context and backfill

Hi [@xbermusic@mastodont.cat](https://community.nodebb.org/user/xbermusic%40mastodont.cat), can you check the category privileges and ensure that the `fediverse` pseudo-user has all of the privileges available to it, specifically "Find Category" and "Access Category"?

[@silverpill@mitra.social](https://community.nodebb.org/user/silverpill%40mitra.social) I think given the addressing limitations of collections, this by-proxy method of determining who to send an `as:Follow` to makes sense as a stopgap measure until ActivityPub's next version...

[@silverpill@mitra.social](https://community.nodebb.org/user/silverpill%40mitra.social) ah yes, thanks for reminding me of this. When I refactored my 1b12 implementation, I actually removed the second `Announce(Object)`, but I think I will add it back.

[@panos](https://community.nodebb.org/user/panos) brought up something interesting recently, which is that Lemmy communities don't boost everything (at least when viewed from Mastodon), but just the original post. I wasn't sure whether this was intentional (because 1b12 _definitely_ specifies that everything is boosted, replies and all). The only explanation I can think of is that 1b12 boosts **activities**, and Mastodon doesn't understand that, so it's actually an implementation quirk that causes Mastodon to not actually see the entire conversation. NodeBB used to `Announce(Note)` **and** `Announce(Create(Note))`, and it meant that Mastodon was seeing everything. This was desirable from a synchronization standpoint, but it meant everything was going into Mastodon user feeds, which was [@panos](https://community.nodebb.org/user/panos)' concern. I think Guppe (which is kind of like 1b12? Not sure) boosts everything, but again, am not 100% sure.

[@Kichae](https://community.nodebb.org/user/kichae) thanks, will have to play around a bit to see what's going on.