Live data from Hacker News

If it will matter after today, don't talk about it in a chat room

critter.blog

211–220 of 329 posts

Re: If it will matter after today, don't talk about it in a chat room

#211

The problem with "trying it with my team for one sprint" is that I now need to have a long conversation with legal. How will the service provider handle the content (discussions, screenshots, code snippets) that my team will upload? Do our current customer contracts contain any clauses that complicate the use of external discussion sites? In the unlikely event that the service offers the option to host it locally --…

Slack and all its clones are based on the chat room model, which structurally has the problem described in this article (and many others for productivity, such as wasting attention). Fundamentally, the chatroom model pioneered by IRC is poor for asynchronous communication because you can't sustain temporally overlapping conversations in a channel. However, you can't "just use email" -- Email's threading model is grea…

Something smells fishy. Oh yeah, it's your stale sales pitch.

Re: If it will matter after today, don't talk about it in a chat room

#212

Earlier quoted context omitted.

While I enjoy slack at work (not without reservations, but overall I like it), I definitely agree slack/discord are terrible for communities. I can't imagine how much discussion that even I participated in almost 15 years ago is still quickly available, would now be lost to the ether of discord and slack.

This is desirable. I like that my discord conversation will be gone in a few years. They serve little purpose being archived anyway. Old IRC logs are a horrible thing to search for help anyway. Much better just picking a forum/reddit post on the same issue which will be better sorted.

The problem is that for many communities there is only the Discord. Quite technical communities - building projects they obvious feel will have longevity.

Mozilla Hubs springs to mind but there are many more. It's become the norm. It's crazy and more people need to speak out if we're not going to lose a big chunk of a generation's tech knowledge.

Re: If it will matter after today, don't talk about it in a chat room

#213

Earlier quoted context omitted.

I prefer to right-click on e-mail and "create rule from message" from context menu. Also, the feature doesn't require any steps to configure, install or enable, it just works out of the box.

Unlike the Outlook+Exchange combination Sieve is an actual open standard (RFC 5228 & RFC 5804 & co) though that can be implemented by all mail servers and mail clients. Or is the Outlook+Exchange feature based on the same? Looking at the sieve website it seems quite a few desktop and web mail clients do have support for it either out of the box or as an add-on. So I would say that having this functionality is more on…

Exchange rules configured through Outlook are omnipresent.

Sieve might be supported by many email clients, but is pretty much nonexistent in corporate email.

Actually, if someone points me to one hosted email provider that does support it, I'd be glad - I was wondering about trying it out but nobody supports it.

Re: If it will matter after today, don't talk about it in a chat room

#214
Twist (https://twist.com) solves this problem entirely. Instead of chat rooms where everyone chats about everything, it organizes discussions around tasks. Each task gets its own chat room. When you work on task X, you chat in task X's chat room. If you work on multiple tasks, you have multiple rooms, one per task. When you come back to a task, you just open the task's room and continue where you finished. When the task is finished, that conversation is pretty much over. It's a get things done product. No useless chatting and conversations don't overlap. Go use Twist!

Re: If it will matter after today, don't talk about it in a chat room

#215

The problem with "trying it with my team for one sprint" is that I now need to have a long conversation with legal. How will the service provider handle the content (discussions, screenshots, code snippets) that my team will upload? Do our current customer contracts contain any clauses that complicate the use of external discussion sites? In the unlikely event that the service offers the option to host it locally --…

Trying to have sensible conversations in an enterprise email client, where 90% of the messages are just garbage is basically impossible for me.

Re: If it will matter after today, don't talk about it in a chat room

#216

The problem with "trying it with my team for one sprint" is that I now need to have a long conversation with legal. How will the service provider handle the content (discussions, screenshots, code snippets) that my team will upload? Do our current customer contracts contain any clauses that complicate the use of external discussion sites? In the unlikely event that the service offers the option to host it locally --…

I'm not sure what you mean by the universal availability of the email. It has the same deploy/configure/security issues any other tool has. It's even worse, because you can send email to "outsiders" unless certain rules are in place. The UX is bad and depends on email clients.

Re: If it will matter after today, don't talk about it in a chat room

#217

Earlier quoted context omitted.

I'm willing to bet money that for every company that deletes emails older than some age also deletes Slack messages, and deletes then sooner . I speak as someone who worked for a company where email got archived and then deleted after 6 months, and currently works at a company where everyone only uses Slack, and Slack is purged after 30 days.

Our email has a 90 day retention window, and Slack is permanent. We're the largest in our industry.

Do the people who wrote the email policy know that Slack is permanent? That sounds like the kind of thing that could easily be not-understood by legal.

Re: If it will matter after today, don't talk about it in a chat room

#219

Earlier quoted context omitted.

This is desirable. I like that my discord conversation will be gone in a few years. They serve little purpose being archived anyway. Old IRC logs are a horrible thing to search for help anyway. Much better just picking a forum/reddit post on the same issue which will be better sorted.

The problem is that for many communities there is only the Discord. Quite technical communities - building projects they obvious feel will have longevity. Mozilla Hubs springs to mind but there are many more. It's become the norm. It's crazy and more people need to speak out if we're not going to lose a big chunk of a generation's tech knowledge.

I just don't see this being as much of an issue as is stated here. I find that over the years its easier and easier to find info. Github issues, reddit, or stackexchange have huge wealths of info that are expanding rapidly.

Re: If it will matter after today, don't talk about it in a chat room

#220

Earlier quoted context omitted.

I’d like to see email clients offer a nice one-click “rebase on top of latest” button.

Dang. I never thought of email like that, but I wonder if email+git+UI would help for complex conversations.

Sounds a little bit like Google Wave.
Post reply on HN