5 ms·
One of the many downsides of "top posting" that I didn't see mentioned is when a given email including quotes is taken as the history of the email thread up to
by neilv 1y ago
One of the many downsides of "top posting" that I didn't see mentioned is when a given email including quotes is taken as the history of the email thread up to that point, but it's missing emails (because of concurrency with possibly multiple replies going on at once, and because of cherry-picking or randomly-picking which subtree to respond to).
Even in a back-and-forth between 2 people, there are some people who'll reply a second time to the same email, not to replace their earlier response, but to add more information.
(Aside: Also, it seems to be rare for people forwarded a top-posted thread context to actually read it, unless they're looking to assign blame.)
In every company, I end up having to reconstruct context for someone, or do archaeology on some interaction, and the top-quoting both helps and hurts.
Downsides of lazy top-posting for these purposes include having to break out all those messages, and fill in the gaps from maybe multiple copies at different points.
Upsides include when, say, a single email is the only record, and the fact that a bunch of people top-posted means you have more raw information, in the quotes, than if that single email was in a history of people doing proper Netiquette with minimal quoting of the parts they were responding to.
There are a whole bunch of reasons and implications for how things are done in corporate practice, and IME most of them come down to one of: poor tools, poor use of the tools (including by "digital natives"), and corporate misalignment + politics.
- thechao 1y agoOne 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.