julian on Nostr: [My post from a couple weeks back](https://community.nodebb.org/post/99512 ) ...
[My post from a couple weeks back](https://community.nodebb.org/post/99512 ) indicated that NodeBB started following part of [FEP-7888: Demystifying the context property](https://codeberg.org/fediverse/fep/src/branch/main/fep/7888/fep-7888.md ).
Our implementation is an endorsement of infinite love ⴳ (npub1t5c…ppw4)'s proposal that the context property be given additional formalization.
During the last ForumWG call, they intentionally (or perhaps unintentionally) summarized their desire that implementors should "just use collections", and that that would be a good starting point for future iteration.
With the current state of context being "there is no coordinated usage of context", this topic aims to provide a snapshot of implementors' use of that property (or lack thereof), and to stimulate further discussion on potential use cases.
Note that this is not the first time the question has been raised. trwnh's discussion topic [contained one such summary of current implementations](https://socialhub.activitypub.rocks/t/fep-7888-demystifying-the-context-property/3021/6?u=devnull ).
As per that topic:
<li><strong>Mastodon</strong> — does not use <code>context</code>, but provides an <code>ostatus:conversation</code> property</li>
<li><strong>Pleroma/Akkoma</strong> — uses <code>context</code>, but the url provided is unresolvable, likely used similarly to Mastodon</li>
<li><strong>Streams</strong> (<a class="plugin-mentions-user plugin-mentions-a" href="https://fediversity.site/channel/mikedev">@mikedev@fediversity.site</a>;) — uses <code>context</code>, resolves to an <code>OrderedCollection</code> containing all activities encontered (Creates, Updates, etc.)</li>
My hope is that a provided context resolving to a Collection (or subtype thereof) would allow for proactive topic backfill, instead of relying on [reply chain traversal](https://socialhub.activitypub.rocks/t/traversing-the-reply-chain-when-working-with-topics/4187/1 ), which while workable, has some rather specific downsides.
As mentioned per the above linked announcement that NodeBB was following FEP-7888:
<li>We attach <code>context</code> to all <code>Note</code> objects (NodeBB posts), and it resolves to an <code>OrderedCollection</code> that contains the uris to the other objects in the context (the NodeBB topic).</li>
Our implementation is an endorsement of infinite love ⴳ (npub1t5c…ppw4)'s proposal that the context property be given additional formalization.
During the last ForumWG call, they intentionally (or perhaps unintentionally) summarized their desire that implementors should "just use collections", and that that would be a good starting point for future iteration.
With the current state of context being "there is no coordinated usage of context", this topic aims to provide a snapshot of implementors' use of that property (or lack thereof), and to stimulate further discussion on potential use cases.
Note that this is not the first time the question has been raised. trwnh's discussion topic [contained one such summary of current implementations](https://socialhub.activitypub.rocks/t/fep-7888-demystifying-the-context-property/3021/6?u=devnull ).
As per that topic:
<li><strong>Mastodon</strong> — does not use <code>context</code>, but provides an <code>ostatus:conversation</code> property</li>
<li><strong>Pleroma/Akkoma</strong> — uses <code>context</code>, but the url provided is unresolvable, likely used similarly to Mastodon</li>
<li><strong>Streams</strong> (<a class="plugin-mentions-user plugin-mentions-a" href="https://fediversity.site/channel/mikedev">@mikedev@fediversity.site</a>;) — uses <code>context</code>, resolves to an <code>OrderedCollection</code> containing all activities encontered (Creates, Updates, etc.)</li>
My hope is that a provided context resolving to a Collection (or subtype thereof) would allow for proactive topic backfill, instead of relying on [reply chain traversal](https://socialhub.activitypub.rocks/t/traversing-the-reply-chain-when-working-with-topics/4187/1 ), which while workable, has some rather specific downsides.
As mentioned per the above linked announcement that NodeBB was following FEP-7888:
<li>We attach <code>context</code> to all <code>Note</code> objects (NodeBB posts), and it resolves to an <code>OrderedCollection</code> that contains the uris to the other objects in the context (the NodeBB topic).</li>