@silverpill@socialhub.activitypub.rocks if recommending outbox I'd suggest also calling out the inbox for future use (follow event, in particular).

Pinging @trwnh@mastodon.social for thoughts.

@julian @silverpill what makes something a "conversation activity" or a "post", and how are these different?

to me, a "post" is "whatever you intend for the user to see". generally this is anything that has content (or summary or name), but you can also support "contentless activities" if the semantics are clear enough. for best practices though, i'd recommend the switch-case be "presence of name/summary/content".

i don't see a reason to single out Create/Update/Like for context.

@trwnh@mastodon.social @silverpill@socialhub.activitypub.rocks thread would just be simple objects, and context would be the activity stream, no?

Wondering whether this addresses concerns between 7888 and 76ea (@evan@cosocial.ca)

@julian @silverpill the main example here is a thread/context (same thing to me) of the following "posts":

- Article.content = "blah"
- Note.content = "foo"
- Note.content = "bar"
- Move.summary = "6 posts were moved to a different thread"
- Like.content = "i really like blah and thank you for publishing it"
- Announce.content = "blah makes a really good case and everyone should read it"

in the HTML version of the web page it renders exactly the same information as the LD.

@julian @silverpill I think using `thread` as a serialized version of the the reply tree is a nice first step. If people want other aspects of a conversation, as @trwnh mentioned, maybe using `context` is good, or maybe using another term.

@trwnh can we set up a time to talk through next steps 1:1? It'd be nice to consider what to do here.

@evan @julian @silverpill yeah i was about to suggest a call or something as well — i’m free basically whenever, so i defer to whatever your most convenient timeslot would be

@julian @silverpill @evan I don't think the distinction matters between "simple objects" and "activity stream", but if it did, then it would be nice for the context collection owner to signal ahead-of-time their criteria for adding.

On the sending side, what matters is whether you put `context` on the activity or not. The exact same consideration applies to any other property, including putting `inReplyTo` or `published` or `to` or even `content` on the Activity instead of on the .object

@evan I guess also if @julian wants to drop in and listen or give live feedback, then that's also fine?

@evan @julian Could also be a Special Topic Call for the Forum TF but that feels like too much formalism