I think “IRC (an open protocol)” served more to explain the why than the what here. It frames the whole rest of the story and why GP felt alienated.
It wasn’t because Mozilla stopped using GP’s favorite chat software. It’s because GP was a believer in the mission and the principles. Switching from an open system to a corny corporate one made the whole illusion fall apart. Mozilla was a corp all along and they took their volunteers for a ride.
Another feeling when reading "(I woudn't know, uBlock is pretty effective)" coming from a volunteer for MDN
Who else would be likely to look at what a web page is trying to get the browser to do, e.g., trigger requests for ads using Javascript. There are a variety of places to look, it is not like this is seriously hidden from those with even the slightest curiousity
That a former MDN volunteer is apparently disappointed by ads on MDN yet satisfied with MDN anyway because of a community-sourced browser add-on. An add-on that can be rendered useless at any time by the browser vendor, including the one that puts ads on MDN
It is not unimaginable that one day uBlock Origin may cease to work on Firefox when Mozilla sells search data to Google as its primary source of income and is actively working on such things as "making ads more private"
I thank the volunteer for their past work on MDN, I'm not singling him out, nor am I holding it against anyone for thinking this way, but I wonder how many uBlock Origin users believe themselves to possess some "specialised knowledge",^1 for lack of a better term, but would be all but helpless against advertising without a solution provided by someone else, e.g., a browser extension
The point I'm making is that today it seems like "knowing which app to install and how to install it" is considered specialised knowledge instead of actually knowing how to avoid ads to an extent where if the app stopped working they could devise another solution
There are definitely some HN users who can do it, and you, dear reader may be amongst them, but it seems, based on the comments I have seen over the years, there are many, many more who cannot. In that sense the situation is a bit like the IRC comment
The more one understands about online ads, the more clear it should be that so-called "ad blockers" is only a temporary solution at best, and these only work with web browsers
IMHO it is important that more people who wish to avoid ads become more curious about how they work instead of only installing a browser extension and concluding the problem is solved for the long-term
1. Many calling themselves "engineers" for example
So far, I've only found clients with different bugs. Calling them good would be a stretch. Passable, perhaps. But the scene as a whole is more of a choose-the-bugs-to-live-with situation than choose-a-good-client.
I'm sorry but I lost interest in matrix in 2017 ish when I tried to use my existing matrix log in when trying to sign into the Mozilla matrix and I simply couldn't. At the end I ended up creating a new account on Mozilla side just so I could use it for a few days.
I've never thought of matrix as a mature technology ever since.
Mastodon does not have persistence of data though. Your instance shuts down? All your posts are gone. I naively assumed I could just move them to a new instance and found out the hard way. I have felt disillusioned with Mastodon ever since.
In practice "better UI" would mean things like being able to trivially share files and images, or quote/link a specific message, or even making it easier to distinguish between users with similar nicks via their profile pictures. And those UI improvements are actually features which are integral to its protocol, so they can't easily be bolted on by a custom IRC client in a backwards-compatible way.
Literally every single modern chat platform has support for stuff like that, and for a reason. Discord became popular because it combined those modern chat features with the ability for every community to create its own private little "server" - while at the same time making it trivial to participate in multiple "servers" at once.
Quoting/linking is a client feature, not a server one.
IRC servers do also support profiles.
I think the real “issue” with IRC is that its users generally prefer the minimal UI. So there isn’t an high enough demand to make prettier UIs. But there are web clients that are a little less basic.
For what it’s worth, I’m in that minimal camp too. I wish I could still connect Slack to IRC.
I'd guess the important feature for Discord is it is easier for the administrators to get hosted and online, but "you could create a client with a better UI than discord" is a terrible line of argument. People could do lots of things in the OSS world and they don't. I can't recall any IRC client that I have found as easy to use as the Discord client except - ironically given the topic - ChatZilla which died off years ago because Mozilla decided that extensions were more of a 2000s technology than something they wanted to support.
Email is OK. The point is that most conversations moved to other media (mainly chats) and so 90% of my mail is notifications, 9% is newsletters, 1% are real messages. They used to be 99%.
The entire reason Mozilla came into being is to do things like improve the user experience for IRC so we can keep the internet open. There has never been any other reason for Mozilla as an organization to exist.
It's been a while since I last used IRC, but afaik one of the issues with it was that servers revealed the IP address of users to every other user by default. Since the IP is geographic that's one piece of information you could use to doxx someone.
IP addresses aren't linked to a complete street address, and many times don't even show the right town, especially those on CG-NAT or a plain ol' direct public dynamic address. I have seen some IPs, like on AT&T and Comcast home Internet, showing a different state.
So in many cases, you don't need a VPN to prevent revealing your actual geographic location.
The fact that this is needed at all is a serious problem. Making people who aren't aware of some obscure details accidentally doxx themselves is incredibly user-hostile.
Netsplits, missed messages and bot wars over channel and nick ownership were an integral part of IRC UX, and they were direct consequences the IRC protocol. If Discord was run on top of IRC protocol, it would have the same. Discord would probably be its own network and the people who prefer IRCnet, EFnet or QuakeNet would never touch it.
It's not inherent to the protocol. https://ergo.chat/ does not have netsplits (from having a single server) and https://github.com/Libera-Chat/sable replaces the server-to-server protocol to eliminate netsplits as well.
And even when not eliminated entirely, they are infrequent and barely visible on well-managed networks like Libera.Chat. Many chat platforms have more (and longer) outages than Libera has netsplits.
Solved decades ago thanks to NickServ and ChanServ (though I'll admit they are ad-hoc additions on top of the protocol). And ~15 years ago we got native support for authentication (https://ircv3.net/specs/extensions/sasl-3.1)
So... Usually it's claimed that one of the advantages of IRC is that it doesn't depend on a single server, so using a single server feels a bit like cheating. Replacing the server-to-server protocol sounds a lot like it's not really IRC protocol any more. The chathistory link says "This specification may change at any time and we do not recommend implementing it in a production environment." right on top. And yes, NickServ and ChanServ exist on some networks and IIRC they were one of the major points in debates over which network is the best and which ones to not touch with a ten feet pole. A hypothetical IRC-based Discord-like service could have it.
I mean the word "Relay" in Internet Relay Chat was meant to refer to relaying between servers. Larger networks even had some hub servers that didn't allow users to connect at all, and existed to be server interchanges.
IRCv3 missed the boat by years. By 2016, when the working group was formed, IRC was already well past its glory years. Even then, it took til the 2020s before any major network fully adopted it. Because - and I say this as a nerd who held an O line on two of those major networks at one point in my life - a bunch of nerds got hung up on arguing about implementation specs rather than looking at features and functionality organically. Ironically, in the quest to avoid becoming a closed Discord/Slack/what-have-you ecosystem product, they needed a product manager to remind them that what they needed to build in that working group was an evolution to IRCv2, not endless arguments over the format of configuration files for server daemons, for but one example.
>Like “the UX of HTTP is horrible”? Still doesn’t make any sense
Sure it does, when all browsers have more or less the same, and the context makes clear we're not talking about the mere programmatic consumption of HTTP (like through some REST api).
"But it's a protocol and not a client" is pedantically irrelevant, given that the clients for that protocol all follow the same conventions. The parent already said they meant the UX of it "which is arguably similar between implementations".
Besides, protocols impose some concepts and models of interaction and consumption, which informs any UX created on top of them. So it's not like that client sameness is merely accidental and unrelated to the protocol either.
It's gatekeeping. Don't be surprised when your pet project slowly dies because potential new contributors choose to join less hostile communities instead.
Makes me think in 10 years time the web will all be discord-like data silos behind infernal subscriptions and/or dark patterns with ads.
What a wonderful thing we've created.