1. 4

    I admit that I wondered what “own” was for far too long. I’m also surprised IRC came later than I thought. It should be better than it is at that late in the game. Not initially, but it should have been improved more, in my estimation.

    1. 3

      The reason IRC never got better is this: https://upload.wikimedia.org/wikipedia/commons/d/d5/IRCd_software_implementations3.svg

      The reason the Timeline lists different IRC networks is because most are not actually compatible with each other: different IRC flavors. This is why Telegram won’t open source the server—once you lose the network, you lose the future (like IRC did).

      1. 3

        Yeah, I wrote a raw IRC interpreter for a bot or a proxy once (I intended to have it used for both). It was an exercise in frustration, and knowing the edge cases and ridiculousness of the “IRC Protocol” have made me long for replacing it with something federated and open. Ah, our eternal lists of projects.

      2. 1

        Maybe “custom” would be better. (But longer.)

      1. 1

        I can see why you’d want to push tweets to slack–a permanent searchable record, easy to keep track of mentions. But it seems overly complex to respond to tweets from slack. Once you are alerted to a tweet, how hard is it to open your twitter client and respond?

        1. 5

          It means everyone has to have Twitter credentials, which isn’t even tbe main problem. The main problem is that it’s a) impossible to have a real discussion on Twitter, and b) multiple people are guaranteed to reply to same tweet (this used to happen a lot). This is why there are so many products that solve this problem with another dashboard.

          Because we already respond to Intercom from Slack, it made so much sense to add Twitter. It’s amazing to watch people respond to questions without even realizing that the response goes out to Twitter.

          We also added FB and Skype, since many companies deal with those for support, too.

        1. 6

          To learn about the hush command that lets you have covert conversations with your Slack teammates in the #twitter channels…

          The foot-shooting potential is high with this one.

          1. 2

            We’ve been doing this for a few weeks now, all day with intercom and a few times a day with Twitter – so far no instances of foot shooting. Things we say are harmless though – mentions, links to issues, hints.

          1. 2

            Version control and issue tracker: GitHub

            Email + documents: Google Apps

            Virtual Linux servers (each developer has a few): Linode

            Chat, video, screensharing: Kato.im

            1. 1
              1. 2

                None of the images in the article loaded for me. This is in Safari on an iPad.

                1. 1

                  Thanks for the heads up (fixed).