BeeIRCd

Your own IRC network, with the services built in.

BeeIRCd is one program that runs the chat server and NickServ, ChanServ, MemoServ, OperServ and AdminServ. Set it up with a few questions, change it from IRC while it runs, and keep the IRC you already know.

In development. Not ready for public networks yet.

Five services, one program

No separate services package to link and keep in sync. The services answer the way they always have, with a short notice and the next step to take.

NickServKeeps your nick yours. Identify with a password or SASL, group nicks, recover a ghost./ns register <password>
ChanServKeeps a channel yours. Founder, SOP, AOP, VOP and UOP levels, AKICK, mode and topic lock./cs register #channel <description>
MemoServMessages for people who are away, and memos to a channel's founder and SOPs./ms send ember see you at nine
OperServThe oper toolbox. Network bans, kills, global notices, forbidden nicks and channels, session limits./os akill add *@203.0.113.* 7d spam
AdminServChange the server while it runs. Every change is saved to the config file, with your comments kept./as port add 6697 tls

Familiar on the outside, modern underneath

Inspired by ConferenceRoom: one server with everything in it. If you have run UnrealIRCd or InspIRCd, you already know how to use it.

What stays the same

  • The commands, modes and numerics your client and bots expect.
  • Services that answer with a short notice and a next step.
  • Opers with single-letter flags, and /oper, /kill and /wallops.
  • One config file you can read, and logs that say what happened.

What's new

  • IRCv3, so modern clients get typing, replies, history-ready message IDs and SASL.
  • Cloaked hosts by default, TLS 1.2 or newer, flood control that slows senders down instead of dropping them.
  • Opers are opered when they identify, so no second password sits in client configs.
  • Written in Go from scratch, with server linking designed in from day one.
saslmessage-tagsserver-timeecho-messagelabeled-responsebatchaccount-tagaccount-notifyaway-notifyextended-joininvite-notifychghostmulti-prefixuserhost-in-namescap-notify

Where it stands

Built in four stages. Each stage is tested on a real server before the next one starts.

Stage 1, in progress

One server, all services

  • Core chat server
  • IRCv3, SASL, cloaks
  • NickServ and MemoServ
  • ChanServ
  • OperServ and AdminServ
Stage 2, planned

Server linking

Link BeeIRCd servers into one network, with services on the hub.

Stage 3, planned

Hive Panel

A calm web dashboard for admins: people, servers, opers and bans, from a phone too.

Stage 4, planned

BeeRoom

Chat from the browser, on the same server, with nothing extra to install.