Live data from Hacker News

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

critter.blog

221–230 of 329 posts

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

#222

Earlier quoted context omitted.

So, you're worried about this > 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? Yet you suggest using email where it basically goes (or can be coerced to go) across the internet in plain-text where anyone can read it?

For email that conversation probably has taken place already. Also, lots of larger orgs have internal mail servers where this isn't even remotely true.

Orgs have internal chat servers too.

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

#223
post #27

Earlier quoted context omitted.

Many organizations seem to use Outlook/Exchange and configure Exchange to make it difficult to use other mail clients (not enabling imap, not enabling caldav support so that a separate calendar and email client need to be used unless you use exchange, etc). Outlook is truly awful as a mail client and it would make one want to use anything else.

Is it really that bad? I'm just a dumb machine operator that uses Outlook at work, Fastmail for myself, and Gmail because I'm an idiot too, and really can't tell the difference.

In terms of experience using the product, I feel the Fastmail client handily beats both outlook and gmail.

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

#224
post #223

Earlier quoted context omitted.

Is it really that bad? I'm just a dumb machine operator that uses Outlook at work, Fastmail for myself, and Gmail because I'm an idiot too, and really can't tell the difference.

In terms of experience using the product, I feel the Fastmail client handily beats both outlook and gmail.

I agree, it's the user experience I notice the least. It doesn't get in my way at all, and I don't recall it changing or if it has the changes have been so mild and consistent I haven't noticed.

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

#225

Earlier quoted context omitted.

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.

I'm talking about communities with very little other material footprint. Nearly all discussion is on ephemeral platforms. There are no other knowledge bases to refer to.

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

#226

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 --…

There is really only one fundamental problem with email: its mechanism for managing who takes part in the conversation is all wrong for team communication. The symptoms of this problem are myriad: reply-all storms, cya-by-cc, replying to a 5 month old email rather than starting a new thread, fyi forwards, etc. Which isn't to say that all the advantages you list for email are not true. They are. It's just that most pe…

I can't speak to how good or effective it is, but the issues you mentioned are, I think, why the rust-lang community communicates through Zulip (instead of email, IRC, etc).

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

#227

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.

It kind of does: https://public-inbox.org/README.html It's used for LKML (and many other lists) archives: https://lore.kernel.org/lists.html

(but it's read-only, there's no rebasing, people still use old-school e-mail clients)

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

#228

Earlier quoted context omitted.

> I have always thought that Slack is designed to make information go away, and that's why people like it. I think it's exactly the opposite?[0] People like it because, except for the free plan, you can find anything that was ever discussed. [0]: https://slack.com/pricing

This is exactly why at my org, slack is one of the de-facto sources of truth. And it's awesome. I can often find the solution to a specific, niche problem that someone else discussed 4 years ago in a few seconds. Assuming your org pays for whatever it is that allows full archival, it's a great way to capture org-specific, tribal knowledge that you won't find on google, but that nobody will take the time to add to an…

Teams is built by boomers, for boomers

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

#230
This is actually about half of the business plan for companies like Slack. They want you to start using it on the basis it is ephemeral and then end up forced into paying for it because its just impossible for people to self-enforce that behaviour and not put information in there that needs to be retained.
Post reply on HN