trwnhlsneff: a/v calls don't really fit into the actor-activity-object paradigm, you'd want to do that out-of-band over a different protocol, and p2p between devices rather than actors. at most, you'd have some signaling over activitypub to initiate the p2p session, similar to xmpp's jingle. but you'd have to be able to address devices and not just actors. in short, it's going to take a lot of extensions to make such a thing possible
lsneffAlso, I have a question about direct messaging. Is the plan to add a Message Activity that would hint it at it rendering in a messaging context instead of a feed?
sl007Just reposted some snippets from EUs digital flagship event. Positions in Europe at https://twitter.com/sl007 (shame on EU for not using ActivityPub for own communication)
Loqi[trwnh] @rokj sending a "private message" is a solved problem -- simply do not include as:Public in the addressing. what is not solved is how to differentiate between a post that should end up in a feed vs. a post that should end up in a messaging context.
...
sl007trwnh ActivityPub has the same addressing like email: To, cc, bcc etc. Why not bcc = only private messaging context. Did I overlook something in the issue?
trwnhreally the question is not about "how do we do messaging" but rather "how do we do feeds". because we currently assume all activities map to a single stream of activities, we've seen mostly feed-based ux in the existing fedi. and this is fine for now because we are mostly interested in the activities. conversations are a matter of context
Ariadnejejune does not use feed ux (well, we kinda fake a feed for mastodon clients, but i've kinda given up on mapping mastodon API to native AS collections and mailboxes)