I happen to prefer IRC is better protocol, rather than Discord.
tepples wrote:
Here are some features that Discord has and IRC lacks:
- The server automatically logs text channels. A user can view messages sent to a channel while the user was offline without each user having to obtain a shell account on which to run ZNC.
- Membership in a set of related text and voice channels is grouped, and the owner of such a group can sync permissions throughout the group by assigning roles to members.
- Users can upload attachments to the server, and the client embeds previews of attachments and linked websites. Unlike with DCC, no port forwarding is required.
- Users can add emojis as reactions to a message, and it counts how many users have added each reaction to a message.
What IRC server and client extensions would allow all of the above?
All of this can certainly be done in a IRC server:
- I have once modified an existing IRC server software to do auto logging, although normally it is another client that does that I think; at least the #esoteric in Freenode uses another client to log.
- Many IRC servers implement a CS command; try CS HELP for a description of the commands and how to use them in that server. Freenode has the following: "Available exttargets are: $chanacs:#channel - Any user with channel access in the given channel (including hostmasks)." It also has "extended bans (ban conditionals)", listed by HELP EXTBAN.
- I have seen no IRC with attachment uploads, although I have seen attachments uploaded to Discord servers and posted on IRC. However, it can be implemented (a client extension will be needed too in this case).
- Such "message reactions" I don't really see much point, although I suppose an IRC server could provide a mode that if the user activates it will provide a serial number with each message, enabling to do such thing.
There are other features of IRC too that are not commonly implemented though:
- Modeless channels: Channel names with + at front, with no permissions, modes cannot be set, and channel takeovers are impossible (because setting yourself as an operator and banning other users is impossible).
- Other kind of channels: Channel names with & at front (local to one server), and with ! at front ("safe", but otherwise like the common # channels). Both are also immune to takeovers, but for different reasons; they do have modes, unlike + channels.
- The SUMMON command: If a user is on the server, the IRC can be used to call them to the IRC without the user having to be on the IRC all the time.
tepples wrote:
The complaint, as I understand it, is that #nesdev on EFnet routinely goes so far off-topic that its character has become overly hardware-oriented to the exclusion of software development. People talk more about "the new FPGA console I'm working on" than about making NES games.
While this happens (and off-topic is not always about that either), I think, if you have something to write about making NES games (a question, a comment about the game you make, etc), then please to mention it. You will write about off-topic when you do not have a on-topic to mention, but when you do, then you can discuss the on-topics (and if someone is simultaneously discussing something else, those who are engaged in the on-topic conversation can ignore them if it isn't relevant to their discussion). (I personally have both on-topic and off-topic things to discuss on this IRC.)