TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Slack #threadfail

10 pointsby bradrobertsonover 8 years ago

1 comment

CaliforniaKarlover 8 years ago
I have to disagree with some of this article.<p>New stuff appearing at the top of &quot;All Threads&quot;: That intrinsically made sense to me, such that I had to try to figure out how to explain why. Here&#x27;s what I&#x27;ve come up with:<p>* &quot;All Threads&quot; is not a channel. A channel is a sequence, in which Slack decided that the newest item appears on the bottom (in the style of IRC, etc.). The &quot;All Threads&quot; view, however, is a different structure. Maybe some sort of stack? Regardless, it&#x27;s a different thing from a channel, and so deserves to be presented different.<p>* Since &quot;All Threads&quot; is placed above the channel list, when I click on it my eyes are already looking near the top of the window. Having the latest thread on top means my eyes don&#x27;t have to reposition as much to see what&#x27;s just come in.<p>Having the &quot;Also send to channel&quot; box turned off by default, combined with not &quot;re-surfacing&quot; the thread when new posts appear, is exactly what I&#x27;d expect. Assuming the thread stays on-topic, once I&#x27;ve decided that I don&#x27;t want to participate, then I don&#x27;t want to see it any more. Re-surfacing an item which I&#x27;ve already dismissed would just cause aggravation (like those annoying Windows 10 upgrade pop-up messages you could never fully dismiss). If I find that I want to check in on a thread, I&#x27;ll either scroll up for it, or I&#x27;ll search for it.<p>I agree about the lack of extra functionality in threads (like posting images and code), but I expect that&#x27;s something which Slack can work on. In no way would I assume that Slack&#x27;s implementation of threads is complete!<p>I&#x27;m kindof curious: Does the Fast Company article you reference provide hard dates, other than those from their blog and from Twitter? All the hard dates I&#x27;ve seen show 2015 as the earliest. Personally, I think that in this case, moving carefully is a good thing: Given the important role that Slack plays in many places, I imagine that breaking something (for instance, by moving too quickly) would create alot of resentment and cause people to move to other platforms. It&#x27;s a conundrum that less-popular platforms don&#x27;t have to face.<p>To Slack, I say Congratulations on their release, and I look forward to the iterations!
评论 #13462537 未加载