v2.1a7

[incorrigo]

Incorrigo Syx Script v2.1a7

Maiden release following the progress of development being upgraded to being a GitHub repository

First Release Notes

Being the first official release, the notes can only logically document the transition from being nothing to being something. Here are the currently existing features

• Away Manager
  Away, Auto Away, Away Reason Rememberer, Away Reminder Messages (on CTCP, query, notice, and being mentioned in channel)

• CTCP-X
  Moving in the direction of the future in IRC, CTCP-X is a combination of server and client implementation to continue client development in the direction of the working group and the specifications of IRCv3 (more info further down)

• Permutating Popup Menus
  Functionality that takes your overall control well into the reaches of an IRC operator that heavily cuts down on the need to manually use commands

• Help Text Documentation System
  Much effort has been taken to introduce someone who would be new to the client, let alone the protocol. Many revisions have been made to make it increasingly less of an effort to read, more of a simplicity to understand

• User Account Auto-Login
  Even though the options provided by mIRC are more than adequate, user information - with optional settings to support securely stored account credentials, and even SASL authentication using a TLS certificate - has been given a robust / more simplified interface which will re-write the /server command each time you wish to change your preferences re: automatic user account login or server connection settings

• +draft/reply and +reply Fully Supported
  A tried and tested implementation of the IRCv3 specifications concerning the client's ability to reply to specific messages, working in both private and channel conversations. This simple feature has been a creature comfort for world-leading instant messaging platforms, and several other IRC clients who are also positive about moving forward to the future of IRC

• DCC File Transfer / Chat Implementated Work
  One of the unique attributes that IRC brings to the table beyond simple instant messaging, is the capability to form de-centralised peer-to-peer links and exchange files, or more privately intimate conversations. Although this is built into mIRC and possible without having to write scripts about it - Incorrigo Syx Script provides the right settings pre-configured into the repository's mirc.ini file. In addition to this, there are menu driven controls for the purposes of the /DCCALLOW list, DCC ignore, the DCC trust list (which can be used to automate the file transfer process with automatic acceptance) ... everything you should need for the correct, working use of the DCC capabilities, is provided to you when you right-click a user in the channel's user list

• A Complement of Capably Clever Commands
  Even though there are some convenient aliases which are built into the server configuration across our network, a number of aliases and identifiers that would bring swift and elegant benefits to any mIRC script can be found throughout all of the script's files, many of them easily adaptable for someone else's script. Though there is no way to enforce this in any realistic situation, we would ask that you give us a nod if you decide something is useful for your own technological pursuits

• Multi Session Script Support
  Although not all features are designed this way, some diligent investment of time and effort has been put into giving the (a) popup menu interface (b) online and background timer functions (c) user account login and current status tracking (d) command adaptation and responses to client requests (etc.) a robust multi-connection support, in an attempt to give you the added possibility of using the script for more than one IRC session, simultaneously

• Incorporation of Info Boxes & User Input Prompting
  Some extensive input and decision prompts have been carefully placed to present you - assuming no expert knowledge - with information and choices that are yours to have and make, in a way that properly reflects the situation that you're in. One may miss an error for instance, because it was quietly placed in the status window, when they might think it ought to be more prominent when trying to join a channel ... to tell you that it is an invite only channel or that you're banned. Further to that, a user might not be aware that they have the ability to knock on invite only channels with an optional message. The comprehensive work given to the feature of user inputs attempts to account for all of this

• A Deep & Exhaustive Menu Map of Network Services
  Incorrigo Syx has user account registration, and full network services, which includes the support for services vHost, and the ability to assign and configure channel bots for services registered channels. In addition to things like having every settable mode, complete with explanations for every single one of them, Incorrigo Syx Script currently has a very convenient grasp of the commands available which will be displayed when you are successfully logged into your user account. As with other things, the functionality mapped out for our range of network services (and their commands) would be easily adaptable to fit other scripts as preference changes, but we think you will find our script sufficiently handy; enough to appreciate what we have provided at the touch of a mouse button and accept our implementation the way it is

• Operator Services
  Because we have found this script gradually more convenient ourselves, additional services commands are unlocked should you be simultaneously logged into an account and also an IRC operator

• Full Specification & Input User Prompting of All User & Channel Modes
  As is the case with a network who uses the same IRC services that we do, an unbelievable undertaking has been invested in making sure you (a) know about modes (b) know what modes are (c) understand user vs. channel modes (d) know the 3 channel llist modes (e) know the five channel status modes (f) know what every single mode does (g) know what extended bans are (h) have a complete and extensively tested UI that acts as an extended ban 'wizard' with even more built in hints telling you what each and every part of it means. If a mode or target type has a parameter, you will be prompted to give it. And if you click cancel, then the process is cancelled

• Full Importation of mIRC Options
  Before you first run mirc.exe when you have extracted the complete repository / files and folders, into the same directory, the mirc.ini file along with other things are meant to be over-written. This doesn't just create the ideal conditions for the script to operate smoothly / stay fresh. Some of the more meticulously located settings have been pre-configured, which will give you more than you would otherwise have with a new install. One example of this is the default colour scheme that's in place. Another more explainable configuration is the setting of nickname colours. When you connect to the network and join a channel, the nicknames are differently coloured according to their status on the channel / being on your ignore list / if they are using a server side vHost / if they are an IRC operator. Mostly the pre-setting of mIRC options using the mirc.ini file ensures that say if two users using the script encountered one another on IRC, certain settings like the DCC configuration would be more compatible. This has been one of the particularly rough details that emerged during early testing

IRCv3 Information / Relevant Parts of the Script

These things have been scripted to accommodate IRCv3 specifications that are fully supported on our network...

• Visually contradistinguished channel messages vs. currently iterating chathistory batch output
• Gathering of appropriately time-ordered message data information using a channel's playback-on-join
• Activation of the echo-message capability to facilitate gathering of data attached to own messages
• Scripted (but currently not activated) display of someone's gecos from the event of them joining a channel
• Temporary construction of a model including private and channel PRIVMSGs that is maintained until mIRC is closed
• Continuous analysis of that model to facilitate features that can be used to make the script compatible with other IRC clients
• Announcing the commencement and ending of batch messages, including when one appears to be empty
• Parsing instances of the invite-notify extension to make the alert of an invitation that takes place more prominent
• Analysis of SASL numerics to track current user account status, also mindful to monitor nick changes etc.

CTCP-X Implementation & Pragmatic Demo

This is not concurrent with existing specifications on the naming of client-only tags. Incorrigo Syx Script contains a client-side implementation of a new concept named for now ctcp-x which, in the current message tags specification (https://ircv3.net/specs/extensions/message-tags.html) states that client-only message tags are intended to replace the use of future CTCP commands ... while there is much more than this in the overall specificaiton of IRCv3, a decision was made to implement two client-only tags on the network ... which have been called +ctcp and +ctcp-x

Conditional Considerations

Given that it is highly unlikely any other IRC client or script will support any of these client-only message tags, and that there will be no practical use for them because they will not be supported on any other network - CTCP-X was constructed according to a number of self-imposed conditions ... giving the environment of validation / conditionality of values, and making the usefulness something that could be determined in the would-be circumstances it would ever exist, such as the maximum length / escaped characters (something that will be standard between IRC clients, for instance)

(a) The initial condition is that these two tags can appear either one at a time, both at once, and neither at all
(b) These two tags can contain anything, and have a maximum length of the maximum possible message tag length
(c) Any usage of these tags shall not be in any attachment to another message (i.e. TAGMSG, not PRIVMSG)
(d) The value of either of these tags shall be pre-written, and not individually typed
(e) Values of either or both tags will be sent only according to the rules of the escaped values in the IRCv3 Message Tags specification
(f) In the same nature a value must be pre-written, any corresponding value given in response must be automated respectively

How to Use

To use CTCP-X, connect two clients to the network using two different machines. Then join a mutual channel. Then one client rightclick on the other's nickname in the channel list (CTCP(X) Request) and choose a request in the section of the menu starting with "Friendly Name" and finishing with "Website"

• Developers: responses are not currently very mutable. you can open the debugging window with editbox to act as a command line by using the /thematrix command.

For other features, the echo-message capability is activated upon successful connection, so you will be able to view your own messages. Answering requests made to yourself causes certain problems, so if a self-request is detected it will be ignored.

Welcome to Incorrigo Syx Script v2.1a7

The Incorrigo Syx project goes far deeper than a simple IRC network. This is just one element of my life I am able to share with a computer-generated audience. I don't know how long I'm going to be here for beyond that ... so you congregate, and idle til your heart's content. Make the most of now. Thank you for attending this page to bear witness to the release of 2.1a7

---

This discussion was created from the release v2.1a7.