Viewing profile — danieloaks

terminal-wise, irssi and weechat are the traditional ones recommended these days. but there's a couple newer ones like catgirl: https://git.causal.agency/catgirl/about/ and some ru…

Yeah we didn't need to agree in writing because I didn't sign anything giving them access, control, ownership, or anything else over my IRC projects. They offered to purchase one o…

Ah! So what we have right now is a websocket API (so clients can speak IRC via websockets), and our default config basically turns the ircd into a 'bouncer' (it automatically stays…

inspircd++ Sadie and everyone who works on insp are great too <3

It depends. There's a lot of people on/around IRC who really like it (see libera and all the other networks), and yeah there definitely are people spinning up new smaller networks.…

To be fair there was also collaboration between PIA and Linux Mint while I worked at PIA. That'd probably be a question best answered by the Mint people who're involved

Oh haha, hey! I was employed by Andrew across a fair few of his companies (I didn't know Shells.com was owned by him while I was working there though). Buuuut this is entirely unre…

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, th…

I can't speak for their possible ircd transition plans but OFTC's been working on https://solanum.chat which has a wide range of IRCv3 support.

Yeah moved away from Ruby a while back. Took a little while to stabilise but the new app is a lot better these days.

For the most part, the Foundation's just a project to support existing projects and developers who use the IRC protocol. This can mean providing financial support, access to more b…

Can't speak for software but in the case of these specs, 'Modern' in the title pokes fun at the fact that the core protocol specifications most people refer to are around 25 and 18…

For what it's worth, there's been a bunch of work around backlogs (to simplify bouncers, though if more niche IRCds wanted to incorporate it natively that'd work too). CTCP isn't g…

These specifications just capture how the IRC protocol currently operates, so that isn't described here (isn't widespread afaict, and there isn't a clear 'winner' in terms of imple…

Yep, pretty much. Unfortunately the protocol's gotten fairly complex without standardisation to keep everyone on the same track. I do my best to simplify the text where I can, but …

Thanks, I'm glad it's useful! Feel free to check out this page for some other useful links if you dev on it in the future: https://ircdocs.horse/info/ :)

The first page I wrote when I was making the site was this one ( https://ircdocs.horse/specs/ ) – and the initial drafts were a fair bit screechier than what's there now. I wanted …

Yeah, I admit the title's not great. I'll update it in the next few days, thanks for the feedback :)

Thanks for posting this here! I will admit, it's hard to know when to start posting it around, but this is already a fair bit more accurate than the traditional RFCs in a lot of wa…

This project (ircdocs) works in tandem with IRCv3. ircdocs tends to focus on currently-implemented stuff (such as the linked Modern docs), where v3 focuses more on establishing rou…

For now, yeah. Devs from various servers are experimenting with alternate s2s protocols aiming to solve this though.

Standardisation is weird in IRC. From what I've seen, most of it that has happened has been the result of one group implementing their custom command/extension and then a bunch of …

That's a really interesting look at the politics between those two. Applies to some stuff I'm involved in too. Useful link, thanks very much for sharing!