3 ms·
I used to spend a fair bit of time in a non-tech IRC (we've moved to Discord since) and the amount of intelligent people who simply could not get the hang of Ni
by DC-3 8y ago
I used to spend a fair bit of time in a non-tech IRC (we've moved to Discord since) and the amount of intelligent people who simply could not get the hang of NickServ was astounding.
- self_awareness 8y agoI've always wondered why IRC clients didn't add seamless integration with NickServs of large networks. Maybe this was one of the reasons why services like Slack or Discord are successful; these services are taking your hand and are guiding you through everything, while IRC expects the user to read RFC and diagnostic server output in order to figure what's going on. I don't think it has to be this way. IRC as a protocol probably can be used to build a service as friendly as Slack. I.e. it's not a problem to add URL autoexpansion, like in this WeeChat plugin: https://github.com/antekone/youtube-autoexpand https://github.com/antekone/youtube-autoexpand . Of course it's not easily possible or practical to show pictures inside of the terminal window, but I think it's entirely possible to create a new modern Slack-competitive IRC client over a pure IRC network. What could be done on IRC can be seen in an old Microsoft app, Microsoft Comic Chat: https://en.wikipedia.org/wiki/Microsoft_Comic_Chat https://en.wikipedia.org/wiki/Microsoft_Comic_Chat . (disclaimer: i prefer IRC to Slack/Discord but I get why for many people IRC is a bad idea)
- jandrese 8y agoNickServ always felt like a terrible hack to me. It doesn't help that some major servers have incredibly stingy limits on NickServ too. I've had usernames age out after only a week, and the registration process is fairly cumbersome. Plus it involves sending a password in plaintext over the network, which never felt good.