1. 37
  1. 7

    I didn’t know about Convos and I appreciate knowing another web frontend for IRC which is self-hostable.

    On the other hand, I keep thinking about companies using Slack because it’s what everyone uses and not because it necessarily is what they need. There is a fundamental advantage in the IRC approach: the ephemeral aspect of messages. I find it much more appealing to use IRC for (quasi) real-time communication between everyone who is online at a given time and e-mail for everything that must reach everyone on the team, must be searchable by everyone and (very important) leaves the reader the choice of when to open and when to reply.

    I feel like Slack disrupts this, without properly replacing email. So on one hand everyone is expected to be reachable at all times. And additionally the content varies wildly, from useless “hello” messages, to emojis and memes with an in-between strewn decision that affects many people. I’ve heard and been angered by statements like this in a few places: “we had a decision on this, didn’t you read the slack message from X? I’m pretty sure it was in the Y channel”.

    Overall what I’m rambling about is: sure, making IRC “permanent” can be good, but it should be a deliberate decision because it changes the communication paradigm IRC was intendent for.

    1. 19

      Except everyone who seriously uses IRC uses a bouncer and you’re back to it being a worse Slack with more steps.

      1. 7

        To add that in every company I worked for, there was a huge outrage when retention in Slack was reduced from infinite to two weeks (because security).

      2. 12

        I first used IRC when it was about 18 months old, and I can’t recall anything about its ephemeral nature being intentional or even really designed. The IRC admins who introduced me to it explained why it was great, and “ephemeral” wasn’t on the list. The people in Oulu who hacked it together weren’t great thinkers, as I recall. Not that that should matter — one of the important properties of good software is that it it can be used in ways its designers didn’t plan. I certainly can’t recall anyone protesting when the early IRC clients gained the ability to log the conversation.

        If you want to argue that being ephemeral is an advantage, you should do so in its merits, not by claiming that this was intended thirty years ago. Software is no holy sacrament that we get from holy men and have to use as they intended.

        I agree with the sentiments that a lot of people misuse Slack. But in my experience those are the same people who misuse(d) email and meetings, too, and I tend to believe that PEBKAC.

        (It is not directly relevant to this, but FWIW I’ve used both Slack and Convos for years.)

        1. 4

          I consider IRC’s ephemeral nature as a downside restricting adoption. When I open my computer, I want to see what I missed, which might include an answer to my question.

          Projects like this allow me to hope that we can push back against the bloat of things like slack with actually good IRC clients.

        2. 7

          For some reason I was hoping this client was entirely browser client-side. I guess thats not possible since the browser cannot open a generic TCP port (is this still true?). Since Convos uses a server side daemon, its worth comparing to https://thelounge.chat/ which is a fantastic self-hosted web irc client.

          1. 4

            Yes, that’s basically true. IIRC the javascript on FFOS could do it, but the javascript used in browsers cannot.

            Good thing too, or shady web pages could do a lot of fun things with the services on your local network.

          2. 3

            I recently setup a weechat relay for use with https://glowing-bear.org, but I’ll test this for a while. Really simple to setup with an existing nginx server as well.

            1. 3

              This is so cool, been looking for something like this to replace irccloud and potentially use for our internal IRC server. Definitely going to give this one a whirl!

              1. 3

                An open-source IRC web frontend that’s actually nice. Where have you been all my life!

                1. 2

                  Nice, but have you tried matrix with a bridge to IRC? It’s good enough for me.

                  1. 1

                    Has that improved much? I last tried to use the bridge about a year ago, and it frequently disconnected from freenode, usually right in the middle of the worst time (in the middle of some important discussion, etc)…

                    1. 2

                      The bridge has improved, and continues improving.

                  2. 1

                    Is there an iPadOS client for it that feels a little more native than just using it in the browser? Honestly, that’s what sells IRCCloud for me. The iPad client is the first one I’ve used that’s better than BitchX over tmux on my iPad. I already have ZNC set up… there are two platforms I use where a terminal is not a good IRC experience, and making those good carries the day for me.