[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>
julian /
npub1uq…pz8a5
2024-05-16 19:47:59
Author Public Key
npub1uq5lznmk9ax9r07mhs0lrv4qaafyguepj2spfjlw54acwkxrds3sppz8a5Published at
2024-05-16 19:47:59Event JSON
{
"id": "6bdea8a15a284a86645f0b1764b4cf0b3b870a0535b876a8e425fd5efb27957e",
"pubkey": "e029f14f762f4c51bfdbbc1ff1b2a0ef5244732192a014cbeea57b8758c36c23",
"created_at": 1715888879,
"kind": 1,
"tags": [
[
"t",
"context"
],
[
"t",
"activitypub"
],
[
"p",
"5d305da969e24116650ed7ddc87cc28df7f312a7c6aeb614e4d7eaa10cceb5ee"
],
[
"p",
"b15ffb4de55f66bbf34537c1535a3af44964f84ed062182ffe2cca3612fcbabe"
],
[
"t",
"forumwg"
],
[
"proxy",
"https://community.nodebb.org/post/99733",
"web"
],
[
"proxy",
"https://community.nodebb.org/post/99733",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://community.nodebb.org/post/99733",
"pink.momostr"
]
],
"content": "[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 ).\n\n\nOur implementation is an endorsement of nostr:npub1t5c9m2tfufq3vegw6lwuslxz3hmlxy48c6htv98y6l42zrxwkhhqkyppw4's proposal that the context property be given additional formalization.\n\n\nDuring 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.\n\n\nWith 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.\n\n\nNote 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 ).\n\n\nAs per that topic:\n\n\n\n\u003cli\u003e\u003cstrong\u003eMastodon\u003c/strong\u003e — does not use \u003ccode\u003econtext\u003c/code\u003e, but provides an \u003ccode\u003eostatus:conversation\u003c/code\u003e property\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePleroma/Akkoma\u003c/strong\u003e — uses \u003ccode\u003econtext\u003c/code\u003e, but the url provided is unresolvable, likely used similarly to Mastodon\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStreams\u003c/strong\u003e (\u003ca class=\"plugin-mentions-user plugin-mentions-a\" href=\"https://fediversity.site/channel/mikedev\"\u003e@mikedev@fediversity.site\u003c/a\u003e) — uses \u003ccode\u003econtext\u003c/code\u003e, resolves to an \u003ccode\u003eOrderedCollection\u003c/code\u003e containing all activities encontered (Creates, Updates, etc.)\u003c/li\u003e\n\nMy 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.\n\n\nAs mentioned per the above linked announcement that NodeBB was following FEP-7888:\n\n\n\n\u003cli\u003eWe attach \u003ccode\u003econtext\u003c/code\u003e to all \u003ccode\u003eNote\u003c/code\u003e objects (NodeBB posts), and it resolves to an \u003ccode\u003eOrderedCollection\u003c/code\u003e that contains the uris to the other objects in the context (the NodeBB topic).\u003c/li\u003e\n\n",
"sig": "278a2781969b14ab3ca4fe0d17bd5102235339eaef216a2cbbce71d9aa2ed12b084965f75c8d10d9eac1aaa6e20185ccebcb5e011a5385ac39ee287fd0e1c6b4"
}