When processing an activity we sometimes end up with a large number of collections that it needs to be disseminated to, both local and remote.

We need to improve the logic for this in such a way that it does not delay the response times for the Activity requests.

The current solution is to use a goroutine for both disseminating from outbox and inbox.

I would like to create a per processor instance loop that dispatches activities to collections where parallelism and retries can be done independently.

Having a single loop for this might also help with fetching remote resources (usually for validation purposes, or HTTP-Signatures) which currently is synchronous and sometimes slows things down. (see #301 for our previous issues with Friendica)