<p>Existing implementations of Conversation Containers (<a href="/tags/streams/" rel="tag">#Streams</a> and <a href="/tags/hubzilla/" rel="tag">#Hubzilla</a>) add a context property to top-level posts of conversations. This is also what <a href="https://codeberg.org/fediverse/fep/src/commit/6ecc6957ac17d2fb6176628f572ced26ae3cd2a1/fep/171b/fep-171b.md#top-level-post" rel="nofollow">FEP-171b</a> currently prescribes.</p><p>However, as I noted in the FEP, this is not consistent with <a href="https://codeberg.org/fediverse/fep/src/commit/8d2c84a82dd1e8ff9b0f9bfa91bfa214400c74de/fep/7888/fep-7888.md" rel="nofollow">FEP-7888</a> recommendations.<br>context property is supposed to be used for grouping objects, and in Conversation Containers we have a collection of conversation activities, not posts.</p><p>A property that links top-level post to its conversation container should be called differently. For example, threadContext or conversationContext</p><p>Note.threadContext == Add.target.id</p><p>context can still be used, but for linking to the collection of posts (although I would prefer to use thread for that purpose).</p><p><a href="/tags/fep_171b/" rel="tag">#fep_171b</a> <a href="/tags/conversationcontainers/" rel="tag">#ConversationContainers</a></p>