upvote
You can use a bouncer on IRC to retain messages while you were offline. In reality, it's the same with every other network: you need a server which receives and retains messages while you're offline.

With WhatsApp, Discord, etc, that server is provided by Facebook, Discard respectively. With XMPP, Matrix, that server is the instance in which you have an account or where the channel is hosted.

With IRC, you use a bouncer. What makes IRC unique is that a bouncer is _optional_. You can even join a channel without an account and without a server which keeps logs while you're offline. This ephemeral level of joining doesn't exist in WhatsApp, Discord, XMPP, Matrix, etc.

And, btw, this is not a new thing: I first saw bouncers 15 years ago and they weren't even new back then.

reply
I know there are technical ways to work around IRC's limitations, my point is that their mere existence adds more friction to using IRC so people move on to more frictionless places - and with chat apps being fundamentally social, that friction affects people who don't even mind the frictions themselves but their peers do (though personally i do mind these frictions - i do not want to bother with hosting anything or setting up bouncers or anything of the sort, i just want to pop in a channel, see what people were discussing, talk with whoever is there and/or share some of my own stuff and that's it).
reply
Agreed. The lack of stored history for every user is a huge blocker for new users. They enter a pretty active chat but they see nothing. They wait 10 mins after asking a question and bounce.

All of our comms for https://pico.sh are on irc and we have tons of users join and leave immediately because the room feels cold / dead even tho we were chatting 10 mins prior.

reply
Ergo has that built in now. It Just Worked when I installed that server and connected with Halloy.
reply
Concord channels on Nostr (https://concordprotocol.org/clients/) are handy for avoiding the centralization and privacy issues of Discord while also avoiding the reduction in asynchronous and media-enhanced functionality you'd get with IRC.

That said I can't say it's hard to just run irssi inside of tmux and attach/detach as necessary remotely. Nor is it hard to throw my media I'm sharing onto a web server. But yes, you do need to mix and match your utilities, rather than have an all in one package.

I do often enough find this to be more of a feature than a bug -- being stuck with Discord's UI is gross, but the network effect does have me continuing to use it for some groups.

reply
I think you underestimate how hard it really is. I don’t think anyone I know who isn't a professional programmer (and some who are) would have found either of your examples easy.
reply
It isn't hard, as i wrote i used to run irssi in screen back in the day when there wasn't another alternative, but that required me to have a VPS (i don't nowadays and i don't really want one because i don't want to bother with the admin side of things) and it is extra friction - and that is for someone like me who already has the knowledge to do it. For most people it is an insurmountable obstacle.
reply
The way some of us operated back in the day was to link to a forum post with a video upload or a chan board with a video upload from IRC. IRC was ephemeral, light-weight, fast and forums, chan boards were the semi-persistence, long enough for the majority of the intended audience to download. Some still do this today. [1]

[1] - https://altchan.org/sh/8

reply
> they post something (very often media-based) and very often others see/respond to it in their own leisure much later

who pays for the storage to keep the file on a computer somewhere, and the network to serve the file to the internet indefinitely? in Discord's case, it's the users

usenet iirc tried to do a sort of "torrent" the data across enthusiasts' / participants' computers?

reply
What you are describing here is microblogging like Twitter or Instagram, not using a chat to do chatting. Chatting, by design, is ephemeral and text only.
reply
This is actually a really good point and perspective. Couldn’t agree more.
reply
And yet that is how people use Discord - or more precisely, a mix of the two in the same interface. I think telling people they're not supposed to do something they find working is always losing battle.
reply
I'm not telling anyone what to do or not to on Discord. I'm pointing out that IRC is the way it is on purpose, not by error. If you want microblogging, use a microblogging platform. If that is Discord for you, use that. Just be aware that you aren't just chatting anymore.
reply
There are draft specs to fix both of these but they haven't been worked on recently because nobody has the time or energy to work on it.

This is fundamentally the main problem with IRC development nowadays. People want IRC to have features but are unwilling to support IRC developers to actually implement them and as a result pretty much every single IRC developer (myself included) who isn't churning out slop is burned out because its a thankless job.

reply
> There is no video (or any other file) host on IRC servers.

Ircv3, the thread title, supports file sharing

reply
How? From a quick search don't see anything in the spec about files or images. The closest i can think of is attaching metadata (which is a draft), but these are meant to store utf8 strings and i doubt a base64 encoded video is what the writers of the spec had in mind.
reply
It is in draft https://github.com/ircv3/ircv3-specifications/pull/562

Good v3 clients like The Lounge also offer it

reply