Thanks to Markus from TeaSpeak for being able to Google the header (magic number) High number of layer 8 problems ()Īs you can clearly read above, YaTQA 3.9.8.2 explicitly works with 3.9.x only. After that, copy the target server’s keypair into the source server’s snapshot and deploy it. Then apply the steps above to this snapshot and the source snapshot (if non-pseudo 3.10.0+ snapshot). If you want to use YaTQA to overwrite a 3.10.0+ server with a snapshot while maintaining the target server’s identity, please create a snapshot of the target server.Use the latter and then decompress using Zstd. If you do want a server that is created from a manipulated snapshot to have the identity of the source server or if you want to manipulate an existing 3.10.0+ snapshot, please download Facebook Zstd (that’s the name of the new snapshot format) and some Base64 decoder.Starting with 3.9.8.3-alpha, YaTQA accepts user-manipulated pseudo snapshots. If you do not care about the deployed server having a different identity (will display a warning for people who have the old identity bookmarked), just use pseudo snapshots.If you want to manipulate snapshots, here’s how: Please note that YaTQA v3.9.8.3-alpha snapshot manipulation tools do not work with 3.10.0+ snapshots or if overwriting a 3.10.0+ server while keeping its keypair. You now have to solve the puzzle on the Support page, which has the only valid email adress (which wasn’t changed). Therefore, I disabled catch-all for this domain. I’m starting to get spammed with email bounces arriving at random yat.qa adresses, even though my SPF records clearly says they’re not from me and must be dropped: Received-SPF: Fail (: domain of yat.qa does notĭesignate 51.211.200.160 as permitted sender) I plan to work on 3.12.0 and TeaSpeak support (3.9.8.4) over the weekend. This is a maintenance update, primarily for increasing the time limit by 1 year (first time ever). TeaSpeak 1.4.10-beta is required, but hasn’t yet been released to the public at the time of writing.ģ.9.8.4 will include TeamSpeak 3.12.0 compatibility and is set for release withing the next days. It includes a small general bugfix and a lot of compatibility fixes for TeaSpeak. No apikey support yet (except for the permissions), though. At least there were some maintenance updates and some cosmetic fixes. Nothing else, but it’s been almost 9 months with no new server and over 14 months (beta over 15 months for stable) with no new client release anyway. I’m still alive! (You know, I had to do what I must because I can.) The update will bring API key management. There is not other change than the removal of the time limit. This is also because TeamSpeak obviously ceased development on the TeamSpeak 3 Server, so there’s nothing to do. But as “releasing on time” seems to be an issue for me, I now released YaTQA without a time limit. In my previous post, I said that I had to do what I must because I can. Note: The English and the German blog both have a few posts that are not available in both languages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |