Yeah, pretty much.
angus:
I think it would be helpful to work through an example of where this particular point of intersection may become an issue.
Say you encounter an actor of type Group. You Follow the actor. You can't expect it to behave in any one particular way, but it will generally behave in one of these ways:
It is a "normal" publishing actor. You will receive Create Object, Announce Object, Like Object, and so on.
It is a boost bot. You will receive Announce Object for any object sent to it, mentioning it, etc.
It is a 1b12 actor. You will receive Announce Activity, and other activities described in 1b12.
It is a Smithereen-style actor. There will be a wall property, and it will send out Add activities where the target is that wall. The Add.object will also have a target, and this will match the Add.target as per 400e.
Bonus: It is a context moderator. You will receive Add activities where the target is the object.context. It may also additionally be a "normal" publishing actor.
So for any given "post", it might be a Create/Add/Announce/Announce-Create. This isn't limited to Group actors, but it is most prevalent in Group actors because of the popular (erroneous) interpretation of Group as equivalent to Facebook Groups. One final thing to note is that "normal" publishing actors and context moderators may be any type, not just Group -- there is no specific type dependency for these mechanisms, as they are the intended mechanisms.
angus:
So, this would result in something like:
You receive Note 2 (with context A, a collection) which is inReplyTo Note 1 (with context A)
You receive an Update to Note 2 and it now has context B (a collection)?
OR perhaps you receive an Add of Note 2 to context B?
In both 2 and 3, the inReplyTo would still be to Note 1, which would still have context A. @trwnh something like that?
Yup.
id:
type: Note
attributedTo:
context:
content: "I'm posting in a thread"
---
id:
type: Note
attributedTo:
inReplyTo:
context:
content: "This post is in a different thread but still replying to the first"
---
id:
type: Article
attributedTo:
inReplyTo:
name: "Some Article"
summary: "In which I reply to a forum post with an entire blog post. This is not part of any context."
content: "
Lorem ipsum dolor sit amet...
"
