A Sparkling Zombie
Once bitten, twice sparkling!
The implication I got from your #4 is that those shorter posts should be bundled into a collab because that makes it more pleasant to read. My point was that, if that's the motivation and nothing else, well, there's collaboration either way and the two methods produce the same outcome. In that case, I'd rather make the posts separately, because the interaction can still be resolved pretty quickly when a hang-up on post length is removed from the equation. However, yes, there are occasionally those players who will take their sweet time anyway, and especially in a group when timeliness is key, bundling the interaction is a solid approach then. But I'm also someone who prefers to keep IC exchanges IC. When I have to regularly discuss with someone how a single post will transpire, it starts feeling less like a roleplay to me and more like co-writing a novel. If two people find the co-writing approach enjoyable, more power to 'em of course, but if the primary motivation is because someone decided a post needs to meet a certain length, that seems silly to me, personally.The problem is the speed at which that destination arrives. And this is chiefly towards battle events or partnered team scenarios against a threat. Or that's how I use them at least. Situations in which speed or flow are at a premium. It is for the sake of others in the group, and that events such as a battle can be done within say a week or two, given all the actions for this tends to be handled inside of IC minutes to seconds. There is no reason to do them as one post at a time, *unless* those replies happen faster than once a week. I've seen way too many rp's die in that slog. Though I have also been known to give single replies when a lot is going on in said battle. I just find unfortunately most of them die during that. As the minutes turn into IRL weeks.
If I misunderstood your point, then mea culpa!