@julian @pfefferle there's a few options on what it would ideally be, but it *can* be any Object

1) group by `id`
2) possibly moderated by `attributedTo`
3) should have some collection associated with it somehow, just a flat list of everything included

the jury's out on how best to do #3 because the goal is to eventually be able to Follow a conversation. but https://github.com/w3c/activitypub/issues/486 makes it problematic to try to Follow a Collection directly...

@julian @pfefferle in terms of what kind of Object to use other than a Collection, i would say maybe don't use a Note because this is often not semantically correct. the current WIP idea is to define a `Conversation` entity that has something like a `posts` property. the thinking is that a conversation *has* a collection of posts, not that it *is* a collection of posts. this is the topic of a separate FEP though. nodeBB briefly went ahead and used Conversation before rolling it back as too early

@trwnh @julian thanks a lot for the guidance!

I think even if an object is possible, I start with the collection because of interoperability reasons.

@pfefferle@mastodon.social you're right about that. While we haven't standardized on what the collection should resolve to, existing implementations today already resolve to a Collection-style type.

Take a look at this example to see how it is done in NodeBB:

Does context have to be a collection?

@julian I am reading through the context fep and I am wondering if nodeBB only supports the context to be a collection or could it also be a post that starts...

NodeBB Community (community.nodebb.org)

(As of writing this context only has 9 items so all items are shown as is, although one could break it up into pages as needed)

@julian I think I have a working draft available in the next few days, maybe you have some time this or next week, to check it with nodeBB!?!

will send you a link when I have it deployed to my site.