We want to showcase our project to the intelligent folks present at FOSDEM with the hope of getting valuable feedback and contributors. We are also trying to develop a reactive store layer to empower realtime applications, in our case, waartaa. You can find some insight about it in our initial design docs 3. We are also brainstorming to figure out an intelligent way to load balance connections from IRC clients to the bouncer service in a stateless fashion. That's why we are looking forward to have a multi node model for ircb, where we can intelligently distribute the IRC network connections, as needed.
We came to know of this during maintaining a demo instance of waartaa on a single node, when Freenode will stop rejecting IRC connections from our IP. IRC networks limit the number of connections for an IP, and this limit has to be manually negotiated, and the process takes time. So, we started breaking down the app into micro services. On IRC, a bouncer (often shortened to BNC) is a program that allows a user to stay connected to IRC indefinitely, even when they go offline or turn off. However, we hit various roadblocks with the initial code base given to it's monolithic structure. We also participated in GSoC under theįedora umbrella. waartaa is our attempt to create an open source SAAS communication and collaboration tool, around IRC. It also envisions to provide a low barrier entry point for users, where users can join and start using the service in an automated fashion, without going through manual processes.Īlthough, ircb is a standalone product, it is also one of the core components of waartaa 2. It aims to provide a scalable bouncer service along with easy setup, deployment and management. It's currently functional as a basic IRC bouncer, however, unlike mainstream IRC bouncers, it supports multiple client connections for the same IRC network connection for a user. Ircb 1 is a IRC Bouncer as a service, made for humans.
0 kommentar(er)
