It's hard to overstate the value I've gotten out of Freenode IRC over the years. The #postgresql channel is chock-full of contributors and PG gurus willing to generously spend time explaining concepts and best practices. A real gem. Same thing with #clojure and #haskell . ##networking is great as well. Pretty amazing to drop into the same channel for 6-7 years in a row and see the same faces every time.

One of the first things I used to teach devs on our team was how to ask questions on IRC to get the answers they were looking for. When you're working with niche tooling, building personal connections and relying on the community becomes irreplaceable.

Wish people IRCed mode, wonder what the trend with that has been recently with Slack taking over.

> Pretty amazing to drop into the same channel for 6-7 years in a row and see the same faces every time.

This... shout outs to darkf, nedbat and aria from Node JS

It amazes me how these people continue to help others and blessed to have them repeatedly help me on so many occasions

I still am not sure the best way to "IRC," I remember back in the day having it running in a program on Windows but lordy knows what the "preferred" method is now.

I've noticed that StackOverflow now has a chat feature which is very IRC-ish and relatively helpful, if a bit empty at times.

The great thing about the "protocols instead of services" design philosophy is that there is nobody to tell you what the "preferred" method is, you just use whatever you prefer.

For infrequent use, perhaps try Freenode webchat: http://webchat.freenode.net/

The "preferred" method is to use some sort of bouncer (znc) along with running a CLI client (irssi, weechat) in a session manager (screen, tmux) on a remote server. Weechat includes its own bouncer, and I would recommend somebody to start with it over irssi. I only fairly recently switched to weechat from znc + irssi because I wanted to try weechat.el as I wasn't happy with the state of using screen in eshell, and I don't have it as configured as my irssi was yet but I'm happy with it. Next up, switching to tmux from screen...

Quassel is also an alternative, for those that prefer a GUI-client

> but lordy knows what the "preferred" method is now.

Who is this 'lordy', and why are they telling you what your preferences are? IRC is just a protocol. You can use the old clients you used to use[1], keep a command line client running in a screen session on some vps[2]some shiny web based client[3], or you can write your own in a couple of days if none of the other options appeal to you. I took the last option[4]

[1] https://hexchat.github.io/ [2] https://irssi.org/ [3] https://kiwiirc.com/ [4] https://eigenstate.org/software/ircmyr

"Preferred" way to IRC is to run a client just like you did in your yesteryears. Nothing ever changed.

I've found IRCCloud to be nice. Browser-based.

The first step up people generally make from the webchat is something simple like hexchat, although I don't know what the state of windows binaries is these days. Used to be that you could only get precompiled windows binaries by paying.

I prefer command-line irc from a vps, I use erc because I'm an emacs fella, but I've enjoyed irssi as well. Don't forget to cloak whenever possible!

Mostly the same thing. Many have bridges between the two. Some features don’t work though. Also on Slack, many use their real names/pics and the communities seem more friendly compare to IRC, at least for now.

Invite to these slacks please

#clojure, #machinelearning and #math on Freenode have been fantastic resources.

I always try and encourage people to use IRC over Slack (which I've found to be a bit of a timewaster).

What I personally don't like about IRC is that you basically have to be online all the time (or at least have some bouncer)...

Otherwise you can't scroll up and read what's going on, if there are people already talking about something.

Also this creates to long lists of idlying people, so you can't really have an overview of who's really online there.

I wish self important mean nerds, who were abused in school, IRCed less. #python and #golang have become horrible, at least last I checked.

Isn't this wish rather selfish as well? Rather than spending time, becoming a contributor yourself and effectively showing them a better way, you want them to disappear.

It is. Have you done that? Does it work?

Becoming the example that people want to emulate? Yes, it does work, but it's a lot harder. The key is to do it in little increments everyday. The more influence you have, the more you'll be able to sway a person's opinion. Growing this organically is the challenge.

This does happen a bunch. I was always dreading asking question in #nginx back in the day, and #bash could be pretty rough too, but you learn to grow a thick skin.

Well #golang is a good test for thick skin. I thought mine was thick, but no.

Valid points, absolutely.

IRC and Freenode are great...if you're already in tech. About every third freelance client I speak with needs help with simple stuff - understanding how to get a host. Understanding how to point DNS to a service like Squarespace. They don't have that one tech friend to help them or know where to ask for help, despite the constant and saturated availability of chat rooms/forums.

So while we'll provide dev-to-dev mentoring, I really hope we reach this audience too.

The target of this service is very much NOT people who would know how to use IRC and know where to go on IRC to ask a question, nor is the type of question which this service is aiming to answer easy to ask over text.

We used to have college freshmen learn to use IRC by seeing someone else using it and getting a five minute "here's how".

I think the missing part is "seeing someone else using it".

What kind of programmer can't figure out how to use IRC?

If this is the target audience. Who will be there to help?

I think there's a flipside to that latency, though - you may have to wait awhile, but once you connect, there's almost zero latency. When you're face to face with a person, you're not wondering if they stepped away from the keyboard to get a cup of coffee, or investigate whether their cat knocked over a christmas tree, or if their internet went down. You know their work didn't just page them with a critical error. The conversation goes much faster once it starts.

And that’s what I love about IRC — if there’s a topic I’m interested in, I can hop into freenode and find a channel focused on it.

> my questions probably don't last that long

If they don't last that long they were not worth bothering other people with, in the first place. Do your job yourself before asking for help.

I mean, programming is a knowledge-based job and you're expected to be able to learn on your own. It's not bad to ask for help once you honestly did your best and still cannot understand something, but giving up in the first paragraph of a man page and hitting IRC immediately is all kinds of bad.