@scott For example, “inReplyTo” does not imply membership in any “inReplyTo.replies.items” if present. “context” does not imply membership in any “context.items” if present.

If the post exists in one or more contexts, then for most intents and purposes you can ignore the post and navigate away from the post and to any one of those contexts; if it is an OrderedCollection, you can render its items in a flat list by whatever canonical ordering is provided for you.

@scott But the way you render that OrderedCollection as a flat list is actually not as important as you’d think. In that sense, there is no significant difference between rendering it in the UI of social media, or of forums, or of messengers or chat rooms, or of something else entirely. At the end of the day, it’s a flat list of posts in a given order. The collection owner can hint to what they *intend* it to be, by declaring a type like ConversationContainer or TwitterMoment or whatever else.

@scott In this case, ConversationContainer might define that the collection owner is expecting you to send posts to them to be added; TwitterMoment might define that the collection owner is just curating some posts they found interesting, and that they will not be considering any posts you send them.

In the absence of a “send” or “don’t send” signal, we generally assume “send” if the context resolves to a collection with an owner and that collection does indeed contain the post (“verified”)

@scott but here’s the thing: by definition, it is generally invalid to declare a TwitterMoment as your “context”, because in reality you are not creating your post only to be considered as part of that TwitterMoment. So in most practical cases, you can generally assume that any context collection is in fact sufficiently considered a “conversational context”. Most contexts are multi-faceted in this way. https://w3id.org/fep/7888#the-different-types-of-context-and-how-they-are-actually-the-same

@infinite love ⴳ

Most contexts are multi-faceted in this way. #^https://w3id.org/fep/7888#the-different-types-of-context-and-how-they-are-actually-the-same

Yes they are. But, as I said, there are practical reasons for wanting to retrieve the conversation container (forum thread, social media thread, chat thread, etc.) as opposed to the reply tree.

The biggest practical reason is delegation of moderation. In order to limit spam, trolls, and off-topic discussions, the owner(s) of the conversation container (thread) will moderate content by removing it from the conversation container, moving it to another conversation container, or flagging it in some way.

If @julian spots a spam post on NodeBB, he can delete it. And if I retrieve the conversation container (thread) that NodeBB places the posts in, I will get the moderated version of the thread without the spam. If I parse the reply tree, I get the spam even though Julian deleted it.

It also helps keep conversations together when the forum moderator moves a post to a different thread. If you follow the reply tree, the post would appear in the wrong thread.

If you want threaded discussions to behave like threaded discussions over ActivityPub, you need to provide additional information that allows that to happen.

cc: @Evan Prodromou

@scott What you've described sounds like what I've described, and might even be mostly the same thing. Basically, if an object declares a context, and if that context is a collection, you can just navigate to that collection and start browsing its items, *ignoring the object you started with*. If it's really in the collection, the collection will tell you.

Then, if it has whatever other properties you consider necessary to be a "conversation container", you can render the collection as one.

@scott The way "post moving" gets handled is probably with a Move activity, which is both delivered to the author(s) of moved posts, as well as quite possibly added to the conversation collection in some systems. For example, Discourse will show users in the middle of a thread that "moderator moved 6 posts to other topic". This means that even if the post author never understood the Move, anyone "following their nose" has a way to get to the "new" conversational context.

@scott In any case, I recognize I've got a lot of examples I need to add to the FEP. The Move stuff probably goes in a new FEP though. Step 0 is getting implementers to recognize the concept of a conversational context at all.

There's also the *possibility* of it being useful to define a dedicated type like ConversationContainer, Conversation, etc. to hint the intention of the collection. This is also something I want to follow up on in a separate FEP.