danieloaks

Joined 11 years ago

Karma
80
Submissions
35
Member since
Feb 21
I do IRC and chat protocol stuff

https://danieloaks.net

[ my public key: https://keybase.io/danieloaks; my proof: https://keybase.io/danieloaks/sigs/tZz_CwIi3s4fVXBPbsIahd5lq4B_xu8pUxedVm-yItQ ]

View on Hacker News

Recent submissions

Comment · 5 years ago
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 rust ones out there.

GUI-wise there's HexChat, mIRC, Quassel, lots of interesting options to look at.

May be worth digging through these tables a bit more if you're interested: https://ircv3.net/software/clients

Comment · 5 years ago
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 of them at one point, but I respectfully declined.
Comment · 5 years ago
Comment · 5 years ago
inspircd++ Sadie and everyone who works on insp are great too <3
Comment · 5 years ago
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. Especially with things like https://sr.ht/~emersion/gamja/ and self-hosted https://kiwiirc.com/ , as well as really polished client experiences like irccloud, it's easier to convince people to join in.

Right now I'm working with a dev from libera on a client that aims to replicate a lot of things experience-wise from newer chat services. Hoping that with that, smaller self-contained servers can become more of a norm~ But for now, your best bets for finding activity are probably Libera and a couple of the other larger networks.

Comment · 5 years ago
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
Comment · 5 years ago
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 unrelated to him, same as my other project https://ircdocs.horse/

It's totally fair to make that link, but I very explicitly told everyone over at LTM/H (including PIA and Handshake) that Oragono/Ergo and ircdocs were not work projects in any way. And while I was working on Shells.com, I was very explicit that I wouldn't be touching any IRC stuff for money while there.

But yeah, it's definitely good to be wary of these kinda links, given what happened to snoo's and fn/libera's team. If you wanna ask any more questions about my stuff in particular, feel free to ask here or send me a mail at [email protected]

Comment · 5 years ago
Comment · 5 years ago
Comment · 6 years ago
Yeah moved away from Ruby a while back. Took a little while to stabilise but the new app is a lot better these days.
Comment · 8 years ago
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 business-oriented resources like designers/legal/etc, as well as simply improving the quality of protocol documentation out there (the part I'm handling).

In terms of strict protocol improvements, the IRCv3 WG is the real place where that's going on, the most authoritative thing in terms of introducing new stuff across the IRC infrastructure these days: https://ircv3.net/

But, for new developers looking to get into IRC today, the resources aren't as available as they could be. Sure, there's a bunch of code to look at, libraries you can use to get started that seem to work fine. But when you wanna start digging into the wire protocol, how particular commands or functions work, how to actually approach writing a client/server from scratch, all you have are either the RFCs, some newer resources like the ircdocs/IRCv3, or stuff spread across 20+ year-old textfiles and pages all across the net. My intention for the documentation side of the Foundation is to build up information on how to use/parse commands and numerics, how widely they're used (in terms of software support), and how to really dig into and approach development with the protocol – since that feels like the more valuable information to be out there right now for new devs. It'll be linked to and public sometime soon, it's just that building up a swathe of documentation large enough to show we're serious about it takes some time (if you want those docs to be decent-quality, at least).

For what it's worth, I'm both the primary writer/maintainer of the Foundation's developer docs work, and the maintainer of the more community effort https://ircdocs.horse/ , so hopefully I'm on the right track with supporting devs in the protocol documentation sense.

If there's any questions or suggestions for directions to take on this (stuff that you, as a dev, would find useful for writing IRC software), please let me know! Even if it's not there for initial launch there's a fair backlog of stuff I'm looking to make up with this project.

Comment · 9 years ago
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 years old, respectively. RFC 1459, very commonly referred to and still the first reference for a lot of IRC software authors, came out before I had my first birthday!
Comment · 9 years ago
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 great, but the simplified CTCP I-D improves things for clients. DCC I'm documenting, hoping we can replace it with something more appropriate and/or extend DCC as it currently exists in a backwards-compatible way (there's a loooot of debate and discussion on DCC in the v3 WG. once we fix up a bunch of misc protocol stuff it's definitely something we'll approach).

For sure, simplicity is better than complexity. A fair amount of the v3 work aims to simplify things that are already done in a bunch of vendor-specific ways and bring them all under one clean, well-specified roof. Always happy for extra help there :)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton