"Because you don't see activities of the form "Monica is no longer
friends with Dan". In fact syndicating pubicly deletes can draw more
attention to these than intended. Look at the picture she deleted ! We
dont want systems capitalizing misfortunes. This spec covers public
syndication so that is why we chose not to focus on negative actions.
Users woud hate it.
Having said that there are multiple use cases this spec does not cover
but since its based on atom we can use atom extensions like feedsync to
address."
While I fully agree that negative activities exposed to the public can be bad I am not sure that this is the right reason not to support negative values in the activtiystreams standard.
I need to look in more details into feedsync but my concern is that we might need to support multiple standards to get all social activities of a person.
Thanks for your feedback
Peter
FeedSync is a generic mechanism for communicating the fact that some
item was deleted from a feed or modified.
I think this is the correct layer to solve the problem, since then it's
agnostic of the verb and object type and it communicates the fact that
the publisher actually wants to delete something rather than simply
publishing a new activity saying that it was deleted.
To be clear, I'm not saying that these two things are different. A
feedsync delete of a positive activity does not mean the same thing as a
negative version of that activity. The feedsync delete just means it's
not in the stream anymore.
(Though with that said, if feedsync is applied to a feed of *objects*
rather than activities then a feedsync delete might be thought of as the
opposite of the implied "post" activity. But that's kinda janky.)
My concern is that I would expect to have all possible activities of a user in the standard activity stream covered. Limiting the standard based on a (very valid) specific use case seems not to be the right approach to me.