121–130 of 370 posts
Here is links to Matrix and Riot. https://matrix.org/blog/index https://about.riot.im/
Please support open source projects! The Internet was built on open standards.
Earlier quoted context omitted.
> This goes beyond Slack or Discord or chat-app-of-the-month. I can probably name up to 10 chat-networks and products which is existed in the 90s. None remain. IRC does though. Exactly because it wasn’t a product, but instead a protocol specification. Whatever rationale Mozilla has for this, it’s going to be proven short sighted.
It depends. If they choose something open like Matrix or XMPP, it could work well in the long-term.
There are no XMPP frontends that can compete with the "shininess" of the modern, proprietary systems like Slack so that's out already.
As for Matrix/Riot ... maybe, but I don't think it's likely that they'll go with that.
Earlier quoted context omitted.
So it sounds like regarding moderation, slack is at best on par with irc. And while on orc you can pretty much script and automate anything you want to facilitate the moderation job, with slack you're at the mercy of having some documented or undocumented api call available? One step forwards and two steps back...
Well, in general you can also ignore people on IRC, you can ban people from channels, and some IRCds support restricted DM permissions which require a user to share channels with you and be _validated_ to message you. We don't have these sorts of controls in Slack because it's built to support companies with Human Resource departments. Communities like ours don't give the Slack shareholders value. So in some ways it'…
Why not ban them completely and have a private appeal process? How often are people a nuisance in one channel yet valuable in another?
Earlier quoted context omitted.
So it sounds like regarding moderation, slack is at best on par with irc. And while on orc you can pretty much script and automate anything you want to facilitate the moderation job, with slack you're at the mercy of having some documented or undocumented api call available? One step forwards and two steps back...
And yet, slack has seen exponential growth, while IRC was always available but rarely used. We have seen this before and we will see it again. If OSS wants to be widely used, it needs to take UI seriously, and not dismiss it as frivolous “eye-candy”. It’s ok so say ‘no, we are fine within our niche’. But then you don’t get to arrogantly explain to them how they are “taking one step forward, two back” by not embarking…
Freenode has about 85,000 people logged in right now and there's over 50,000 channels.
I'm in a bunch of tech related channels and there's hundreds (or 1,000+) people in most of them. It's still active and has been for 15+ years. Freenode is just 1 IRC network of many too but it's where a lot of tech channels are set up.
IRC is awesome. You can use it from a terminal (or get a GUI client that uses < 20MB of RAM), it opens instantly, you can connect to a bunch of channels and networks automatically (with password protection on your nick), typing feels instant and you get infinite log history. Doesn't get much better in my opinion.
It's a shame that IRC usage is dwindling especially in techie circles. However I can understand it if it doesn't work for them any more although in my opinion IRC has a lot of moderation tools available. In any case, the "problem", of sorts, is not abandoning IRC but what comes next. The web is choke full of proprietary communication protocols that cannot talk to each other and you have private entities acting as gat…
Earlier quoted context omitted.
Spam can be difficult to stop on IRC compared to modern webchat applications. From lacking things like javascript, captchas, cdns, and so on, to having a distributed network architecture and fewer ways to verify users.
> having a distributed network architecture and fewer ways to verify users You have exactly as many ways to verify users as are implemented in your NickServ, and pretty much every snazzy web-y proprietary chat platform has a "distributed network architecture" as well. IRC has plenty of real problems, but your particular list of arguments seems completely irrelevant.
There's really a need for IM interop. These fragmented islands stall the network effect (Metcalfe's law) that is needed to sustain and grow communities. I guess the best thing for the current situatio would be a headless service that would connect to your IM identities, and buffer messages, from many different IM identities and protocols. You would then have intermittedly connected web or terminal or mobile apps as i…
If something 'modern' is required, Matrix protocol and its ecosystem is a contender. Also look into the world of ActivityPub federated applications, which cover everything from replacing Twitter to blogging.
My personal setup is to use bitlbee or libpurple to connect to every major chat network that exists today, bridged to my irc client via znc. This provides a consistent presence, status, and ui across desktop/mobile, push notifications, filtering, and behavior under my control, all with chat client that doesn't take up 1GB+ of memory with phone-home telemetry and useless emoji
It's a shame that IRC usage is dwindling especially in techie circles. However I can understand it if it doesn't work for them any more although in my opinion IRC has a lot of moderation tools available. In any case, the "problem", of sorts, is not abandoning IRC but what comes next. The web is choke full of proprietary communication protocols that cannot talk to each other and you have private entities acting as gat…
As an IRC user since the early 90s (EFnet and freenode), I can say that it really feels like it is dying. There are still a few popular channels with helpful people, but the vast majority of channels are silent with no one but afk users logged into a seemingly forgotten ‘screen’ session. And of the channels that do have real people, those people often seem to be there for no reason other than to tell people to RTFM,…
It's a shame that IRC usage is dwindling especially in techie circles. However I can understand it if it doesn't work for them any more although in my opinion IRC has a lot of moderation tools available. In any case, the "problem", of sorts, is not abandoning IRC but what comes next. The web is choke full of proprietary communication protocols that cannot talk to each other and you have private entities acting as gat…
A slack like interface can be built on top of IRC. I'm a bit amazed that no one has decided to do that.