News for hackers. Stuff that matters.
Re:IRCv3 by sneak on Wednesday May 19, 2021 @03:58PM (#27213700)
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.

Re:IRCv3 by metroholografix on Wednesday May 19, 2021 @04:10PM (#27213831)
Not everything has to run on top of HTTP or use json.

IRCv3 gets a lot more right than wrong.

Re:IRCv3 by SilverRed on Thursday May 20, 2021 @12:02AM (#27217242)
Using HTTP would be an absolutely massive improvement for IRC. IRC is essentially useless on mobile without having some man in the middle server to convert IRC to http.

It's even pretty useless on laptops or desktops that aren't always running.

Re:IRCv3 by Nasreddin_Hodja on Thursday May 20, 2021 @04:23PM (#27226688)
> IRC is essentially useless on mobile without having some man in the middle server to convert IRC to http.

That's not true. I used HoloIRC client on Android with no problem.

> It's even pretty useless on laptops or desktops that aren't always running.

There is no need to. If it's about talks history, chats are not right tool then, forums are more convenient.

Chats are suitable for casual or urgent instant discussions. In all other cases forums are better because user doesn't have to present during discussion, he can return and comment any time he want.

Re:IRCv3 by SilverRed on Thursday May 20, 2021 @09:23PM (#27229503)
>There is no need to. If it's about talks history, chats are not right tool then, forums are more convenient.

This sounds like a fox and the grapes situation. You can't see history on IRC so rather than noting the deficiency, you list it as a feature.

As a modern IM user, I am part of many low volume groups and the history is essential as there will usually only be 5 or so messages in the day which I would have just missed if I had used IRC. I agree that history on a fast pace 100 member chat is not so useful but not having it isn't a benefit either.

Re:IRCv3 by GekkePrutser on Thursday May 20, 2021 @12:06AM (#27217266)
Quassel and the mobile Quasseldroid app fix that and more :) They add a lot of mod cons like infinite scrollback, persistent connection and multi network bouncing with a really good UI.
Re:IRCv3 by threeseed on Wednesday May 19, 2021 @07:24PM (#27215703)
If 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.

Re:IRCv3 by metroholografix on Wednesday May 19, 2021 @08:03PM (#27215926)
So 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.

Re:IRCv3 by threeseed on Wednesday May 19, 2021 @08:06PM (#27215940)
Which is why everyone uses Slack, Teams etc and IRC is irrelevant.

Because there wasn't enough focus on end user experience.

Re:IRCv3 by metroholografix on Wednesday May 19, 2021 @08:41PM (#27216133)
"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.
Re:IRCv3 by Karrot_Kream on Wednesday May 19, 2021 @08:54PM (#27216199)
> 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).

Re:IRCv3 by Dracophoenix on Wednesday May 19, 2021 @09:14PM (#27216308)
>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.

If you mean anime subbers, 4channers, and the warez/pirate crowd , they've all moved to Discord or Telegram. The only ones left are the technically inclined folk who adopted the platform at its genesis (i.e. #c, #perl, etc.)

Re:IRCv3 by Karrot_Kream on Wednesday May 19, 2021 @10:24PM (#27216643)
No I mean the technically inclined. Adding a layer of gatekeeping just means folks who are okay with that keeping make it across. IRC has a very particular culture.
Re:IRCv3 by metroholografix on Wednesday May 19, 2021 @09:44PM (#27216464)
You're being disingenuous. IRC has been right at the center of the vast majority of non-enterprise technical communities and especially opensource for the last 25 years.

Say what you will about culture but this is a fact and I don't see it changing. Slack and Teams are gimmicks at best. Matrix unusable for me, every single one of my peers and, apparently, the vast majority of said technical communities that keep their center of operations firmly entrenched in IRC.

Re:IRCv3 by xvilka on Wednesday May 19, 2021 @10:30PM (#27216686)
We recently switched to use self-hosted Mattermost plus Matterbridge[1] to connect with IRC, Telegram, Discord, etc. There is also an amazing console client - Matterhorn[2].

[1] https://github.com/42wim/matterbridge

[2] https://github.com/matterhorn-chat/matterhorn

Re:IRCv3 by sneak on Thursday May 20, 2021 @02:15PM (#27224948)
Note that mattermost by default phones home to a spyware analytics service even when you selfhost it. The env vars for disabling it are hidden/undocumented.

Copy the diagnostics/securityalert env vars from here, as well as the sed lines:

https://github.com/caprover/one-click-apps/blob/master/publi...

Re:IRCv3 by it33 on Thursday May 20, 2021 @03:55PM (#27226300)
Mattermost CEO here, thanks for the share out! We're big fans of Matterbridge and Matterhorn as well!
Re:IRCv3 by xvilka on Sunday May 23, 2021 @08:07AM (#27254445)
I hope the categories that are already available in the Web client will be available in the mobile [1] and Matterhorn [2] clients too.

[1] https://github.com/mattermost/mattermost-mobile/issues/5387

[2] https://github.com/matterhorn-chat/matterhorn/issues/711

Re:IRCv3 by threeseed on Thursday May 20, 2021 @08:29AM (#27220267)
Weird. I contribute to a lot of open source projects.

Never once used IRC. Discord, Slack, Gitter but never IRC.

And love the idea of Slack being a gimmick.

Re:IRCv3 by mech422 on Thursday May 20, 2021 @05:58AM (#27219286)
slack has to be the worst 'end user experience' I've had with messaging. The threading is horrible, the client is huge and regularly 'stalls' (garbage collection?), and the voice chat is laggy as all get out. Basically, for large international orgs - it seems to be more trouble then its worth...

about the only highlight is ease of creating bots for monitoring and automation.

Re:IRCv3 by hedora on Wednesday May 19, 2021 @09:42PM (#27216454)
This should fix the “broken enterprise network” problem:

https://www.stunnel.org/

Listen on port 443; problem solved until they switch to server allow lists.

Re:IRCv3 by danieloaks on Wednesday May 19, 2021 @06:25PM (#27215316)
For 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 ) 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.
Re:IRCv3 by sneak on Wednesday May 19, 2021 @07:28PM (#27215722)
Websockets 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.

Re:IRCv3 by otherflavors on Wednesday May 19, 2021 @04:12PM (#27213858)
Many modern IRCDs expose a websocket connection, if that's HTTP enough
Re:IRCv3 by SilverRed on Thursday May 20, 2021 @12:02AM (#27217244)
Does the web socket let you see the history while your device was sleeping?
Re:IRCv3 by carlhjerpe on Thursday May 20, 2021 @12:42AM (#27217453)
irccloud allows this
Re:IRCv3 by SilverRed on Thursday May 20, 2021 @01:23AM (#27217709)
Not 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?
Re:IRCv3 by carlhjerpe on Thursday May 20, 2021 @02:05AM (#27217953)
Yes 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.
Re:IRCv3 by secure on Wednesday May 19, 2021 @05:36PM (#27214793)
RobustIRC does this: https://robustirc.net/docs/robustsession.html

(Disclaimer: I’m a developer of RobustIRC)

Re:IRCv3 by sneak on Wednesday May 19, 2021 @07:30PM (#27215738)
This is super cool! Where do you irc?
Re:IRCv3 by pantalaimon on Wednesday May 19, 2021 @04:10PM (#27213829)
What's the advantage of using HTTP?
Re:IRCv3 by sneak on Wednesday May 19, 2021 @04:12PM (#27213859)
I 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.
Re:IRCv3 by swiley on Wednesday May 19, 2021 @04:19PM (#27213949)
I 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.
Re:IRCv3 by sneak on Wednesday May 19, 2021 @04:28PM (#27214051)
Reverse 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/

It's messy. The tooling around TLS and reverse proxying for HTTP is much more common and easy.

Re:IRCv3 by progval on Wednesday May 19, 2021 @05:26PM (#27214681)
> 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

It's supported by all the major IRCd implementations these days.

Re:IRCv3 by sneak on Wednesday May 19, 2021 @07:31PM (#27215743)
Terrible hacky custom extensions like this is precisely why I just want to talk to it via HTTP.
Re:IRCv3 by progval on Wednesday May 19, 2021 @07:38PM (#27215785)
How is this more hacky than X-Forwarded-For + X-Forwarded-Host + X-Forwarded-Proto?
Re:IRCv3 by Karrot_Kream on Wednesday May 19, 2021 @04:42PM (#27214208)
Indeed, 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).
Re:IRCv3 by toast0 on Wednesday May 19, 2021 @04:57PM (#27214375)
Is 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.

Re:IRCv3 by threeseed on Wednesday May 19, 2021 @07:30PM (#27215740)
Whether 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.

Re:IRCv3 by tastyfreeze on Wednesday May 19, 2021 @04:09PM (#27213824)
What 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.
Re:IRCv3 by SilverRed on Thursday May 20, 2021 @12:04AM (#27217255)
At 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.
Re:IRCv3 by petre on Thursday May 20, 2021 @12:37AM (#27217424)
MQTT 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.