Административные YaTQA / Yet another TeamSpeak 3 Query App 3.9.9b

Спойлер: 3.7-rc2b (31 Dec 2016, official release)

Despite being a release candidate, this is an official update. The time limit in 3.5 did not properly run out on August 31th, 2016, so these people must download a new version by January 1st, 2017. I want those people to upgrade to the 3.7 series because of the new IPv6-enabled DNS resolver and all the bug fixes that are included. I want to do some more DNS improvements for 3.7-final, though.

• Added an option to ignore all errors in chained operations
• Add client icon
• Add channel icon
• Fixed version selection in DNS resolver not being updated in English version
• Decided to make 1481641346 iOS visible in version selection, though I’m not sure if it’s only an internal release

• Fixed position of the new script checkbox (affected Pro users with non-default window size only)

Спойлер: 3.7-rc2 (18 Dec 2016, unofficial release)

• Fixed brief flashing of other info pane when opening the users tab
• Changed all comboboxes to a dropdown count of 15, a number that is already used universally in the permission tab for example
• Changed name of version 3.1-beta5 to 3.1-beta4r2 to match the internal numbering TeamSpeak uses (this has always been marked as only a hotfix in YaTQA, though)
• Above change for DNS resolver
• Possibly fixed a rare bug that sometimes caused an access violation when doubleclicking a server in the client cache’s server list
• Added a hint that you can find information on times with delayed key creation on the website
• Prevented -c from changing your quick connect server
• Fixed incorrect official syntax of channeldelete (YaTQA Pro)
• Fixed a bug that displayed an error after using the “What’s this value?” feature for a parameter-style string (YaTQA Pro)
• Added support for myTeamSpeak badges (RedeemerTS3 only)
• Fixed a bug that prevented the top bar and caption from updating if serverinfo failed but whoami worked
• Server groups in Users and User Details tab are now sorted by sort ID.
• Added option to replace all channels when importing a channel file
• The quickstart guide that ships with the server implies that serverstart should be synchronous, so we can use a server right after starting it. I haven’t seen a server not being marked online when the list refreshed after starting it.
• Fixed a bug that prevented users from selecting groups in many places, e.g. the instance (instance statistics) and server settings (advanced tab)
• Fixed a bug in the DNS resolver that displayed SRVs resolving directly into IPs as a fail for versions that would actually connect and displayed a warning for versions that wouldn’t
• Changed links to TS3Index and the IP locating service to HTTPS
  • Note: yat.qa does not use HTTPS because without HTTP Firefox’ location bar just says “yat.qa” which looks cooler to me.
  • Note: Services accessed using YaTQA (update checker, Planet TeamSpeak API) do not use HTTPS because I want people to be able to verify what is being sent to my servers. I think that’s important for software that asks for potentially valuable credentials. Also, implementing HTTPS would require me to ship ssleay32.dll/libeay32.dll with the product.
• Added displaying of the channel group icon
• Added displaying of the server group icons
• Added displaying of badges
• Fixed “shared IP” feature being disabled when all users were loaded
• Bade the instance stats tab’s “license” button’s hint clearly state that it’s about the TeamSpeak server rather than YaTQA
• Fixed a bug that caused recalculating the snapshot hash of snapshots with hashes containing slashes to fail (not enough text removed before hashing)
• Fixed a bug that caused recalculating the snapshot hash of snapshots that would include slashes to fail (missing escaping)
• Fixed a bug that caused adding people to server groups to be executed at least twice if the user pressed Enter for this action and the combobox control was in dropdown style
• Fixed a bug that caused adding people to server groups to be executed repeatedly if the user pressed Enter for this action and confirmed a resulting error message with Enter while the combobox control was in simple/list style (in this style, you can only add a user again if you changed the input, which makes sense anyway)
• If you have the server icon cached, it is now displayed as the image of the “join” button (it is loaded as soon as you enter either of the two first virtualserver tabs which usually is instant, but for some features that change servers the previous TeamSpeak icon is displayed instead)
• Added a feature to set all permissions currently displayed (Permissions tab)
• The filter warning message displayed by that feature (and the “cluster” variant it derives from) is now displayed for the “delete displayed permissions” feature as well, which has consequently been renamed into “delete all permissions”.
• Add a feature to set all ‘power’ permissions
• Add a feature to set all existing (already set) ‘power’ permissions
• Add a feature to delete all ‘power’ permissions
• Moved some features in the permission tab’s context menu
• Update hinting for outdated server versions from 3.0.13.5/1475595457 to 3.0.13.6/1478594913 (beta=final)
• Updated client versions to choose from (not quire sure if iOS 1481641346 as well as Android 1474882482 and 1477071110 are public, but I don’t think so and chose to hide them from the list)
• Changed plain TSDNS lookups to show up as warnings on more recent server versions

Спойлер: 3.7-rc1 (19 Oct 2016, unofficial release)

• ––– English development snapshot updated here, see below for download –––
• Fixed two buttons being default (blue border, so they are activated when pressing enter) in login tab when connected
• Fixed server group member controls not being aligned right in permissions tab
• If the window is wide enough, the server group window list now spans the full height. I tried to make this available to non-Pro users, but there is no event that notifies me if the list is small enough.
  • Please note that a workaround is used to add a user when pressing the Enter key, because in simple list mode, this event isn’t fired, at least on Windows 7. If this event is however fired on other versions (1282, database duplicate entry), please report this error!
  • Please als note that this list does not support multiselect. This is a limitation in Windows and cannot be changed.
• Fixed last “Did you know?” message (regarding IPv6) not showing for registered users
• Added a feature to show only users with non-unique IPs in User DB
  • Note: You must have these users downloaded.
  • It can be combined with the ban mode.
• Added a word (“downloaded”) to the label that displays the number of downloaded User DB records to make sure people understand what it is and why it doesn't go away in neither the groups, ban nor unique IP mode
• Added “All Channels” button to the selection window
• Improved the DNS lookup simulation’s version selection a lot
  • Note: YaTQA can now simulate all the lookups of every TeamSpeak version from today’s 3.1-beta5 back to the earliest 3.0.0-betas.
  • Note: These versions behave in 10 different ways which is how you select them:
    1. 3.0.0-beta37: Simple DNS (A, CNAME) only and no IDN support.
    2. 3.0.0-rc1: Added TSDNS (which I think did support IDN for the TSDNS queries itself (UTF-8) back then, therefore essentially only working on subdomains of the domain running the TSDNS server).
    3. 3.0.0-rc2 – 3.0.7: Added Punycode support to IDN A lookups.
    4. 3.0.8 – 3.0.16: Added SRV (using an algorithm for IDN that is simply bullshit).
    5. 3.0.17 – 3.0.19.4: Properly converting uppercase characters to lowercase (now works for non-ASCII).
    6. 3.0.20: Completely broke any IDN support for non-TSDNS queries. Added TSDNS tail (0x0A0D0D0D0A), so the server can serve IPv6 results as well as multiple results for redundancy (which is both not supported until 3.1-beta1 it seems). Removed plain (non-SRV) TSDNS. Always looking up only the second-level domain for SRV TSDNS (if there is no second level, there is no SRV TSDNS). IPs are now considered invalid SRV targets. Domains are now considered an invalid TSDNS result. BTW: hosts no longer works.
    7. 3.1-beta1: Added AAAA support.
    8. 3.1-beta2: SRV TSDNS now uses Mozilla’s Public Suffix List for determining what domain to use for the SRV TSDNS lookup. Stuff that’s a public suffix is no longer queried for anything but standard lookups. SRV lookups are not done if connecting to a public suffix (or other top-level name).
    9. 3.1-beta3: Plain TSDNS re-added. Domains used for new plain TSDNS include the domain used for SRV TSDNS as well as up to one subdomain of that domain. TSDNS is now completely case-sensitive. IDN working for A again and working for SRV for the first time. BTW: IPs are still invalid SRV targets.
    10. 3.1-beta4 – 3.1-beta5: TSDNS is now completely case-insensitive again.
• Added support for new 3.1-beta DNS resolving log format to server history (the feature did work, but did not display the original input)
• Fixed a bug that stopped adding more servers from a log file to the history list if a was a duplicate of one that was already in the list
• Improved displaying of IPv6 addresses in server history
  • Note: TeamSpeak 3.0.20 used a format here that is a bit ambigious. Because very few people used this version and it was quickly deprecated because of an important hotfix from the 3.0.19 series, I chose not to make special adjustments just for this version.
• Fixed IDN not displaying correctly in server history
• Adjusted duplicate server history entry detection to work with 3.1-beta
  • Note: This is and has always been case-insenstive, even if all client versions until 3.0.16 are case-sensitive in terms of IDN (which was a bug) and 3.1b3 is case-sensitive in terms of TSDNS (which is likely a bug again).
• Fixed connecting to IDNs in server history
• Add support for importing exported YaTQA group overviews to permission file editor
  • Note: It supports both, Channel and Server. They are individual features just to start you off with the appropriate directory.
• Added support for importing exported YaTQA group overviews and TeamSpeak permission overviews to permission comparison
• Added support for importing channel files with included permissions to permission file editor and permission comparison
• In the client cache explorer, fixed incorrect display of client log lines and server history entries in old versions of TeamSpeak
  • Note: As most of the stuff in the log is in English, IDNs are the likeliest case of that bug occuring.
• Fixed “Unused” icons feature causing an access violation when an icon was not found instead of displaying a list of missing icons when done with checking like it was intended
• Added support for 3.1-beta3 to DNS resolver.
• Fixed failed standard queries sometimes being displayed four times, with the fourth always being called an empty result for no reason...
• Clicking the “Register” button with no key entered will now unregister YaTQA. This change is meant for people who temporarily use a demo key. A demo key allI>ows you to use the Pro features, but with less servers than the freeware version.
• Fixed IDN support when using IPv6 with the lowest level domain being an IDN
• Prevented serveradmin from uploading an avatar (regression fix)
• serveradmin is no longer considered a Global ID by the offline message composer. Although basically a regression fix, this feature wasn’t even offered back when the server software allowed offline messages for serveradmin years ago.
• Added support for IPv6 nameservers
• Added support for non-default nameserver ports
• Added support for copying and connecting to IPv6s from the resolver
• Implemented the fact that TeamSpeak doesn’t support domains returned from TSDNS (v3.0.20+) and added a warning for older versions (clients that do not support this anymore report “TSDNS server at x doesn’t know y”, which is incorrect)
• Added support for IPv6 returned by TSDNS
• ––– German development snapshot updated here, see below for download –––
• Added support for TSDNS v3.0.13+ results supporting redudancy
• TSDNS NORESPONSE now results in a line saying empty result instead of an actually empty result and is now considered a failed lookup.
• Fixed joining IPv6 servers with the official client when connected via DNS
• Added displaying the elapsed time for failed standard DNS lookups (as total time and number of lookups)
• You can now export the channel -mapping to shell and batch scripts that rename your files after restoring a snapshot (can be enabled using the checkbox above the links).
  • Note: These files appear in the “File Folder Rename Scripts” subfolder of YaTQA’s configuration directory. There is a button in this tab to open that folder.
  • Note: The filenames are: {address}_port-{new port}_sid-{new SID}_{virtual server name}, with the .bat and .sh extensions added respectively. The files use the OS-specific EOL characters. Further notes:
    • Address: IDN addresses are in Punycode, IPv6 addresses have their brackets stripped, numeric IPv6 addresses have their colons replaced by hyphens and their link-locals stripped.
    • Virtual server name: Characters not allowed in 8.3 (include .) are replaced by hyphens. Unlike 8.3, YaTQA allows lowercase letters and has no length restriction.
  • Note: This feature is included in the Freeware version and will make the backup feature in YaTQA Pro obsolete for many users.
• Added duplicating bookmarks
• Added support for DNS lookup patterns in 3.1-beta4 (and beta5, which is identical I think) and mobile betas. Many thanks to ts3index.com for their continued support.
• Added new versions for selection: 3.1-beta3/4/5
• Updated hinting for outdated server versions from 3.0.13.3/1471538803 to 3.0.13.5/1475595457 (note: this was actually a beta released when YaTQA was released and I think the actual final 3.0.13.5 release had a different number)
• Did some small adjustments to a very few texts
• Fixed a bug that caused ampersands to fail to be displayed correctly in the status bar
• Fixed a bug that sometimes caused YaTQA to look like it was hanging when it wasn’t
  • Note: This might make YaTQA look like you could continue using it, but although YaTQA is mostly thread-safe, the query interface is not, because the use command makes the connection context-dependent! To prevent users from trying this, I made the application react only once every 5 seconds when doing something else.