1. 33


  1. 9

    Beautifully simple, and still more powerful than Slack.

    1. 3

      For what it’s worth you could do the same with a “Slackcat”. Or a simple curl to one of the many Slack webhooks. I don’t see how it is more powerful than Slack.

      If anything, this trick still involve running a network service written for the JVM. Not so simple when you think about it, just moves the complexity somewhere else than your scripts.

      1. 4

        With Slack webhooks, you have to manage credentials, make sure the tool runner has public internet access, encode arguments, all that stuff.

        Running a JVM network service is actually very simple, you tell your OS’s service manager how to start it and health check it (Solaris SMF could absolutely do this in 2009), just like any other network service at your company that exists only to run network services.

        1. 3

          My real gripe is, why is Slack better than this, why all the brouhaha about how slack was changing the way we work and saving the world when people have been doing this for years. Reading the comments on his blog/Reddit go further with several people with similar solutions that have been in use for years.

          1. 3

            the claim that Slack changes work was never targeted towards tech professionals – it’s about the average person, for whom chat apps were either difficult to use or had terrible UX. whether or not Slack has actually done that is a different question of course (on the whole I think yes)

        2. 1

          Still not as robust as MS Teams /s

        3. 4

          I wonder if they just use Slack like everybody else now.

          1. 3

            Wanted to work at last.fm until I saw the (2009)

            1. 1

              I see that irccloud has a reimplementation of irccat in go: https://github.com/irccloud/irccat