julian on Nostr: As of today, the NodeBB-ActivityPub implementation now supplies both context and ...
As of today, the NodeBB-ActivityPub implementation now supplies both context and audience properties with every post.
*N.B. When I say context and audience, these are also terms used by the ForumWG that refer to "topic" and "category", in NodeBB parlance.*
Early indications from [the last ForumWG meeting](https://community.nodebb.org/topic/18012/minutes-from-2-may-2024-wg-meeting ) indicate movement towards the inclusion of context in a low-level as:Note object (a federated NodeBB post), resolvable as an as:Collection or as:OrderedCollection. The latter is what NodeBB will send, ordered by post time.
Discussions with [@angus@socialhub.activitypub.rocks](https://socialhub.activitypub.rocks/u/angus ) also suggest that Discourse has the ability to parse an as:OrderedCollection context if provided, but currently does not if encountered as a property in a Note.
A minor change today also updates the audience property, which used to erroneously point to the context/topic, but now points to the audience/category. This change aligns usage of this property with FEP-1b12's expectations.
This change should allow other implementors to:
<li>automatically group objects together given a the provided context, and</li>
<li>more thoroughly backfill a given object's context, without relying on <code>inReplyTo</code> traversal</li>
*N.B. When I say context and audience, these are also terms used by the ForumWG that refer to "topic" and "category", in NodeBB parlance.*
Early indications from [the last ForumWG meeting](https://community.nodebb.org/topic/18012/minutes-from-2-may-2024-wg-meeting ) indicate movement towards the inclusion of context in a low-level as:Note object (a federated NodeBB post), resolvable as an as:Collection or as:OrderedCollection. The latter is what NodeBB will send, ordered by post time.
Discussions with [@angus@socialhub.activitypub.rocks](https://socialhub.activitypub.rocks/u/angus ) also suggest that Discourse has the ability to parse an as:OrderedCollection context if provided, but currently does not if encountered as a property in a Note.
A minor change today also updates the audience property, which used to erroneously point to the context/topic, but now points to the audience/category. This change aligns usage of this property with FEP-1b12's expectations.
This change should allow other implementors to:
<li>automatically group objects together given a the provided context, and</li>
<li>more thoroughly backfill a given object's context, without relying on <code>inReplyTo</code> traversal</li>