Side-effects of a "like" activity

[solid]

Side-effects of a "like" activity

[deiu]

Yes, it would be the client's job to handle these operations.

[bblfish]

I think @deiu is giving the pure example, but one could envisage others. It depends a bit on what activity streams are thought to be.

If the activity stream is no more than a log of changes to a server, not a way to make changes to the server then it would be server generated. SoLiD does not need activity streams to exist in order to bypass PUT, PATCH, DELETE, ... etc as activity pump does. A SoLiD client can do the actions directly on the resource as required by 3 in @evanp's example. So if an activity stream is just a log of the content on the web server, then it would seem to make sense to have the web server generate it, considering the web server as an agent here.

In that case one could imagine that a solid app would add a like relation by PATCHing the relevant file, and that would generate an activity in the servers or users activity stream. This would allow very generic activity streams to exist, that would show the changes to any resource to anyone allowed to view them.

I am not sure what "the list" of people who like an object is. Is that something one can find by looking at the HEAD of a resource to find a link to the official like resources?