Using TTCom, the TeamTalk Commander
Doug Lee
Last Revised September, 2020

This is the user guide for TTCom, the TeamTalk Commander, also informally referred to as the TeamTalk Console or the TTCom text client. This client is mostly for managerial (not necessarily administrative) functions and is not an audio or video client. TTCom may be of use to those meeting any of these criteria:

• TeamTalk server managers and administrators who want quick ways of accomplishing some tasks from a command line, such as account creation/modification, moving users among channels all at once, and managing ban lists.
• Server owners who want to see TeamTalk events in real time and/or in a summarized form without having to paw through a server log file. (TeamTalk logs more events in server logs than it sends to clients, including TTCom; but many events are sent both places.)
• Technically-minded users who just want a quick glimpse of who is where among all their TeamTalk servers now and then without having to log into one server at a time and scan through a treeView for each.

This document describes how to install, launch, and use TTCom and its command set. For information on recent updates, or to see a history of TTCom's evolution, see the final "Release History section.

This program is Copyright (C) 2011-2020 by Doug Lee and falls under the GNU General Public License as found in LICENSE.txt. iniparse, included in its entirety, comes with its own license (also included).

TTCom is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program as LICENSE.txt. If not, see http://www.gnu.org/licenses/.

Table of Contents

• System Requirements
• Quick Installation and Startup Instructions
• The Lint Command For Diagnosing Configuration File Problems
• Known Issues
• Revision History

System Requirements

TTCom should run on any operating system where Python 3.7 or later can be found. Python (though not necessarily a new enough version) comes by default on at least Linux and MacOS. It can also be installed on Windows, though a stand-alone ttcom.exe application is provided for Windows users to avoid the need to install Python.

This author is aware of users having successfully used TTCom in the following environments, run from source unless otherwise indicated:

• Windows Vista, 7, and 10, 32-bit and 64-bit versions, with Python 3.7 installed or via the stand-alone ttcom.exe application.
• 32-bit and 64-bit MacOS versions.
• Various Linux distributions.
• iOS under iSH with Python 3.7 installed, though it may log out of TeamTalk servers when the device lock screen appears. There may be other ways to run TTCom on iOS.
• Android under Termux.

Quick Installation and Startup Instructions

1. If running from source on Windows or if your OS does not include Python 3.7 already, install Python 3.7. Possible sources of Python 3.7 include
   • http://www.python.org/ (preferred by this author for Python 3).
   • http://www.activestate.com/activepython (requires an account and updates Python as a service).
   Some operating systems include a package distribution system that simplifies Python installation. If you are using the Windows stand-alone executable ttcom.exe or your system already includes an appropriate Python version, this step is not necessary.
2. Download the TTCom Zip file and unzip it into a convenient folder.
3. Copy ttcom_default.conf to ttcom.conf and edit to taste. This is where servers and per-server behaviors are defined. The autoLogin parameter determines which servers connect automatically on TTCom startup.
4. This author recommends setting a nickname for all servers at once by including something like this in ttcom.conf:

   [server defaults]
nickname=My Name


   If you don't do this, you will be called "TTCom User" everywhere you go. Of course, change "My Name" above to what you want as a nickname.
5. If you want events to print as they occur for only the currently selected server, instead of for all connected servers, include silent=1 in the above section. See ttcom_default.conf for further ideas.
6. On Windows, run ttcom.exe. If running from source (on Windows or anywhere else), run TTCom by running ttcom.py through Python 3.7:

   python3 ttcom.py

   Warning: Just typing "python ttcom.py" may try to run TTCom through Python 2, which will not work. If you get errors, make sure you are running Python 3.7 by typing python -V to check the version number.

The final step above will launch TTCom and connect to all servers with an autoLogin value above 0. As an alternative, you can specify a server or servers on the command line, by their shortnames from ttcom.conf, to connect to just those servers:

python3 ttcom.py simon

To start TTCom without connecting to anything, use -n in place of a server name.

Once TTCom is running and you see a "TTCom>" prompt, type "?" or "help" at the TTCom command prompt to learn what is possible. You can add a command name for help on that command; e.g., "?whoIs." Case is not important in command names.

The Lint Command For Diagnosing Configuration File Problems

If you experience unexpected problems with your TTCom configuration, such as strange errors or updates that seem not to take effect, try typing "lint" as a command in TTCom. This will scan your configuration file and report anything that looks odd to TTCom. Each issue found will consist of the ttcom.conf line number followed by a description of the anomaly. The number of lines in the file will also be reported; this is primarily aimed at helping detect line ending problems caused by porting configuration files between operating systems.

The lint command is not guaranteed to catch all possible problems but will catch the following:

• A missing or unreadable configuration file.
• Unrecognized line formats that are neither a valid section header nor a valid line within a section.
• Unrecognized section names.
• Attempts to use spaces inside a server shortname.
• Unrecognized server parameter names within a server section.

For the curious, the name "lint" is chosen because Lint was a C program checker that reported errors and warnings about C program syntax many years ago, and the term is still in common use in programming circles for anything that helps verify the correctness of code or file syntax.

Known Issues

The following issues are known and may be fixed in a future version of TTCom:

Revision History

This is the revision history of TTCom, most recent revision first:

Revision 1119, October 26, 2020

• Added the lint command for diagnosing various problems with the TTCom configuration file.
• There is a new url command for generating a TT URL for people to click in order to join the current server. The URL approach will work in many cases but will fail for some due to problems with characters in passwords and possibly other fields. See also the tt command for creating a .tt file that will launch TeamTalk into a particular server. Both commands also support automatic joining of a channel on connection if desired.
• Status changes that print elapsed times now indicate when the shown time only represents time since TTCom login instead of time a client spent in a particular status. This applies to the output of the WhoIs command and to status change events that print asynchronously.
• The TTCom application and this document now use the version control revision number in place of an arbitrary version number. As the generation of this number is automatic, this much more reliably maps the reported TTCom version to the exact code that is running.

Revision 1108, September 07, 2020 (version 3.1.0)

• The structure of files and the website area for this project are reorganized to match the normal structure for this author's projects, for ease of future maintenance and updating:
  • The small README.txt file, these release notes, and various other notes are combined and transformed into a more comprehensive user guide, which itself becomes the main website page for TTCom.
  • The download link for TTCom is found within this guide.
  • From time to time, an advanced beta of TTCom and its documentation may be available from https://www.dlee.org/updates/ttcom.zip and https://www.dlee.org/updates/ttcom.htm, respectively. When present, these two URLs should retrieve files that are either identical to or newer than their corresponding officially released counterparts. This author makes no promises as to the availability, stability, or announcement of such beta versions of any project, however.
• Logins and logouts without a nickname are reported. Historically these were ignored because of "scanners" that, for example, produced public HTML pages listing available public TeamTalk servers along with current connections by logging quickly and often into and out of numerous servers at once to maintain current information.
• Fixed a failure to log out and disconnect from a server on a refresh command when the server has been deleted from the TTCom configuration file.
• Fixed the failure of the login command to log into a disconnected server that uses encryption. Startup-time login already worked, but manual login without an existing connection did not.
• Typing a command prefix that has multiple command matches does not reprompt for a selection if the user presses Enter once without making a choice.
• Some commands that concluded their output with an extra blank line and/or extra spaces at the ends of lines no longer do so.
• Various cross-project code updates.
• Documented in the sample configuration file that spaces should not be included in server shortnames.
• Per a discovered TeamTalk API doc of unknown date, the first word in a TeamTalk server's first line on connect, which the doc called the system id, is no longer required to be "teamtalk" and is reported on connect if different.

Revision 1021, August 24, 2019 (version 3.0.3)

• Fixed a few possible error exceptions caused by deleting a server while TTCom considers it "current" for event output.
• On MacOS, event speech output (when enabled) is sent directly to the OS rather than first being made into a wav file to then play. This indirection was necessary in much older versions of MacOS to avoid missed speech in some cases.

Revision 1010, August 12, 2019 (version 3.0.2)

• Fixed an exception that occurred on a server disconnect.
• Fixed ability to run TTCom with no Options section in ttcom.conf.
• Fixed a ResourceWarning that could occur on server connect on Windows but apparently not on MacOS. (It may also have been fixed between Python 3.7.3 and 3.7.4.)
• Removed some obsolete code for TeamTalk 4 servers.

Revision 1005, August 8, 2019 (version 3.0.1)

• Resurrected the feature that allows speech rate specification on MacOS for event output. The environment variable to use is now SAYPREFIX, though, rather than TTCOM_SAYPREFIX. This feature was accidentally lost during the conversion to Python 3.
• Eliminated an import warning caused by using the old imp library instead of the newer importlib alternative. This change will only be noticed by users who run TTCom from source.
• Idle times on status update events no longer print when they amount to 00:00:00. This primarily affects the output produced by clients that log in with a pre-existing Away status.

Revision 1000, August 5, 2019 (version 3.0.0)

This is the first public TTCom release targeted at, and requiring, Python 3.7 rather than Python 2.7. The Windows stand-alone .exe will work as before, but running TTCom from source, on any operating system, will now require a Python 3.7 installation that launches with the "python3" (not just "python") command. This approach avoids problems on systems (such as MacOS) where the "python" command must for now continue to launch Python 2.x in order to avoid many other problems.

This release is also the first to support professional encrypted (SSL) TeamTalk servers. For these, add the line encrypted=true to the server's configuration section in ttcom.conf. Note that encryption, or SSL support, is not related to the new TeamTalk 5.4 web login system used by the public TeamTalk servers. The web login system is not at this time supported by TTCom.

Important: Install this TTCom into a fresh folder, not over the top of TTCom 2.x, to avoid stray and possibly problematic residual files from the older version. In particular, .pyc files produced by an older TTCom could confuse the new version, as Python 3 handles .pyc files differently.

Other enhancements in this release:

• The tt command can make a proper .tt file for an encrypted server.
• Attempting to replace an existing .tt file prompts for confirmation of permission rather than issueing a NameError.
• Several fixes to the WhoIs command:
  • More accurate "can share" rather than "sharing" indicators for users who are granted special permission to share video, media, desktop, etc. in specific channels. *(Media file sharing permission was previously omitted accidentally and is now included as well.)
  • Users who are voiced explicitly in a channel show as "Can speak."
  • Users whose current userid happens to be a substring match of a userid that is granted one of the above channel-specific permissions is no longer reported as having that permission erroneously. Example: If userid 2045 has voice permission in channel /Library/, userid 5 will no longer show as "Can speak" in that channel just because "5" is part of "2045."
• The list of public servers previously shown in ttcom_default.conf is removed for the following reasons:
  • The list of public servers is dynamic, so a list in a TTCom file will continuously go out of date.
  • Public servers have begun requiring the web login system that debuted in TeamTalk 5.4; and TTCom does not currently support this login system.
  • There is little good reason to use TTCom on a public TeamTalk server in the TTCom author's considered opinion.
  One entry remains in ttcom_default.conf as an example server entry, however.

Revision 969, May 28, 2019 (version 2.1.0)

• Python 2.7 is the oldest Python version supported.
• TTCom may now auto-join a channel when logging into a server. To arrange for this, indicate the channel in the server's configuration file section. There are two supported syntaxes, shown here by example:

  chanid=4

  makes TTCom join the channel with chanid 4 on login. Use channel list to find channel ids. This method has the advantage of working even if a channel or one of its parent shannels is renamed. Alternatively,

  channel=/My Space/the Library/

  joins the channel with the given exact path. Letter casing in a channel path must match exactly, and the path must both begin and end with a slash. These rules also apply to other TeamTalk clients. Note that the root channel always has the id 1 and the path of just one slash character. If the channel requires a password, include another configuration line to specify it:

  chanpassword=blah!blah!

• Channel lists (see the channel list command) now sort case insensitively by channel path, much like the TeamTalk channel trees.
• There is a CKick command for kicking a user from current or specified channel, syntax similar to that of CMsg.
• The refresh command deletes servers from the running list when they have been removed from the config file.
• allSum and shortSum results end with a total server count then broken down by connection state.
• ban list now uses a three-row format and includes ban type as text (IP address or Username). The other two lines are nickname and channel at ban time.
• The addresses command is now just address.
• whoIs reports IPV6 addresses correctly as does the address command.
• Support for TeamTalk 4 UDP addresses and TCP and UDP ports is removed. This affects code for events and for the whoIs and address commands.
• The environment variable TTCOM_SAYPREFIX works on MacOS as a place to put Mac-specific voice parameters to apply to all event and trigger announcements. This feature is included to help those who wish to hear events on a Mac at a personally chosen speech rate, pitch, etc. This feature is experimental and may change or vanish without notice, especially since it is Mac-specific and relies on MacOS features that may themselves disappear. Example usage: In Bash or a compatible shell or one of its initialization / startup files, add this line to increase the TTCom voice speed:

  export TTCOM_SAYPREFIX="[[rate 450]]"

  Of course, a TCP port may still be specified for a server in the configuration file.
• TTCom is beginning to try to honor user locale settings.

Revision 930, November 23, 2018 (version 2.0.5)

• Incoming user messages from invisible userids work without exception traces. This can occur on a server where TTCom is not allowed to see into channels but yet receives a message.
• UMsg can send to a userid directly via a number sign; e.g., umsg #232 I got that!. This was documented but did not work as expected. This allows replying to messages such as described in the previous item.
• The UMsg command for sending user messages has a new -i option for sending a more private user message to another compatible text client. These messages have the following properties as compared to normal TeamTalk user messages:
  • They are not recorded in server log files according to tests run on TeamTalk 5.3.3 servers at least. (TeamTalk server logs normally record all channel and user text messages and broadcasts.)
  • They do not appear to be interceptable by TeamTalk administrators.
  • They are ignored by regular TeamTalk clients, which means they are only useful when sent among compatible text clients.
  • They are an irregular use of the TeamTalk TCP protocol. They should therefore be considered experimental in nature, and their behavior subject to change without notice, such as in the event of a new TeamTalk server version handling them differently.
  See the help text for the UMsg command for more information on this option. Note that nothing in TeamTalk should be considered "private" (partly because nothing is encrypted) and that neither the TTCom author nor the TeamTalk author can guarantee privacy of these new messages or that they will be handled as expected by different client and server versions.

Revision 915, October 3, 2018 (version 2.0.4)

• On startup, the "current server" (the one to which commands apply by default) is now the first server defined in the configuration file, rather than a seemingly random server.
• Attempts to use TTCom without creating a configuration file (ttcom.conf) or without defining servers in it now print more sensible error messages.
• A warning is printed on startup and after a refresh command if no server definitions can be found.
• The vlist command now formats and sorts its output more intuitively.
• Status change events print the length of time the previous status was in effect; for example, when a user switches from Away to Online after being away for 10 minutes, "00:10:00" is included with the event. In addition, the WhoIs command includes the length of time the current user's status has been in effect. Note though that these durations reset when TTCom itself logs in and thus will not always reflect actual status lifetimes.
• A stray comma is removed from WhoIs output.
• WhoIs includes the domain address for an IP address that is given as the IPV6 version of an IPV4 address; e.g., "::ffff:192.168.15.124."
• Fixed the naming of subscription bits, so that user subscription changes report correctly.
• Fixed the handling of channel name changes so that TTCom uses the new name rather than the old one thereafter.
• On a server that hides channel participants from this user, the status update events sent for admins no longer attempt to print anything. The information previously printed tended to be both unhelpful and confusing.
• Fixed a long-standing bug that caused an exception to print on a refresh command if a server's autoLogin value changed from 0 to 1 without other changes for that server.
• A change in login parameters without changes in host or port no longer cause a disconnect and reconnect, but just a logout and login.
• Runtime errors encountered during the processing of a server event now include Python tracebacks to help with debugging.

Revision 873, June 12, 2018 (version 2.0.3)

Note: The syntax of the cmsg command is changed in this update.

• The channel-message command, cmsg, operates by default on the currently joined channel. The following sequence will thus message the root channel:

  join /
cmsg Hello!

  A specific channel may be specified with an at sign; e.g., cmsg @blah Hello to blah channel members. If TTCom is not in a channel, a channel must of course be specified in this way.
• The abbreviation of Facebook ids applied in the previous update (see next section) also apply to event output now, such as on logins and status updates.
• Some updates, channel updates in particular, report changes more reliably. This includes reporting of voiceusers list changes as channel participants are voiced and unvoiced by an admin.
• There should be fewer UnicodeDecodeError issues, such as when listing and filtering lists of channels (the channel list command).
• Fixed rare instances where output such as from whoIs could include a line beginning with a comma.

Revision 858, May 27, 2018 (version 2.0.2)

• Facebook account ids just print as "facebook" instead of as the full long id for the following commands: summary, shortSummary, allSummary, VList. This is for speech users, for whom the long ids are distracting and time-consuming to read. Full ids are still printed for the WhoIs command. This feature only applies when both server and client versions are 5.3 or later, which means when Facebook ids are actually Facebook logins.
• During login to a server with file uploads in channels, events are no longer printed for each file.
• TTCom now requires Python 2.7 and will not work with older Python versions.

Revision 852, February 11, 2018 (version 2.0.1)

• New channel command. So far, the only implemented subcommand is list, which can list channels with varying detail and can filter the set of channels listed by many means. Warning though: There are still problems with this command on servers with non-ASCII characters in channel names.
• Commands that operate on channels, such as cmsg, allow channel matching by specific TeamTalk parameter. One use of this is to message a channel by its id:

  cmsg chanid=5 Hello

• Various updates to the account command:
  • Fixed a bug that caused user rights on an account add command to be set to 0 when the user type was given as a number (1 or 2). The following command will list any accounts on a server affected by this bug:

    acc li userrights=0

    and the following command will set rights for account Doug to the default values:

    acc mod Doug userrights=259591

  • Passwords do not print unless a -p argument is specified.
  • Added a Rights column to the Account List table. Currently rights are shown as an integer.
  • Corrections to example account delete usage help text.
  • When not blank, the Notes for an account are shown in an Accounts table below the line for the other fields for the account.
  • -e prints all fields except passwords (use -p to add passwords), even when blank. This is useful for determining what fields are allowed for an account.
  • For long account listings (-l and -e), fields are sorted by name except for Note, which is always last.
• Fixed a long-standing bug that broke some commands when issued on a "server ..." or ">..." line that made the command address a specific server. The issue was the introduction of extra spaces in some cases, such as (or at least) around equal signs.
• The default name for this client when connecting to servers is now "TTCom User."
• ttcom_defaults.conf better documents the format and capabilities of TTCom .conf files.
• For users of the python or ! commands, the name of the TTCom root object is now app rather than ttcom, for consistency with other projects.

Revision 819, August 8, 2017 (version 2.0)

Please read this entire section of release notes before upgrading.

This revision includes many fixes, a few new commands and features, and some changes in syntax for existing commands.

This revision also marks the official end of TeamTalk 4 support. This does not mean that TTCom will instantly stop working with TeamTalk 4 servers; it simply means that support for those servers will begin to fail as reasons arise to remove or modify the code that supports them.

New and changed commands and features:

• New Windows stand-alone executable, so you need not install Python.
• Changed the syntaxes of the following commands to add power, flexibility, and perhaps comprehensibility:
  • account.
  • ban.
  • kb.
  Read the help for each of these by typing help or ? followed by the command name. Each of these commands now has subcommands, for which help is also available.
• account add now does the following sanity checks:
  • Aborts on a duplicate existing, case significant.
  • Warns specifically if an account differing only in case exists.
  • Warns if an account exists differing only by case and/or spacing and/or punctuation.
  Warnings allow the user to abort the account creation. These checks are meant to help avoid some very common administrative accidents.
• New motd command for displaying the current server's message of the day.
• The version command is now about.
• version without arguments gives the currently selected server's TeamTalk version, and with arguments gives a client's version and client name.
• Selection lists now allow all and negation via an exclamation mark (!) if multiple selections are allowed. Type help selection or ?selection for complete help on handling selection lists.
• -p option added to the vlist command for filtering by packet protocol or voice capability.
• Login and logout events that print in the TTCom window include admin for admin users and user for other users.

Fixes:

• A missing [server defaults] section no longer causes a launch-time crash.
• Deleting a file from a channel with a regular TeamTalk client no longer causes an event dispatch failure error message to print in the TTCom window. This functionality may not work on TeamTalk 4 servers.
• Fixed op, intercept, and subscribe commands to work on TeamTalk 5 servers. (The no-audio restriction remains, however, as there is still no support for audio in TTCom.)
• The summary command no longer combines multiple instances of the same user in a channel into a single entry.
• Various output formatting improvements, including better handling of unicode.
• Time reporting should work correctly for local time zones under Cygwin where it may not have before.
• The nick command is now nickname, which lets nick continue working while also letting nickname work.
• Fixed various problems with matching channel names in the join command. Channel matching now works thus:
  • Channelname and/or password can contain spaces if quoted.
  • Channel / always refers to the root channel.
  • A channel starting and ending with / must match exactly except for letter casing.
  • A channel containing a / is matched against all full channel names (path included).
  • Otherwise, the channel is matched against only the actual channel names, without paths.
  Note that this command will no longer create temporary channels as it once did under TeamTalk 4.
• The Server command should properly honor any quoting on an included command.
• The rights assigned to an admin account are now consistent with TeamTalk defaults (as of TeamTalk 5.2.1.4781). This matters when an admin account is later reverted to a normal account.
• If TTCom is kicked off of a server for which autoLogin=1, the TTCom user may restart the auto-login behavior by logging in again manually.
• Some error messages are improved for clarity to end users who are not also Python coders.

Revision 692, August 13, 2016 (version 1.4)

• The tt command allows a target TeamTalk client version number, such as 5.1, to be specified before the name of the .tt file to create. This makes it possible to generate a tt file for a client whose version number differs from that of the current TeamTalk server.
• There is a new vlist command that summarizes users on the current server sorted by increasing version number and then by client name.
• Quote characters should work in messages sent to users or channels from TTCom.
• The say command on MacOS may work across more non-ASCII character situations.
• Temporary files for say commands are created more securely.
• When logging into a server, TTCom will print a warning for each or both of these conditions if true:
  • The server disallows multiple simultaneous logins from the same account, and/or
  • The server does not allow this user to see who is in any channel until the user joins the channel.
  The same information prints for a WhoIs command with no arguments (i.e., a request for information on this current TTCom user login).
• TTCom itself now uses its actual version number as its version value for display by other clients, and the name "TTCom" for its clientname where supported.
• The speakEvents option is supported: Setting it makes TTCom try to speak all events that print in the TTCom window through the active screen reader. This currently requires SayTools to be installed on Windows but works natively on MacOS. To turn this feature on, type opt speakEvents 1. Use 0 instead of 1 to turn the feature off. The state of this option is saved across TTCom restarts.

Revision 652, November 21, 2015 (version 1.2)

This revision fixes more issues with TeamTalk 5 servers and adds a few enhancements:

• A new version command reports the running TTCom version and other information.
• Joining the root channel (/) works as expected.
• The tt file should generate TT files compatible with the TeamTalk server version for which the file is being generated.
• TTCom will keep up with channel renaming on a TeamTalk 5 server without requiring a TTCom restart.
• Deleting bans with ban -d works.
• The account command works on TeamTalk 5 and supports copying user rights from a chosen source account when creating a new one. To use this feature, specify an account name (or something that matches an account name) in place of the 1 or 2 normally given as a user type. To use the anonymous account as the source account for user rights, specify "" in place of the user type. The user type will become 1 and the user rights for the new account will duplicate those assigned to the source account indicated.
• The anonymous account is more properly supported in other account scenarios; for example, acc "" reports the information for the anonymous account instead of displaying a list of all accounts.
• It is no longer necessary to add udpport=0 to every ttcom.conf entry for TeamTalk 5 servers. TTCom no longer transmits a UDP handshake at all. (This was implemented to avoid short Windows XP client freezes on TeamTalk 4 servers, but Windows XP has long been deprecated by Microsoft.)
• The statsAdmin command is now changed simply to stats, and the old stats command is gone. Reasons for this include
  1. The old command never worked on TeamTalk 5 servers because TeamTalk 5 does not support / commands sent to a channel..
  2. Attempting to use the old command on a TeamTalk 5 server would run the risk of sending the string /stats visibly into the root channel even if the sending console was not there, which could startle and confuse users.
  3. The old command stopped working for non-admin users on TeamTalk 4 servers at some point.

Revision 607, December 20, 2014 (version 1.1)

This release primarily fixes a number of issues TTCom initially had with TeamTalk 5 servers, caused by changes in the text TeamTalk client/server protocol:

• Events no longer generate errors.
• Channel membership is reported correctly in summaries.
• WhoIs works when TTCom is not logged in as an admin.
• Move, join, leave, cmsg, and several other commands work as well.

The following commands still do not work completely on TeamTalk 5 servers:

Account

List may omit fields, and add/modify will not work.

Intercept and Subscribe

Bits are wrong.

Op

Not tested but not updated command formats.

TT

Not able to write updated file format.

Other changes in this release:

• The default version string is now "TTCom" instead of "4.2.0.1479."
• The say command usable in triggers, when used on MacOS, now uses the afplay command and a temporary file instead of piping directly through say in order to avoid the speech breakup that occurs often (at least on SnowLeopard) when the `say' command is used. This change causes a Python warning against use of tempnam() on the first say command call.

Revision 580, September 7, 2014 (version 1.0)

This is the initial public release of TTCom and the start of its falling under the GNU Public License (GPL). To learn of TTCom's use through the date of publication, see "All About the TeamTalk Commander." To learn its history prior to publication in more detail, read "TeamTalk Commander (TTCom) Pre-Publication History."

I am publishing TTCom for the following reasons, approximately in this order:

• A predicted reduced need for TeamTalk security assistance on the release of TeamTalk 5, which by all appearances will require special steps to allow accountless logins whereas TeamTalk 4 allows this by default.
• A personal tendency to prefer sharing over hiding of my code.
• A dislike for favoritism and the fact that my having given two people code while withholding it elsewhere would naturally give that appearance, despite the reasons for my having done this.
• Possible appeasement of some who wish to see the code for purposes of inspection.
• Removal from me of the burdens of both responsibility and technical resources for managing the connections and data.
• A means to allow TeamTalk users, server owners, and server admins to work out among themselves, without my constant input, the questions of when, where, and whether to run non-standard and/or constantly-connected TeamTalk clients.