1. 13

    Classic Mozilla-style decisionmaking:

    Hey everybody, we’re going to be deprecating our thing in a few months. Not only are we not at the point where we can begin proofing the thing we’re going to replace it with—and then going to spend the intervening time doing exactly that—but we actually have no idea what the replacement is even going to be.

    (FWIW: I hate IRC.)

    1. -1

      inb4 slack

      1. 9

        Worse - Discord.

        1. 2

          Please note that the Rust project was not involved in any decisions and is also not part of any evaluations. (We also didn’t want to)

          We were just pre-informed and still have 2 active community channels and a working group there.

        2. 4

          Half the company already uses slack. The other half still uses irc. It’s maddening. Any given solution will be better than the current situation.

      1. 30

        I object to the historical tag. I use IRC on a daily basis. (In fact, it’s how I keep in touch with most of my social circle)

        I do think that the most important thing IRC could do is implement server side history, which solves the main issue: catching up on history after joining a channel or going offline.

        Everything else feels like fluff.

        1. 22

          On the other hand, I consider lack of history a feature, a highly desirable feature.

          I don’t need to be notified of everything that happens, I don’t need to know all of the history.

          IRC is like walking into a bar. If there’s an interesting conversation, you jump in. And when you’re away, if something important happened, someone else will fill you in. Otherwise, it wasn’t important.

          Just miss out without fear. It’s okay. Do other things.

          If you need persistent and slow communication, use a different protocol, but leave chat protocols as ephemeral and forgettable.

          1. 5

            This is not usually how IRC is used in practise. In practise people use bouncers or “irssi in screen forever” to get the history client side. Better to let the protocol solve the problem most people seem to want, and if you don’t want history configure your client not to fetch or show it.

            1. 6

              I don’t know how usual this is. Lots of people don’t use bouncers. Some use bouncers. The way we use #octave in Freenode is memoryless; #emacs in Freenode has a no public-logging policy (just a politeness convention) and #mercurial in Freenode also has people coming and going all the time. If something happened and people are talking about it, I ask in #mercurial and people will give me the context. Nobody has ever said to me, “get a bouncer, ya n00b!”

              I don’t know if most people want persistent history but I certainly don’t.

              1. 3

                Sure it is. Source: JordiGH and I hang out in several of the same bars^Wchannels. (Sup.)

                I currently use “weechat in tmux forever” (formerly “ERC in screen forever”). However, I never actually bother to scroll back except to search for my own name to see if anybody was looking for me.

                Once in the past decade, I reviewed my entire buffer for a specific channel because there was “drama” going on when I got back and I wanted to know what happened. The privilege to do so is what the chanops and opers there grant me when they allow my client to idle.

                Honestly, after you join a few big channels and a lot of small ones, “keeping up” is neither possible nor worth it. Do you “keep up” with newly uploaded youtube videos? :)

                1. 5

                  I do irssi in screen forever (call me old-fashioned ¯\_(ツ)_/¯), and that’s not really my experience. I don’t ‘keep up’, but – well, there are a couple of things. #1 is that when I join I’d like to have some context for what’s going on, and drama that causes me to want to scroll up quite a bit happens a lot more often than once in 10 years. Another thing is that sometimes, when it’s been a quiet day, I’ll go on and see that it’s not more than a screenful of text since last time I joined, which provides a nice sense of continuity. Additionally, just being already connected makes for a generally nicer experience. It makes communication asynchronous because there’s not an expectation that if you’re connected, you’re available; so, you can ignore people (or, to put it more generously, wait till later to talk to them). If you join a channel and immediately ask for help with something, it seems a lot stickier and you’re a lot less likely to get a response, than if you’ve been there for a while.

                  1. 1

                    Ah, yes. I agree with your description; I have experienced those things you describe. Which makes me wonder, why did I describe my experience differently?

                    I think I figured it out… Social channels are different than technical channels. I do in fact review the full buffer of technical channels (if they are low-volume enough). I just hadn’t thought about it when posting my previous comment! Thanks.

                    1. 2

                      Huh. Generally I don’t look at what happened in technical channels. Generally I come, ask/answer a question, but when I’m not there, I’m not there. Only exception is when there’s some bickering in the c channel (it happens a lot), I read backscroll so I can get an informed opinion and join in. Social channels, I know the people there so I care about what they said while I wasn’t there.

              2. 1

                What do you do to chat with friends? Coordinating an event over email with 7-8 people is painful.

                1. 5

                  I coordinate an event over email with 7-8 people; I don’t know, it works for me. I just did that last week.

                  1. 1

                    Hm, to each their own I guess. For us, someone will usually just ask who’s free tonight and whose house is free, where we’re eating etc etc and within a few hours we’ve sorted it out and whoever comes comes.

                    1. 1

                      Yep, email works great for that.

              3. 7

                I’ve always been saying that if you want a paper trail, you want email. There’s nothing wrong with it, it works. Chats are for real-time conversations, and those don’t mix well with having a paper trail. Whenever I’m forced to use Slack in companies where it’s the main way of communication, it’s obvious how inconvenient it is to hold a conversation over a few days (or time zones) buried in a constant stream of messages not separated into topics.

                1. 4

                  Wow - your post made me remember something I haven’t ‘felt’ about the web since back when Facebook’s instant messages feature was separate from it’s ‘mail’ feature, probably 2008. I remember reading that they planned on combining the two. At the time, I thought “How can they possibly do that? My IMs and my Mails are completely different ways to communicate, because one is real-time and the other asynchronous.

                  Facebook and Slack messaging work the same now. Real-time, with the paper trail. Both real-time and asynchronous. Stopped starting at your phone or your desktop client? Too bad, you’re now behind.

                  I miss being able to differentiate between a message I was expected to read instantly vs a message I could read on my own time.

                2. 3

                  That’s certainly one of the biggest drivers that’s forced my scrum team to transition to AWS Chime.

                  Being able to have persistent messages regardless of client connection state is an absolute deal breaker for us. Coordination becomes much MUCH more difficult otherwise. We used to use IRC, and it got to the point where I was the only one with ZNC working in the whole team :\

                  1. 2

                    I’m always a bit surprised by the staying power of IRC. This kind of feature is the reason I have always used XMPP for my chatrooms.

                    1. 4

                      XMPP is an awesome protocol IMO, the issue is that there does not seem to be any decent clients.

                      1. 1

                        What platform and style are you looking for? I’m partial to irssi-xmpp myself – and Conversations is king on Android. There are hundreds of clients of every kind, so hard to list at once until I know what you’re after :)

                      2. 2

                        Pardon my ignorance, I’ve used Jabber a bit way back in its infancy so I can’t recall - does XMPP inherently record server side traffic like that?

                        1. 1

                          The ability for a multi user chat to play back recent history when you join has been part of the protocol basically as long as the ability to have chatrooms at all. How much history is configured by room admin (usually).

                          More recently there are extensions to make this even better, but in practise that original feature covers everything I’ve wanted.

                        2. 2

                          Matrix seems to have figured out how to bridge different networks well. Does XMPP have similar success in that area, and if not, do you have any theories why? Is it a technical thing or just a matter of not enough critical mass?

                          1. 1

                            Yes, XMPP has always had bridges (we usually say “gateways” or “transports”) to different protocols. When I first started using XMPP most of my contacts were on MSN Messenger, and I talked to them seamlessly.

                            These days, there’s Spectrum as a gateway to everything in libpurple, transwhat to WhatsApp, biboumi to IRC, cheogram.com to SMS, even a few to Matrix :)

                            1. 1

                              So you guess it was mostly poor salesmanship kinda problem that not many people use those?

                        3. 2

                          Everyone I know who cares about persistent messages on IRC runs an IRC bouncer (e.g. ZNC). It’s pretty easy to set up..

                          1. 2

                            You’re assuming several things:

                            1. Bedrock infrastructure to run znc on. Not at all easy or guaranteed in the enterprise.
                            2. Enterprise IRC has the same lax auth strategy that Freenode or other ‘open’ IRC servers do.
                            3. That younger people give enough of a shit to go through this admittedly minimal effort when they can just use SlickCord or whatever and not think about it.
                            1. 2

                              Eh, I was just pointing out that there are options besides “completely change the IRC server”, that users can do to use IRC with persistent messaging.

                            2. 2

                              You still have to pay for, secure, and patch a server though. Unless you run ZNC at home, in which case you’d probably want to isolate that machine from your LAN.