@p @silverpill
>Create->ThingsBesidesNote is already present.
I am well aware. My point is that Create despite being very clear in what it does makes things harder. Because if you write your views in a way that they fetch Create activities from the DB and preload the Object, you then have to make a list of things to exclude, because not all Objects that Create works with are what you want. You probably don't want Answer objects in your timeline view for example.
So your query construction looks something like this:
If you have CreateAnswer, CreateNote, CreateDocument, your ingestion is more complicated and your builder is more complicated, but rendering timelines and stuff is simpler, because you can restrict by the ActivityType.
>Create->ThingsBesidesNote is already present.
I am well aware. My point is that Create despite being very clear in what it does makes things harder. Because if you write your views in a way that they fetch Create activities from the DB and preload the Object, you then have to make a list of things to exclude, because not all Objects that Create works with are what you want. You probably don't want Answer objects in your timeline view for example.
So your query construction looks something like this:
ActivityOr alternatively you have `restrict_object_type(query, types)`
|> restrict_type(activity_types)
|> restrict_visibility()
|> restrict_instance()
|> restrict_object_typeX()
|> restrict_object_typeY()
If you have CreateAnswer, CreateNote, CreateDocument, your ingestion is more complicated and your builder is more complicated, but rendering timelines and stuff is simpler, because you can restrict by the ActivityType.