5 ms·
IRC's operator model is pretty awful though. In the 80s when IRC was designed, they didn't foresee the importance of channel #names. Today, we know that names
by dragontamer 5y ago
IRC's operator model is pretty awful though.
In the 80s when IRC was designed, they didn't foresee the importance of channel #names. Today, we know that names are incredibly important (paying big bucks to keep your domain name in your control, as well as enforcing your names with trademark law where appropriate).
The fact that you can lose "control" of a #channel if you simply log off is a fundamental problem of IRC. Its a known problem: you have bouncers and services (ex: NameServ or ChanServ) to solve this problem.
---------
So "raw" public IRC doesn't work. At a minimum, we need NameServ and ChanServ (and probably a few other bots) before we can make a competent, modern IRC service.
I realize that's where IRC v3 was going (standardizing which bots were enabled). But it should also be noted that xmpp avoids the issue all together with a different channel security model.
-------
Hmmm, maybe there should be an IRC service with a policy to automate #op control to DNS lookups or something. That way, #channels can be connected to DNS lookups and unambiguous? I'm thinking something similar to email / DNSsec style lookups that proves ownership of a name.
- toast0 5y agoFirst to join gets ops is just a convention. You could certainly write a IRC server that requires strong authentication (client certificate maybe?) and enforces whatever policy you like. Maybe #dragontamer isn't joinable unless you are in it, and of course you would get ops when you join.
- dragontamer 5y agoIts not #dragontamer that people are worried about in practice. It'd be #ubuntu, or #linux. Who is the operator of the channel? The names don't really collide on Discord. Everyone gets their own private "server" instance.
- toast0 5y agoWhoever the server/network blesses. Typically, networks tend to bless whoever got there first, and with ChanServ services, whoever got there first and comes by once in a while. But if you control a server/network, you can do what you like. This isn't really a protocol problem though. You could certainly run a small IRC server for you and whoemever you could convince to connect, and there's room for some sort of virtual private IRC where anyone can have their own server instance and do whatever. Technically, it wouldn't be too hard; servers and networks are way better than around 2000, and user counts are way down from the peak; dealing with abuse might be a big issue though... IRC servers tend to be DDoS magnets, and botnets and whatever other unsavory stuff.
- Lammy 5y ago> In the 80s when IRC was designed, they didn't foresee the importance of channel #names. The network itself used to provide the namespace. What we didn't foresee were all the economic/political pressures that would eventually lead us to Centralize All The Things.
- dragontamer 5y agoThat's a point. Decentralized IRC has very limited use cases. Battle.NET or "Worms" video-game servers are a good use of decentralized IRC, as is the coordination of botnet swarms. (Turns out that IRC is very simple and robust) Decentralized video game servers (think Quake) probably could be built off of IRC protocol as well. But there's limited use in hooking up these decentralized sources to a central IRC chat. --------- For humans who want to chat, the primary services are: * Identity -- A 3rd party proves that people are who they say they are (be it Steam-identity, Facebook, or NameServ in IRC). Long-term conversations need trusted identities. * Channels -- Discord Servers, Facebook groups, Reddit Subreddits. You split up the community into silos that shares the same identify servers, so that groups of people can moderate topics of conversation and practically steer these "online eternal meetings" towards their intended purpose. (Often: to coordinate open source projects, but maybe just talk about C++) The larger the "surface" of your identity, the better. And the more channels with more (useful) humans to communicate with, the better a chat gets. As such, IRC-for-chat purposes naturally lends itself to centralization. Its mostly economic, and a little bit political (again: them dark-web Botnets are IRC-based, and politics of the internet means that web administrators should shut those down). By centralizing chat, you centralize policing. (Good luck starting up a botnet on Libra.irc) You also centralize the channels and identity services. So #RandomFooBar project's identities can be shared with a big #Ubuntu channel's identity.
- Lammy 5y ago> You split up the community into silos that shares the same identify servers, so that groups of people can moderate topics of conversation and practically steer these "online eternal meetings" towards their intended purpose. This is also a textbook COINTELPRO-style technique for controlling/misdirecting activist groups. > And the more channels with more (useful) humans to communicate with, the better a chat gets. Luckily our wetware comes with a built-in defense mechanism against this: https://en.wikipedia.org/wiki/Dunbar%27s_number https://en.wikipedia.org/wiki/Dunbar%27s_number
- orthoxerox 5y agoThat's not the only problem with IRC. There's no channel history, no multi-device support, no replies or mentions, no media sharing, it lacks many things we take for granted these days. I spent a lot of happy hours on IRC 20 years ago, but I wouldn't want to go to a barebones protocol like IRC in 2021.
- GekkePrutser 5y agoYou can tack on all these mod cons though with clients. Like Quassel or IRCCloud. That's the nice part of IRC. It's so simple that everything can talk to it, unlike most commercial services
- orthoxerox 5y agoThat's why commercial services just work. If I want to provide best-effort support for some library of mine I can set up a Gitter channel or a Discord "server" and it will work for sync and async communication, with incredibly low barrier for participation to boot. I could set up a clever bouncer for my own account, but anyone who asks a question when everyone else is asleep and logs off will never learn the answer. Yes, that's what async communication services are for, I know. I could run a bulletin board, or use GitHub discussions or Discourse, but the ship has sailed: people are used to chats full of features.
- dkdk8283 5y agoI like irc precisely because it lacks the features you mention. I don’t want irc to turn into social media.
- r3dk1ng 5y agoan IRC service kind of like how this was? https://news.ycombinator.com/item?id=12490685 https://news.ycombinator.com/item?id=12490685