4/
Looking for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —
I think using "alsoKnownAs" or "sameAs" would be a poor choice. The semantics are wrong.
For example: a Service actor might represent my mobile phone (or software on it). My phone is not me. It is something I have.
So —
#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall