Overlapping taxonomies and the audience property

[jenniferplusplus1]

@julian @thisismissem It genuinely never occurs to me to use tags as a means of controlling notifications. In fact, the very idea that the sender has more control over notifications than the recipient is mind boggling.

[tedu1]

You can also just make the tag be a Collection owned by a common server actor.

[trwnh]

@julian

audience it’s not used widely, so there are limited unintentional side effects to using it.

@julian

technically there is nothing stopping a context in NodeBB from being a part of multiple audiences, our UI is largely built around them only being a part of one.

@julian

So to that end, if we were to support federated private group discussions, the audience would just be the category (with access restrictions) those objects and contexts are posted to, exactly how 1b12 expects.

I’m not sure those three things add up exactly. Having multiple items in audience sounds like by your own admission as something that would cause at least UI issues for NodeBB, and also probably bigger issues for 1b12 implementations such as Lemmy:

@nutomic

In Lemmy each post belongs to single Group which is specified in audience. Having multiple audience values would be valid according to Activitystreams, but there is no way that Lemmy could support it.

Now, this isn’t an argument against having multiple items in audience. But it is something that needs more thought before pursuing it.

For what it’s worth, I remain mostly unconvinced that the best application of audience is to list a bunch of taxonomies. I’m also not sure it should be a single Group actor. I could maybe see it being a private collection including all to/cc/bto/bcc; I could also see it being something that you copy over from the context.audience to your own object/activity audience. So I guess the next question is, how do you include or exclude yourself from an audience? If there were an actor for you to Follow or Undo Follow, then that seems straightforward enough… but addressing and audience doesn’t really follow that kind of paradigm. So something else is needed.