4 ms·
I really want the IRC protocol to decouple its sessions from the TCP connection and move to using HTTP as a transport, even if the only api verb is "send" and t
by sneak 6y ago
I really want the IRC protocol to decouple its sessions from the TCP connection and move to using HTTP as a transport, even if the only api verb is "send" and the only response is "receive output buffer".
I used to really love IRC, and think it could undergo a resurgence given the right upgrades.
- tastyfreeze 6y agoWhat upgrades do you think should be added? I miss the environment of IRC 25 years ago. Its something that no messenging application has really been able to replicate for me.
- SilverRed 6y agoAt a bare minimum it needs to be redesigned for modern computers. We have left the days where user all use desktops which sit online always and hold an open connection. IRC needs to support something HTTP like with history.
- petre 6y agoMQTT or another pubsub queue protocol is probably a better choice than HTTP for disconnected operation. Use it over websockets if you want it to go through proxies.
- pantalaimon 6y agoWhat's the advantage of using HTTP?
- sneak 6y agoI can reverse proxy it, I can dockerize it, I don't have to modify my firewall, I can TLS-SNI vhost it, I can decouple the TLS keys from the daemon process by terminating TLS on a different container, I can connect to it from weird LANs that filter non-HTTP, I can drop the TCP connections from my mobile device without dropping my whole login session, et c.
- swiley 6y agoI don't know what makes http important for reverse proxy or docker. I've reveres proxied and dockerized apps that listen on normal TCP port.
- sneak 6y agoReverse proxying non-http protocols and preserving the client ip back to the backing service involves a terrible hack called Proxy Protocol that IIRC haproxy invented to work around the fact that TCP-directly protocols don't normally allow you to carry metadata (like HTTP does in headers). https://www.haproxy.com/blog/haproxy/proxy-protocol/ https://www.haproxy.com/blog/haproxy/proxy-protocol/ It's messy. The tooling around TLS and reverse proxying for HTTP is much more common and easy.
- Karrot_Kream 6y agoIndeed, and it's because TCP is not meant to deal with that sort of proxy-ing and framing. HTTP is specifically an L7 protocol and that makes it a good spot to do things like framing and signalling (through headers and such).
- toast0 6y agoIs proxy protocol really a terrible hack? (Ok the part where it expects the header to be in a single packet and have no other data kind of is, but that usually works out ok) It's a way to pass some meta data at the beginning of the session and you can configure it. Alternatively, if your proxy and origin are on the same ethernet broadcast domain, you could just change the destination ethernet address and resend the packet as-is, or stick it in an IPIP tunnel.
- progval 6y ago> preserving the client ip back to the backing service involves a terrible hack called Proxy Protocol No need for that, there's an IRC extension to indicate the source IP to the backend: https://ircv3.net/specs/extensions/webirc https://ircv3.net/specs/extensions/webirc It's supported by all the major IRCd implementations these days.
- threeseed 6y agoWhether you are in an enterprise, university, airport, internet cafe, restrictive country etc. HTTP traffic just works. No one is going to open up non-standard ports especially not for IRC which most people aren't familiar with.
- metroholografix 6y agoNot everything has to run on top of HTTP or use json. IRCv3 gets a lot more right than wrong.
- threeseed 6y agoIf you want adoption within the enterprise then you really need to use HTTP. And these days even most SMBs are taking network security seriously and blocking non HTTP ports.
- metroholografix 6y agoSo let those who need it use existing HTTP <-> IRC gateways or write their own. IRC is flexible enough to accommodate this which is testament to how resilient and extensible the protocol has proven to be over the decades. I see no reason whatsoever to make HTTP a core requirement.
- threeseed 6y agoWhich is why everyone uses Slack, Teams etc and IRC is irrelevant. Because there wasn't enough focus on end user experience.
- metroholografix 6y ago"Everyone". Obviously not. Having used IRC for 25 years, I'll take excellent SNR over the sort of focus on end user experience you're talking about.
- Karrot_Kream 6y ago> I'll take excellent SNR over the sort of focus on end user experience you're talking about The kind of SNR that causes an attempted takeover? As IRC has depopulated it's been increasingly inhabited by a particular type of person and has a particular culture. That's fine, but ascribing some technical superiority to it because of your cultural preferences doesn't make sense. IRC attracts a certain type of user who persists despite its UX; it's not technologically superior. The rest of us who aren't in that culture go elsewhere, to a network that fulfills our needs. Like Matrix (or even XMPP for some).
- otherflavors 6y agoMany modern IRCDs expose a websocket connection, if that's HTTP enough
- SilverRed 6y agoDoes the web socket let you see the history while your device was sleeping?
- carlhjerpe 6y agoirccloud allows this
- SilverRed 6y agoNot familiar with the service but is irccloud one of those services that sits in the middle and converts IRC to a modern http protocol for your device to consume?
- carlhjerpe 6y agoYes but not only. If you pay for their service It's also an IRC bouncer, meaning you can bring your own IRC client. It'll replay messages for you.
- secure 6y agoRobustIRC does this: https://robustirc.net/docs/robustsession.html https://robustirc.net/docs/robustsession.html (Disclaimer: I’m a developer of RobustIRC)
- sneak 6y agoThis is super cool! Where do you irc?
- danieloaks 6y agoFor what it's worth, we've been throwing around a websocket standard that should be supported across a range of servers. On the decoupling sessions from the TCP connection side, the server that I work on (Oragono https://oragono.io https://oragono.io ) does this by default, and I've heard that InspIRCd has plans to do work on this issue as well. Definitely a lotta fun stuff in this area.
- sneak 6y agoWebsockets over http over sockets is silly. There's no point in moving a socket based protocol to a websocket; if you're going to change it, make it just use HTTP and skip the terrible hack that is websockets in the first place. I like oragono and also wrote an ircd in go, and was inspired a bit by some of the project's code.