Proprietary Server Administration Architecture
For a few years Incorrigo Syx has maintained what will always be a proprietary core. We want to preserve that but at the same time make room to grow beyond this core and welcome communities who might see the opportunity to set down some roots here
We have been working on a new design so that everything will keep that consistency throughout the entire network and, aside from the infrastructure element of things, have drawn up a charter in the time being that we believe could be possible to accept
PSAA Charter
Incorrigo Syx has the control of its core network. And would need an exclusive control of the configuration file. As a part of that core and for user account services, we also operate the network manager
| Proprietary Administration Agreement | ||
|---|---|---|
| 01 | Financial Framework | Diversity in IRC is mission critical. Not just the load capacity of another server, but a geographical, cultural, interracial, reach in all kinds of places with all kinds of people. But it must be agreed on a server by server basis |
| 02 | Configuration File | Complete control of the server's configuration file is needed by Incorrigo Syx. This is essential to implement the shared network architecture and operating security. If necessary we are willing to make the arrangements and forward your payments for the required operating expenses with your provider |
| 03 | Server Name | Even though this is unusually prominent for all networks to push their personal perception of clever and cool sounding things, we don't have some sad sort of sick sounding selection of servers. But if you really insist on choosing this we can entertain suggestions. You might even come up with something that will sound brilliant |
| 04 | Server Administration Team | The server admininstrator will appoint any people who will assume the appropriate operclasses that will be defined in the distributed config but only granted on the servers they are responsible for
Note: Distributed configuration will not be shared or seen by any server administration team. TLS client certification will be provided and entrusted to every member of your server's staff
|
| 05 | Server Software Specification | The software for all servers will be maintained with the most up to date & stable release of UnrealIRCd |
| 06 | Network Manager | All servers will accept the network manager and nominate it as their SASL server. Also - but ONLY one that's on the same network - the server administrator will decide where the traffic will go i.e. when the server is full and things like that
Note: Our network manager is maintained & up to date with the latest 'solid' release of Anope Services
|
| 07 | Mass / Ops Communication Scope | The server administrator will be added to the group for global communication privileges. Operators who may be appointed by the administrator will be given full access to local and mass local communications. Access to the creation and reception of /WALLOPS messages will work the way wallops walways does |
| 08 | Internal Channel Affairs | Both Incorrigo Syx and the server operating team will stand united on the professional courtesy of we will not intervene in channel affairs, Think of it as some kind of prime directive, and remember how grateful get when you row the boat over to try and rescue them from drowning |
| 09 | The Bigger Picture | Our banning system removes people automatically and we will not dole out any exceptions to it. It deploys and co-operates with the centralised API infrastructure, which involves sharing most of an incoming client's handshake at logon time - except for certain cases when a trusted user is identified - with a trusted third party who develops our server software. It might not be a good idea to try and connect via an open proxy that might trigger our banning system because it has been misused during a computer attack |
| 10 | Determine Listening Ports | Incorrigo Syx core will maintain a plaintext presence - but a server administrator can choose whether to accept plaintext connections or not, and are under no such obligation to do the same. The minimum criteria is to provide properly certified TLS access on ports 6697 and 9999 |
| 11 | Strict Transport Security | All servers will advertise the network-wide STS secure port: 9999 |
| 12 | A Helping Hand | It is not mandatory but those who are willing and able to assume a few extra responsibilities and answer people who come to #help will be gratefully appreciated |
| 13 | Charterial Newness | This charter is likely to be subject to change. Just saying, it would not be such a bad idea to check for updates when you remember to click on the link |
[ Back to Top ]