4 ms·
I agree that IRC would have been a good fit, and with modern IRC clients like LimeChat and Slate, it's not the "legacy" experience a lot of people remember. IR
by mtrpcic 11y ago
I agree that IRC would have been a good fit, and with modern IRC clients like LimeChat and Slate, it's not the "legacy" experience a lot of people remember. IRC also would solve all of the problems this guy faced:
* Free. You can hop onto an existing tech-focused server like Freenode, or if you want your own control, throw it on your own server(s) for pennies. If you do the latter, you have full control over all logging.
* Logging. Every client can choose what they want to log, what format the logs are in, where the logs live, etc. No more archived messages. Some IRC clients are smart enough to pull from the log to "back-fill" the messages.
* Modern Clients. Like a said above, LimeChat is a really nice IRC client. It doesn't have all the features of Slack, but do you really need all the features of slack?
* Bot Surplus. There are hundreds of bots written for IRC, in nearly every conceivable language. This was the first "integration" anyone ever used for chatting, and can integrate with anything if you put the time in. You don't get it for free, but for a community focused on programming, that's not the worst thing.
- voltagex_ 11y agoThe slow demise of IRC is sad. Clients like WeeChat excel on the text side of things, but where's the knockout web, desktop and mobile client? Something with the UI of Gitter would go far. I always feel like IRC is a few protocol extensions and a few clients away from being relevant again. /me goes back to Freenode
- Lazare 11y agoI think IRCCloud has a UI significantly better than Gitter. (Then again, I'm not a fan of Gitter's UI, at least as far as their desktop OS X client goes...)
- jsmthrowaway 11y agoI'm happy IRC is dying, because it's a giant attack surface. As a hosting provider sysadmin, dealing with IRC servers was among the absolute worst parts of my job -- mitigating DDoS attacks against them, extensive hacking attempts directed at their infrastructure and later, mine, when they couldn't get in, credit card fraud associated with the accounts, IRC networks designed specifically for command and control of botnets and trafficking in child pornography, FBI raids against said networks we hadn't yet discovered... There are exceptions, like OFTC, but merely waltzing into the wrong place on EFnet these days is enough to get 10+ Gbit of UDP traffic directed at your IP address. I used to be fairly okay bouncing on a vhost, but now even the 12-year-olds have enough traffic to knock over a 40 Gbit port channel. An increasing number of datacenters are just filtering 6667. I'm on board with that. Seriously, let IRC relegate itself to the dark corners of the Internet on shitty hosts and stay there, IMO.
- voltagex_ 11y agoI wonder if this is an argument against IRC, or just against EFNet.
- pki 11y agoFrom my experience I haven't seen anything like this in the last few years. Botnets are controlled primarily from C&C web services or other SSL/TLS (+encrypted messages) transport via web. The brute force ddos attacks I've seen are on illegal private server emulators and Minecraft et al. Maybe this is just a completely different experience by being in differnt part of internet.
- not_with_retard 11y ago> hosting provider sysadmin You should kick them out for repeated DDoS attempts on their IPs, like any sane host does.
- LinuxBender 11y agoThis does not sound related to IRC at all. It sounds related to a specific network and unintended target audience. This in no way would affect a corporation or organization that decided to use IRC. You can determine on your own IRC who is authorized to connect, make channels, etc.
- kzvezdarov 11y agoThe IRCv3 work group is making some good progress: http://ircv3.net/ http://ircv3.net/ .