Hi @silverpill@mitra.social right;

1. Move and Remove are explicit actions concerning membership of a context in an audience.
2. Update is overly broad and receivers would have to infer audience change based on what the updated object contains (e.g. Audience Y is suddenly missing, and Z is new, was this always the case?)
3. It is likely that sending audience as an array will not be correctly interpreted by existing software, so this property is an unreliable indicator of context audience membership at best
   • Existing threadiverse apps check addresses, and audience may not be used at all in some.

There is no conflict with Move(Person), and I have not heard a convincing reason to adopt a new activity type when these two AS activities work quite well to describe what we want to accomplish.