4 ms·
One thing I like about Slack-like message systems is that they naturally bottom post. However, they tend to go "asynchronous", which makes conversiarcheology ne
by thechao 1y ago
One thing I like about Slack-like message systems is that they naturally bottom post. However, they tend to go "asynchronous", which makes conversiarcheology nearly impossible. I don't understand why I can't click the message I want to reply to and have my response inserted at that point. (With an obvious: it's been too long to do that limiter.) The messages can stay inline, but having the user mark the dependency (even retroactively) could lead to some real tooling & conversation recovery improvements. I dunno; Slack has some sort of Canvas integration which I need like a new hole on my head.
- richardwhiuk 1y agoPeople already struggle to use threads in Slack correctly, adding arbitrary nesting of messages doesn't feel like it'd be an improvement.
- thechao 1y agoNot nesting: the ability (for a little while) to tell slack to locally reorder the conversation. This tends to happen with three users all trying to talk to each other: the communication is still dual, so you end up with "yeahs" and crud like that "out of place". The emoji solve this to a large extent; but, neither well nor articulately.