How do we handle Groups (Reconciling FEP-400e and FEP-1b12)?
-
@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
-
@[email protected] happy to publish on fedi but it doesn't necessarily have to take place within the confines of ForumWG, the group just has an interest in the outcome
-
@trwnh @julian @silverpill Conversation activity is any activity that conversation owner thinks is related to the conversation, and wants to distribute to other participants. In (micro)-blogging applications that would be Create/Update/Delete, sometimes Like, EmojiReact and Announce too (if one wants to synchronize reactions and boost counts). But in other applications these activities might be different, for example video sharing app may include View activities, and audio sharing app may include Listen activities.
-
@[email protected] @julian @[email protected] this sounds more like the kind of thing that should be discussed at a protocol level for whichever protocol is distributing such activities or objects. for activitypub that usually means inbox forwarding of as:Activity, or fetching the as:outbox. for fedi which doesn’t enforce a strict requirement that everything be an as:Activity, we generally focus on final/current state of contentful objects (“posts”) as resources
-
infinite love ⴳreplied to infinite love ⴳ last edited by [email protected]
@[email protected] @julian @[email protected] which is to say: collecting the activities is generally useless for fedi. except/unless the activities are contentful objects, in which case they become “posts”.
