timbl, xmpp-social, ben_thatmust, vasilakisfil, timbl_ and jdormit joined the channel; jdormit left the channel
#heluecht[m]I've seen actor and "to"/"cc" as well in activity as in the object. Is there any reason to do so?
#rialtate[m]You mean the same 2 full actor objects, one expanded in activity:to and again in object:to like hubzilla? No it's a complete waste of bandwidth.
timbl joined the channel
#nightpool[m]heluecht: The client2server section of the spec mentions this:
#nightpool[m]>A mismatch between addressing of the Create activity and its object is likely to lead to confusion. As such, a server SHOULD copy any recipients of the Create activity to its object upon initial distribution, and likewise with copying recipients from the object to the wrapping Create activity. Note that it is acceptable for the object's addressing to be changed later without changing the Create's addressing (for example via an Update activity).
#nightpool[m]I think that in the sprit of that, servers that generate s2s activities should have the same audience on both the Create and it's object
#nightpool[m]re: actor. Actor is only a property of Create. On objects, it's called attributedTo.