5 ms·

Another couple great things about slack over irc (I use irssi as well): 1. Text logs that you can grep. I've probably grepped dozens of times for ip addresses,

Another couple great things about slack over irc (I use irssi as well): 1. Text logs that you can grep. I've probably grepped dozens of times for ip addresses, conversations where I know i mentioned someone or they mentioned me, etc. 2. No deletes or edits, once it's been sent to your client there is no mechanism to retract it like there is in the browser or native client.

solipsism 10y ago
Why is 2 a plus? It was deleted/edited for a reason. It's like going through someone's trash.
- iamdave 10y ago
  This assumes all edits and deletions are done in good faith or that there wouldn't be legitimate need for persistent chat logs for auditing (chat support for instance).
  - solipsism 10y ago
    Slack group administrators can see edit history. That's not relevant, we're talking about what end users see.
    - TeMPOraL 10y ago
      Still doesn't make edits/deletes a feature. When you say something, the information leaves your control. You should not be able to retroactively edit/retract it. It's mine now.
      - solipsism 10y ago
        Why? Give a good reason for this being the case? I realize lots of people have that feeling, but no one I've encountered can back it up. It feels like the "git history should never be modified!" fundamentalists. Pragmatism always wins out in the end. In practice the editing feature is not a problem. The pros outweigh any cons. Point me to the groups of people talking about the disasters that ensued once they allowed editing?
        TeMPOraL 10y ago
        As a principle of communication. Working on a git repo is working on a shared artifact that's external to you and other developers. Retroactively deleting a message you sent me is literally like reaching out into my inbox and yanking out something that's mine now. Feels a bit different.
        solipsism 10y ago
        Yes. Very principled. I'm telling you that in practice, for the multiple large teams I've been a part of that have switched to slack, violating that principle doesn't prove to lead to problems. The benefits dominate the theoretical, academic concern. Try it!
        TeMPOraL 10y ago
        In my company we use Skype for group chat (inb4 thanks for condolences). It has the edit/delete feature which I myself use mostly for fixing typos. But sometimes I'm a minute late to a discussion and see some deleted messages that are crucial to understanding what it was about. It's mildly annoying, and I was trying to reverse Skype to get at the deleted messages. It turns out Skype does store edits in its SQLite database, but sadly blanks out the original too if edit was a deletion. I'm too lazy to be bothered to set up a monitoring service that would make a separate, append-only log.
        solipsism 10y ago
        Sounds like you have people on your team with poor judgement and people skills then. You could focus on fixing that instead. Some groups have a problem with people forking email threads. Education works wonders.
        deleted 10y ago
        [deleted]

solipsism 10y ago

Why is 2 a plus? It was deleted/edited for a reason. It's like going through someone's trash.

iamdave 10y ago
This assumes all edits and deletions are done in good faith or that there wouldn't be legitimate need for persistent chat logs for auditing (chat support for instance).
- solipsism 10y ago
  Slack group administrators can see edit history. That's not relevant, we're talking about what end users see.
  - TeMPOraL 10y ago
    Still doesn't make edits/deletes a feature. When you say something, the information leaves your control. You should not be able to retroactively edit/retract it. It's mine now.
    - solipsism 10y ago
      Why? Give a good reason for this being the case? I realize lots of people have that feeling, but no one I've encountered can back it up. It feels like the "git history should never be modified!" fundamentalists. Pragmatism always wins out in the end. In practice the editing feature is not a problem. The pros outweigh any cons. Point me to the groups of people talking about the disasters that ensued once they allowed editing?
      - TeMPOraL 10y ago
        As a principle of communication. Working on a git repo is working on a shared artifact that's external to you and other developers. Retroactively deleting a message you sent me is literally like reaching out into my inbox and yanking out something that's mine now. Feels a bit different.
        solipsism 10y ago
        Yes. Very principled. I'm telling you that in practice, for the multiple large teams I've been a part of that have switched to slack, violating that principle doesn't prove to lead to problems. The benefits dominate the theoretical, academic concern. Try it!
        TeMPOraL 10y ago
        In my company we use Skype for group chat (inb4 thanks for condolences). It has the edit/delete feature which I myself use mostly for fixing typos. But sometimes I'm a minute late to a discussion and see some deleted messages that are crucial to understanding what it was about. It's mildly annoying, and I was trying to reverse Skype to get at the deleted messages. It turns out Skype does store edits in its SQLite database, but sadly blanks out the original too if edit was a deletion. I'm too lazy to be bothered to set up a monitoring service that would make a separate, append-only log.
        solipsism 10y ago
        Sounds like you have people on your team with poor judgement and people skills then. You could focus on fixing that instead. Some groups have a problem with people forking email threads. Education works wonders.
        deleted 10y ago
        [deleted]