logoalt Hacker News

movedxyesterday at 11:19 PM4 repliesview on HN

I’m going to do a video on this soon, but I was able to get Ergo IRCd and TheLounge up and running pretty quickly; https://chat.crilly.au/

I’ll be building a new platform on these two technologies and using Zoom or something else like Jitsi on the side for video/audio sharing.

It’s time accept the loss of “features” and go back to something simpler but also something that can still be here in 38 years — like IRC has been.


Replies

Aurornisyesterday at 11:28 PM

> It’s time accept the loss of “features” and go back to something simpler

I guess I have a hard time understanding these calls to switch to a platform that has even fewer features than the unverified Discord accounts. The blog post is incorrect in claiming that verification will be mandatory. It will only be necessary to access certain features and content. For simple IRC-style chats or even for voice chats with gaming friends, no verification is required.

The average Discord user, or even the 98th percentile user, isn’t going to be looking to switch to a platform that isn’t a replacement for the features they use. They’re just going to not verify their accounts and move on.

show 1 reply
outimeyesterday at 11:40 PM

It's time to accept that 99% of people will not accept the loss of "features" (not sure why that's in quotes) or move to something objectively inferior for their needs i.e. something that requires more knowledge instead of simply opening an app where everything is ready to use.

Coming from a former heavy IRC user who's not going back except for nostalgia trips.

zanellato19yesterday at 11:30 PM

Only a small handful of people will do something like that. For most people, losing people is a nonstarter

stackghostyesterday at 11:33 PM

I still use a few niche IRC channels and run my own internal IRC network as a home automation message bus, so I'm a fan of IRC for its simplicity, but honestly: IRC really does need a modernization.

Things like image embeds, "markdown lite" formatting, and cross-device synchronization are now considered table stakes. There are always going to be some EFnet-type grognards who resist progress because reasons, but they should be ignored.

IRCv3 and Ergo support some of what's needed already (and in a backwards-compatible way!) but client support just isn't there yet, particularly on mobile.

show 1 reply