141–150 of 180 posts
Earlier quoted context omitted.
Naw, IRC was v1. It worked quite well, was well thought out, and standardized. Perfect? No. Good enough for the time and use-case? Yes. Slack and its kin are v2, capturing the requirements that have changed with the changing userbase. I only wish they were standardized, so we could have non-first party implementations (with the benefits that come with that).
Isn't mattermost an open source version of slack with most of the important features?
Earlier quoted context omitted.
Well that's the whole idea behind Snapchat, but I get your point. Sometimes I wish I didn't have so many messages saved forever tho, honestly.
Not just persistence in terms of "exists after I read it", but in terms of getting the messages at all. When someone sends you a snap while you don't have snapchat open, you get a push notification about it and the message is waiting on the server for you to read it. In IRC, anything that happens while you don't have an active session just doesn't exist. That might work for some communities, like programming language…
Other chat protocols fix this but lack the base, and are having trouble competing against the likes of Slack or iMessage in different use cases for example.
I'm excited to see how Purism's Librem 5 is going to play out with matrix as it's primary communications platform.
Earlier quoted context omitted.
For tech groups there are a lot of good ones on matrix which is a federated network.
I second this. Matrix is a great protocol, with lots of promising clients [0] like Fractal, Spectral, Riot(X), Pattle, etc. and bridges pretty well with Slack, Discord, Gitter, IRC... It is self-hostable, and provides a modern baseline of features (though Riot is the only fully-featured client at the moment). Burying myself in a walled garden is a no-go, so it has been working pretty well for me so far. I only regret…
Earlier quoted context omitted.
Reminds me when you start working on a side project, get a PoC working on the weekend (like a to-be application/website that for now kinda works on the command line), and tell yourself "alright, the hard part is over!" Then you realize you only finished the 0.01%. That's about where IRC seemed to have stopped. "We're done. The clients can do the hard stuff that users actually want."
Naw, IRC was v1. It worked quite well, was well thought out, and standardized. Perfect? No. Good enough for the time and use-case? Yes. Slack and its kin are v2, capturing the requirements that have changed with the changing userbase. I only wish they were standardized, so we could have non-first party implementations (with the benefits that come with that).
It’s hard to see a future for IRC or something like it to beat the proprietary alternatives unfortunately.
Earlier quoted context omitted.
> IRCCloud is a centralised, closed-source entity that stores all your chat logs in the cloud. So, no different than Slack/Discord (with the exception of the protocol). (A very important exception.) IRCCloud just appears to be akin to a BNC. If Bob decides to use IRCCloud or a BNC that is his choice. The rest of the team or group can still use their preferred IRC client because the protocol is an open standard. Would…
> (A very important exception.) IRCCloud just appears to be akin to a BNC. If Bob decides to use IRCCloud or a BNC that is his choice. The rest of the team or group can still use their preferred IRC client If just one team member uses IRCCliud for chat, all tgat sensitive info is now stored on IRCCloud’s servers. So, hiw exactly does “open FOSS protocol” help in this case?
30 years later and we have reinvented IRC, but worse as you can't use your own client, the protocol may not be public and it's harder to discover channels.
Slack is IRC for millennials. Just reinventing the world.
Earlier quoted context omitted.
He's likely being downvoted because he's discussing that he's happy with an open protocol being deprecated in favor of a centralized service that is the opposite, logging all of your private messages, forcing you to use their own client, etc. Granted, they increased usability significantly by doing this, but it comes at a large cost for people that value freedom and privacy.
"people that value freedom and privacy" Come on man, it's so hard to have conversations when people say shit like this...
[deleted]
Any thoughts on why StackOverflow chat never really took off?
30 years later and we have reinvented IRC, but worse as you can't use your own client, the protocol may not be public and it's harder to discover channels.
Amusingly, I couldn't see why slack stopped doing IRC, essentially that's what it was. The one and only thing that let IRC down was the message limitation. Some clients didn't make it very clear when those messages were not sent.