Live data from Hacker News

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

critter.blog

261–270 of 329 posts

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

#261

I disagree with the conclusion of the article. Using this logic, one could say that you shouldn't speak about long term projects during voice call meetings. I agree that the quality of conversation drops when speaking over chat, but I would also say that communication increases. In my opinion, the increased communication more than makes up for the decline of message quality. I also feel that the author of this articl…

200% agree. First time I've ever really felt young on HN before. People still waste time with internal email?

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

#262
post #145

Earlier quoted context omitted.

Zulip really hits the sweet spot for a communication tool. Especially with large amounts of users communicating across many different threads. The FHIR community "chatroom"[0] is a Zulip server and is indispensable for communication and knowledge building across thousands of users. [0] https://chat.fhir.org/#

I signed up for that to see what Zulip is like, but there are only 19 messages visible if you do that, so I shouldn't have bothered. It seems nice, I guess.

New users on Zulip instances get 20 unread messages by default – I guess you marked one read. The full history is available to you.

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

#263
post #166

Earlier quoted context omitted.

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…

We've been using self-hosted Zulip for about 18 months now, and it's exactly what our company needs. I have been recommending it right and left to people who don't need federation in their chat system. If there was a clear gateway to federation -- enabling a Matrix room as a Zulip Stream, for instance -- I would enthusiastically recommend it for everyone.

You can also use something janky like matterbridge to link with other things (poorly). Depends on your use case for federation.

https://github.com/42wim/matterbridge

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

#264
post #220

Earlier quoted context omitted.

Sounds a little bit like Google Wave.

Wave seemed to me to be an unimaginative copy of other threaded comment implementations. The indentations seemed to waste valuable space on each page. Allowing anyone to edit anyone’s post seemed insecure. If I hadn’t known it was Google, I would’ve thought it to be a bad college project.

> Allowing anyone to edit anyone’s post seemed insecure.

Insecure in what manner?

To me it's no more insecure than a VCS - sure, anyone could edit anyone else's code, but version history was always there.

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

#265

Earlier quoted context omitted.

>I'm a Thunderbird user, but I don't really think that there's a clear winner in that comparison. Outlook has features that Thunderbird has been missing for over a decade, like reliable send-in-background (and other database operations in background unlike Thunderbird that likes to interrupt you to ask permission) and a far more mature calendar product. A fair point. As someone who has used both Outlook (professional…

I tend to really harp on send-in-background because I view it as a core feature of an MUA, but as far as I know it's still hidden behind an about:config flag in Thunderbird because it has an excessive number of known bugs, and it's been this way for many years. Another ongoing pain with Thunderbird is the inability to switch between HTML and plaintext when composing a message. Outlook lets you do this, in Thunderbird…

Outlook.com and the current version of OWA in Microsoft 365 are nearly the same. What are you still missing? (If you’re on-prem still, you’re probably running a much older version)

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

#266

I disagree with the conclusion of the article. Using this logic, one could say that you shouldn't speak about long term projects during voice call meetings. I agree that the quality of conversation drops when speaking over chat, but I would also say that communication increases. In my opinion, the increased communication more than makes up for the decline of message quality. I also feel that the author of this articl…

> advance search features

These are only useful if the chat content is suitable for search. Searching human conversation is much different from searching content crafted for long term usage.

Also, there is the problem of what to search for. Many meaningful discussions may be lost in conversations that do not explicitly mention the topic but build upon the context.

Great many ideas can be expressed in a few words and these may not be searchable.

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

#267

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.

Have your Slack chats been subpoenaed yet?

If not, you are very lucky that you are being sued by people with incompetent attorneys.

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

#268

Earlier quoted context omitted.

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.

Yeah this policy mismatch definitely seems like a "nobody in legal has noticed yet".

They're gonna notice real quick the next time they get sued by somebody clueful enough to subpoena that goldmine.

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

#269

Earlier quoted context omitted.

I get that you're just trying to get your software out there, but your modern features that email doesn't support are just wrong. >shared history Not if you have a mailing list, and then going off the record is as easy as removing the mailing list from the CC field. >markdown formatting This is an implementation failure, not really a fundamental problem with email. There is no reason that email clients don't support…

This. I mean I get that there are various different chat or chat/email hybrid solutions nowadays that are competing with each other. Personally though I have nothing to complain about with slack. It has threading. It only has one level threading but that might actually be a good thing because we slack with non tech people too. One thread is sometimes hard for them to grasp. Make that a regular threading model and the…

> It only has one level threading but that might actually be a good thing because we slack with non tech people too. One thread is sometimes hard for them to grasp. Make that a regular threading model and they will utterly get lost

Off topic, but this astounds me.

Not trying to be elitist (I'm genuinely curious), but what is it about threads that throws them off?

They seem unrelated to software. I would have thought "non-tech" people would also understand them.

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

#270
I haven't yet seen anything better than NNTP (the protocol of Usenet) and a decent news client, which used to mean tin on Unix and MT-NewsWatcher on MacOS. We used to have patches and CVS commit messages on code review groups and fork discussions seamlessly into dev groups. Mailing list email to NNTP gateways allowed ready collab with workers outside the group. Common NFS share allowed easy joint work without huge amount of code & build duplication. And it was possible to just grep every message in the News spool.

This was much better than Slack + github + email + Confluence + Teams + file shares + SharePoint -- no one knows where anything is or which chat system a conversation was on. Searching Slack is a fool's errand.

I attribute the failures of these systems to be their reliance on the pattern of centralised SQL+httpd+templated crud+js vs federated standardized exchange+text.

In modern web apps the client is embedded in the app by its very nature, and so the proprietary nature of each system makes community contribution impossible.

Post reply on HN