RelayServ is a Techtronix service that allows channels both on and off the network to be interlinked together, creating more communities available under Techtronix. Techtronix relay services operate almost invisible to everyday operations of the network and they work to provide more of a complete user experience by substituting in remote content where organic content is unavailable. A great example of this is #rcfreak0, which is a Minecraft community.

RelayServ can be identified as simply RelayServ on the network and isn't controllable by users. If you'd like a channel linked to or from another network, please contact Techman or another staff member. The below information is primarily intended for network operators who have been linked to this page but is also available to everyone else for the sake of knowledge.

Networks linked are identified in the user list by their "short name". For example, "freenode" has a short name of "fn". Techtronix is referred to as "ttx".

Types of Links

There are two types of links that are available from RelayServ: client bot, and server-to-server (s2s).

Client bot

A relay bot created from the relay service connects to the remote IRC channel and relays content back and forth. Users in the remote IRC channel appear as channel members on Techtronix, but all messages appear from the relay bot to the remote channel. Typically, the name of this bot is ttx or techtx. Client bot relays are the easiest to implement, but they don't offer the most seamless integrations. A server-to-server connection is the best for smoothness.

Users of Techtronix will see nickname/<short name> in their user list, and messages show as coming directly from the relayed user:

02:04:30 PM --> Little/ef (PyLink Relay Mirror Client) has joined #rcfreak0

01:47:18 PM <poxifide/ef> hi

The relayed channel will have the ttx bot relay items in this format:

02:58:29 PM <@ttx> <Techman/ttx> hi

03:01:54 PM <@ttx> - Techman/ttx (Techman@Techtronix/operations/Techman) has left #rcfreak0 (I needed to cycle this chan as an example so sorry)

Server to server

The actual relay server itself connects to one of the IRC servers of the network hosting the remote channel, opposed to just a simple IRC bot sitting in the remote channel. Users on both sides of the relay appear organically in the user list, and all common channel modes, as well as topics, are synced. Sending private messages to remote users is also more fluid this way, as talking to a remote user on a client bot relay requires the user to message the relay bot itself, beginning all messages with a command to make sure that the message is routed to the correct person.

Users on both networks will see messages in the format of the first example above.