My main problem with Discord is its atrocious way of handling logs.
There's no (that I know of) to export channel logs from Discord, nor to log to an external text file.
That means that if I'm interested in something that was discussed at some point in the past, I have to either use Discord's crappy search feature, or manually scroll back and manually scan through text to try to find what I'm interested in.
Discord's scrollback is slow and painful.
By contrast, IRC logs are just plain text files, so I can use powerful regexes or a plethora of text search/manipulation tools to work with them, and scrolling back through text logs is super fast... especially in a decent editor like vim or emacs.
I also own my own logs, and don't need to be connected to any server to read them. Reading/searching through logs can be done completely offline.
If Discord decides to ban you or some channel/server you're interested in goes down (permanently or even temporarily), you're completely screwed. You'll never get the information you're interested in out of it.
The only substantial advantage of Discord I can see over IRC is inline images (which are often just an annoyance, but can sometimes be useful) and voice chat.
Other than that it's bloated, opaque, and a worse experience for me than IRC.
I don't know a way to export logs, but I am in some Discord channels which have a bot joined to connect them to an IRC channel in a 2-way echo. The IRC side of that could be logging everything from that channel with standard IRC logs.
> "The only substantial advantage of Discord I can see over IRC is inline images and voice chat."
Inline code blocks with syntax highlighting using ```python markdown syntax; replying to a message brings a clickable line of what you are replying to which jumps back up to the previous line in the chat.
> replying to a message brings a clickable line of what you are replying to which jumps back up to the previous line in the chat.
I actually really despise this feature, because it pings the user you're replying to by default and you have to explicitly turn it off as a user sending the message. "Server" admins cannot change the functionality around.
From a personal standpoint it's not generally a problem, but my company uses Discord as a support platform so we (the staff) end up constantly getting pinged when we do not want to, especially when it's for a message that we may have posted in our general "community area" a few hours ago, and someone has just now decided to reply with "lol" and it generates a ping for it.
Pinging should be opt-in not opt-out, just like when replying to someone before hand, you explicitly needed to make a conscious choice to ping them.
Even worse, when the feature was first released, literally editing your message (even if you explicitly turned off the ping) caused it to ping the other user.
It's actually against our rules to ping support staff in ticket channels (primarily because someone will either ping everyone with the staff role upon two seconds after the ticket opens - or ping a staff member to "bump" their ticket), but its not like we can realistically enforce that for reply-generated pings due to the fact that most of the time its accidental (we do ask them to turn off the ping after the first time - and a good chunk of the time people "forget" to still do so, whether intentionally or unintentionally). /endrant
I remember their official twitter responding to someone that exporting logs wasn't something they could/wanted to do for whatever reason so I wrote a content dumper super quickly https://github.com/IceFlinger/discord-server-dump
But its a big shame that they don't wanna include this as a built in feature since yeah exported logs are very useful.
There's no (that I know of) to export channel logs from Discord, nor to log to an external text file.
That means that if I'm interested in something that was discussed at some point in the past, I have to either use Discord's crappy search feature, or manually scroll back and manually scan through text to try to find what I'm interested in.
Discord's scrollback is slow and painful.
By contrast, IRC logs are just plain text files, so I can use powerful regexes or a plethora of text search/manipulation tools to work with them, and scrolling back through text logs is super fast... especially in a decent editor like vim or emacs.
I also own my own logs, and don't need to be connected to any server to read them. Reading/searching through logs can be done completely offline.
If Discord decides to ban you or some channel/server you're interested in goes down (permanently or even temporarily), you're completely screwed. You'll never get the information you're interested in out of it.
The only substantial advantage of Discord I can see over IRC is inline images (which are often just an annoyance, but can sometimes be useful) and voice chat.
Other than that it's bloated, opaque, and a worse experience for me than IRC.