Has anyone noticed that Slack communities are a lot less active these days? And IRC communities are less active these days. Where are the chatters going to now?
IRC turns thirty
121–130 of 232 posts
Re: IRC turns thirty
#122It is worth noting that IRC is in the middle of overhaul and upgrade with IRCv3 [1] standard. Sadly not many clients and servers support it (almost none of them). [1] https://www.ircv3.net
Most IRC clients are slowly developed or almost dead these days; the modus operandi of the IRCv3 developers is that they write patches for those IRC clients to support IRCv3 features and then push hard for the maintainers of those clients to merge them ("this is what the future of irc looks like! it's what the other clients are implementing! do you wanna be the only one not implementing it???")
They argue the development of their "standards" is open, but the truth is that nobody cares about it (most people are OK with IRC as it is now) so very few people contribute; they pretend that nobody complaining is a tacit agreement that everybody is OK with their changes, when that's far from the truth.
Re: IRC turns thirty
#123Love IRC. But what client should I use on my telephone?
It might seem weird, and probably will not please everyone, but in my experience, using an XMPP client (Conversations) along with biboumi (an XMPP IRC bridge, https://biboumi.louiz.org (note: I'm the author)) is the best way to use IRC on mobile: - You can idle in the channels without doing hundreds of part/join when your phone loses the connection - You get the full backlog of what was said while your phone was offl…
Thanks louiz! You do good work!
Re: IRC turns thirty
#124If you've never poked the IRC protocol directly, Google how to connect to IRC with Telnet. You can pretty reasonably use IRC just by writing to a socket - by hand. It's all human readable and understandable. It's incredible. It's what an open protocol should be. Writing a simple IRC client is a breeze!
I have found Matrix to be easier to interact with. You need a HTTP client instead of netcat but it's super simple to send JSON from a program or terminal.
Re: IRC turns thirty
#125Earlier quoted context omitted.
Perhaps #hackernews and #startups on freenode?
Another good starting point is #xkcd. it is a large channel with a lot of tech-ish and math-y people. EDIT: Note that channel discovery on IRC is largely a word-of-mouth thing so don't be shy to ask people for channel recommendations on irc. Most programming language have a dedicated channel, e.g. #D or #python or whatnot.
(A big channel for everyone to join is ##programming, by the way.)
Re: IRC turns thirty
#126Re: IRC turns thirty
#127I really can't wrap my head around how communities, especially for programming languages use Slack where all the information gets fed into some silo and is not publicly available. Especially if they don't pay for it, which most open source projects don't do for money reasons and the history gets wiped after a while. If I were to decide what to use in a company I'd probably go for https://www.irccloud.com/ - it's an open protocol but still has the convenience of not having to set up a bouncer and run your own IRC server.
Re: IRC turns thirty
#128I am invariably going to see in the world of Slack, "IRC, why don't you die already". No, IRC is not going to die. FreeNode is alive and well. And while you busy slamming and wishing death of IRC, just check the memory usage of your Slack client.
Is there a reason IRC couldn't look like slack to the user? kiwiirc is an opensource webUI IRC client (demo at https://kiwiirc.com/ ). To my untrained eye it looks slack-ish, but not being a slack-native I'm not really sure what Slack's draw is and whether its something webUI clients for IRC can't do.
Re: IRC turns thirty
#129Re: IRC turns thirty
#130If you've never poked the IRC protocol directly, Google how to connect to IRC with Telnet. You can pretty reasonably use IRC just by writing to a socket - by hand. It's all human readable and understandable. It's incredible. It's what an open protocol should be. Writing a simple IRC client is a breeze!
I tried it before and it's not as easy as it sounds. There is no one spec, it's a handful of RFCs and other ad hoc extensions that are barely documented anywhere. I think there's at least a dozen different documents you have to refer to.
Hardly anyone uses the DCC file transfer stuff anymore, so other than encryption, all you really need to handle is channel messages and private messages, plus the management commands (ops, voice, mute etc).