no-services by DalekIRC is a set of software(s) for UnrealIRCd which provides services-related functionality without having to rely on messaging a bot user.
The main software comes in two parts, the UnrealIRCd module and the web-hosted no-services URL API endpoint which the module talks to. This is the repository for the UnrealIRCd module.
IRC (Internet Relay Chat) services form the backbone of online communities, facilitating communication, collaboration, and the management of channels and user accounts. However, the current state of IRC services often faces challenges during network splits (netsplits), disrupting crucial functionalities and impeding seamless communication. Integrating IRC services functions directly into the IRC server, allowing them to communicate with URL API endpoints for managing account and channel settings, presents a compelling solution that addresses these shortcomings and offers a myriad of benefits.
Presently, IRC services typically operate as separate entities, independent of the IRC server infrastructure. When netsplits occur, these services lose connectivity and become unable to manage accounts or channels effectively. This disconnection leads to a lack of synchronization across servers, causing inconsistencies in user access, permissions, and channel management. Such disruptions degrade the user experience and hinder effective community management.
By embedding services functionalities within the IRC server itself, connected servers can maintain access to account and channel management capabilities even during netsplits. This integration ensures continuous service availability, enabling users to manage their accounts and channels seamlessly, regardless of network disruptions. The direct communication between the IRC server and the URL API endpoint for managing settings establishes a resilient and robust infrastructure that persists through network partitions.
Furthermore, consolidating services within the IRC server architecture enhances efficiency and reduces latency. Eliminating the need for external service connections streamlines the communication process, leading to quicker responses and smoother interactions for users. The centralized management of account and channel settings simplifies administration for network operators, promoting a more streamlined and cohesive user experience.
Additionally, integrating IRC services functionality into the server infrastructure enhances security and reliability. With a unified system, security protocols and access controls can be implemented more comprehensively, fortifying the network against vulnerabilities and unauthorized access. Moreover, the consolidated structure reduces dependency on external services, mitigating potential points of failure and ensuring a more reliable platform for users.
In conclusion, the integration of IRC services functions directly within the IRC server, communicating with URL API endpoints for managing account and channel settings, presents a transformative solution to the current limitations of IRC services. By enabling uninterrupted account and channel management during netsplits, streamlining operations, improving reliability, and enhancing security, this approach heralds a new era of stability and efficiency for online communities built upon the IRC framework.
Below is a list of commands which have been implemented so far and any plans regarding the future.
Following the Account Registration IRCv3 specification, you can register an account using /REGISTER with the following syntax:
/REGISTER <account name> <email address> <password>
Example:
/REGISTER Valware [email protected] FantasticPasswordWhichDefinitelyNobodyWillEverGuessLmao
You have two options here. You may either use SASL PLAIN as is standard in clients, or you can use the command /LOGIN to login to your current nick. In the future this will support specifying an account name to log into. The syntax is as follows:
/LOGIN <password>
Example:
/LOGIN FantasticPasswordWhichDefinitelyNobodyWillEverGuessLmao
/CREGISTER will let you register a channel, which sets mode the 'registered mode (+r)' on the channel and 'owner status (+q)' on you and the syntax is as follows:
/CREGISTER <channel name>
Example:
/CREGISTER #mychannel
no-services {
// your api endpoint, don't forget to use single quotes for this.
api-url 'https://example.com/no-services/v1/';
// your API key. you can define separate API keys in the URL API configuration.
api-key "insert your API key here";
// Account registration settings
account-registration {
// which options for account-registration
options {
before-connect; // let people register before they are fully connected
custom-account-name; // let people choose an account name
email-required; // require that people register using an email address
}
// a minimum password strength between 0-4
// 0 = no strength requirement
// 4 = very strong requirement
// defaults to 4
password-strength 4;
}
}
Using UnrealIRCd's built-in set::restrict-commands functionality, you can really fine-tune things to suit your needs.
set {
restrict-commands {
register { // account registrations
except { // but allow the below
security-group { tls-users; }
reputation-score 150;
}
}
cregister { // channel registrations
except { // but allow the below
security-group { tls-users; }
reputation-score 300;
}
}
}
}
The plan is to implement as many existing account/channel-related commands into the server, and also many more new things; from /AJOIN to manage your auto-join channels list to /VOTEBAN, a command channel staff can enable or disable for their channel.
At the time of writing this, the no-services project is very early on, and I'm only a few days into coding it enthusiastically.
If this has inspired any ideas in your mind (you, the reader), please open an issue in the github repository and I'll be more than happy to consider it.