Re: Refactoring audience targeting and activity target/origin

On Sun, Apr 12, 2015 at 10:45 AM, ☮ elf Pavlik ☮
<perpetual-tripper@wwelves.org> wrote:
[snip]
>>
>> It would require a change for folks who currently do audience
>> targeting using "to" (which is why I'm cc'ing Evan directly to make
>> sure he sees it) but overall I think the change makes sense and
>> simplifies the vocabulary overall.
>>
>> Thoughts?
> -1 mixing terms used for describing the actual Activity with anything to
> do with 'audience targeting'! I see describing an Activity and it's
> distribution / notifications as two very distinct concerns and would
> prefer to keep them nicely separated.
>

This proposal does not mix terms for describing the Activity with
explicit audience targeting. It removes the use of "to" as an audience
targeting property and redefines it as the "target", deprecating the
existing use of the "target" property name. The result is a
simplification of explicit audience targeting down to 2 proeprties
instead of the current 4 and a clearer semantic structure to the
Activity. This proposal does not conflate the two.

- James

> BTW once we iron out how to structure an Activity itself, we may need to
> rethink distribution/notifications all together, paying more attention
> to API & Federation work. Also we better make sure that tagging in a
> photo, mentioning etc. fits nicely with to, cc, bto, bcc stuff.
>
>
>

Received on Monday, 13 April 2015 16:19:27 UTC