5 ms·

As someone having an IRC client open while working since around 15 years this is so mindboggling. (Well, everything regarding the buzz about Slack and how it's

by wink 10y ago

As someone having an IRC client open while working since around 15 years this is so mindboggling. (Well, everything regarding the buzz about Slack and how it's a replacement for email, no it's the best thing since sliced bread, no wait, it's horrible.. etc.pp) Why yes, of course you need to restrain yourself from chatting all day. And learn to ignore people or tell them you're not able to talk to them right now - but it can still be immensely helpful to have your network of people available to help you solve your problems - because you're also helping them solve their problems from time to time.

gooseyard 10y ago
same story here, I don't even want to admit how long I've been using IRC. I can imagine that people who are new to using an IRC-like system in an office might lose sight of when it's right to do things in person or over the phone, but once you've got a handle on that, you ought to use the hell out of the chat system, since the more comfortable everybody gets with it, the more they're able to reduce everybody's level of distraction by using IRC judiciously. It also means that on days when you're remote, things feel mostly the same.
fiatjaf 10y ago
Since IRC was available for the last 15 years and only a handful of people used it like you, we should conclude that about the same number would do the same with Slack, all the others are just people who shouldn't be using Slack at all.
- kazinator 10y ago
  IRC dates back to 1989. I myself first compiled a client on a HP-UX 9 system and connected in 1993. IRC was relatively big because it preceded the web; it was one of the few cool, interactive things you could do over the network. That and some early networked games. MUDs, shooters like Hunt (1986), XPilots (1992?)
  - deleted 10y ago
    [deleted]
  - ams6110 10y ago
    Even before IRC there was "talk" which let you chat with anyone logged in to the same host (don't recall if it supported network chat). Remember in those days few people had a computer on their desk, instead they had a terminal that connected to a central host.
    - kazinator 10y ago
      Yes talk did work over the network. The programmers that wrote it, though, made fundamental mistakes in it. They sent raw C structures over the network without marshaling, oops! So talk didn't work very well. The issues were addresses in "ntalk".
      - alblue 10y ago
        And while talk only allowed for 2 people to communicate, ytalk allowed multiple people to talk at the same time.
        blister 10y ago
        Hey, glad you remember ytalk. I was one of the maintainers for a short period of time (I owned metawire.org and worked with Jessica Peterson on it). We depended on ytalk for collaboration to chat and share shells. Those were happier times when the internet was populated by geeks. :)
mixmastamyk 10y ago
IRC is often mentioned in regards to slack, but I find Instant Messenger(s) a bit closer in spirit. Did everyone stop using those too, in favor of facebook and slack, etc?
- 1123581321 10y ago
  Same here. We started using Slack because it was the only thing that could break the use of ad hoc AIM and Google Chat accounts. I do think that the Slack homes for user groups and open source projects (the ones set up with auto-invite on Heroku) are direct replacements for "join us on Freenode" invitations.
  - guyzmo 10y ago
    which, TBH, a nightmare, because within slack you need to change "group" to be able to be present in multiple projects, or join multiple slack-irc-server...
- mkhpalm 10y ago
  True, or Skype.
- fridsun 10y ago
  IM in a corporate setting has never really take off IMO. Email is usually the choice, which has a more mature in-house management model.
  - SyneRyder 10y ago
    I've seen Lync (Skype For Business) gain some traction in more corporate settings.
    - april1stislame 10y ago
      Why not only use pidgin with local peer discovery? No config needed whatsoever... Well, besides a user name.
  - 10y ago
untog 10y ago
"I've been doing X for 15 years, and I'm amazed that people who are new to X are finding it difficult" Is it really so surprising?

by wink 10y ago

gooseyard 10y ago

same story here, I don't even want to admit how long I've been using IRC. I can imagine that people who are new to using an IRC-like system in an office might lose sight of when it's right to do things in person or over the phone, but once you've got a handle on that, you ought to use the hell out of the chat system, since the more comfortable everybody gets with it, the more they're able to reduce everybody's level of distraction by using IRC judiciously. It also means that on days when you're remote, things feel mostly the same.

fiatjaf 10y ago

Since IRC was available for the last 15 years and only a handful of people used it like you, we should conclude that about the same number would do the same with Slack, all the others are just people who shouldn't be using Slack at all.

kazinator 10y ago
IRC dates back to 1989. I myself first compiled a client on a HP-UX 9 system and connected in 1993. IRC was relatively big because it preceded the web; it was one of the few cool, interactive things you could do over the network. That and some early networked games. MUDs, shooters like Hunt (1986), XPilots (1992?)
- deleted 10y ago
  [deleted]
- ams6110 10y ago
  Even before IRC there was "talk" which let you chat with anyone logged in to the same host (don't recall if it supported network chat). Remember in those days few people had a computer on their desk, instead they had a terminal that connected to a central host.
  - kazinator 10y ago
    Yes talk did work over the network. The programmers that wrote it, though, made fundamental mistakes in it. They sent raw C structures over the network without marshaling, oops! So talk didn't work very well. The issues were addresses in "ntalk".
    - alblue 10y ago
      And while talk only allowed for 2 people to communicate, ytalk allowed multiple people to talk at the same time.
      - blister 10y ago
        Hey, glad you remember ytalk. I was one of the maintainers for a short period of time (I owned metawire.org and worked with Jessica Peterson on it). We depended on ytalk for collaboration to chat and share shells. Those were happier times when the internet was populated by geeks. :)

mixmastamyk 10y ago

IRC is often mentioned in regards to slack, but I find Instant Messenger(s) a bit closer in spirit. Did everyone stop using those too, in favor of facebook and slack, etc?

1123581321 10y ago
Same here. We started using Slack because it was the only thing that could break the use of ad hoc AIM and Google Chat accounts. I do think that the Slack homes for user groups and open source projects (the ones set up with auto-invite on Heroku) are direct replacements for "join us on Freenode" invitations.
- guyzmo 10y ago
  which, TBH, a nightmare, because within slack you need to change "group" to be able to be present in multiple projects, or join multiple slack-irc-server...
mkhpalm 10y ago
True, or Skype.
fridsun 10y ago
IM in a corporate setting has never really take off IMO. Email is usually the choice, which has a more mature in-house management model.
- SyneRyder 10y ago
  I've seen Lync (Skype For Business) gain some traction in more corporate settings.
  - april1stislame 10y ago
    Why not only use pidgin with local peer discovery? No config needed whatsoever... Well, besides a user name.
- 10y ago

untog 10y ago

"I've been doing X for 15 years, and I'm amazed that people who are new to X are finding it difficult" Is it really so surprising?