Maybe use threaded conversations as Twitter does? Could also color conversations in the same thread, similar to how we have colorized brackets in VSCode 😄
I swear Twitter changed something about that recently (like within the last 6 months). I'm having such a difficult time following conversations on Twitter now, where I never used to.
I generally like vBulletin's model, personally. It's been about a decade, but IIRC, replying to a post wasn't particularly relevant, it would just prepopulate your response with the quoted post, and the metadata of the quote contained the link to what you were replying to. So you could use that to focus in on which portion you were replying to, and you could use it to reply to multiple posts that happened before you. (NOTE: it's also possible we had modded ours, this was before I coded)
🤔 Maybe this is what Slack needs to do, too. That model is much friendlier to time series data like Slack posts. Their current threading model is fundamentally incongruent with their chat model. Eg do you put the reply as the most recent message, or under the parent message its replying to, or in both places? (note the "also send to #channel" option) If you put it under its parent, then now people can't look at the last several messages to see what's new, how will they know about this other new thing earlier in history? (hence "Threads" in the sidebar) Maybe move the whole thread to the front of the list? Then the root message is anachronistic, or maybe put the whole thread in 2 places? Then why the thread over the reply? (they don't do this, but it would be b/c the thread is only temporally at the front, logically the thing you want to see is what it's replying to, not some irrelevant other recent message) How do I make a thread inside a thread? (you can't) What if one message is sufficient to address 3 separate comments from earlier in the thread? etc...
Aaaaand Imma just submit this now, b/c I could totally ramble on like this all night 😝
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can't reply to Quincy, but to "check canonical links" here you go:
medium.com/@brandonskerritt/how-to...
medium.com/brandons-computer-scien...
hackernoon.com/public-key-cryptogr...
hackernoon.com/how-does-tor-really...
The dev.to model of hybrid branched conversations which turn into flat chronological finds another victim 😄
I still believe it is a good system, but perhaps we need some re-thinking.
Maybe use threaded conversations as Twitter does? Could also color conversations in the same thread, similar to how we have colorized brackets in VSCode 😄
I swear Twitter changed something about that recently (like within the last 6 months). I'm having such a difficult time following conversations on Twitter now, where I never used to.
I generally like vBulletin's model, personally. It's been about a decade, but IIRC, replying to a post wasn't particularly relevant, it would just prepopulate your response with the quoted post, and the metadata of the quote contained the link to what you were replying to. So you could use that to focus in on which portion you were replying to, and you could use it to reply to multiple posts that happened before you. (NOTE: it's also possible we had modded ours, this was before I coded)
🤔 Maybe this is what Slack needs to do, too. That model is much friendlier to time series data like Slack posts. Their current threading model is fundamentally incongruent with their chat model. Eg do you put the reply as the most recent message, or under the parent message its replying to, or in both places? (note the "also send to #channel" option) If you put it under its parent, then now people can't look at the last several messages to see what's new, how will they know about this other new thing earlier in history? (hence "Threads" in the sidebar) Maybe move the whole thread to the front of the list? Then the root message is anachronistic, or maybe put the whole thread in 2 places? Then why the thread over the reply? (they don't do this, but it would be b/c the thread is only temporally at the front, logically the thing you want to see is what it's replying to, not some irrelevant other recent message) How do I make a thread inside a thread? (you can't) What if one message is sufficient to address 3 separate comments from earlier in the thread? etc...
Aaaaand Imma just submit this now, b/c I could totally ramble on like this all night 😝