if it's up to me, I'll keep helping, whether with $ or anything else!.Hello,
I'm sorry for postponing the project for the last couple of months (may be some more )!
I personally didn't wanted to admit, that I don't have time nor motivation to work on TeaSpeak.
By now it has been over half a year without any progress and I don't want to let this software die like some other.
For this reason (as I promised from the beginning) I took the time
and made TeaSpeak fully open source. This includes the server and client source code including their dependencies.
You can now browse, edit and even compile your own version of TeaSpeak!
URL: https://git.did.science/TeaSpeak
The source code is available under GNU GPLv3.
Note:
I'm expecting a strong decrease of license sales, but I'm hoping that it will not average bellow the maintaining costs of all TeaSpeak services.
If so I may have to consider on downsizing them
PS:
I'll post an official statement the following days.
I really hope, someone finds the patios and time to continue TeaSpeak with me
PPS:
If there are any interested folks out there in further developing the project,
just reach out to me via E-Mail to [email protected]!
Best regards
Markus ~ WolverinDEV
Hi Markus,Hello,
I'm sorry for postponing the project for the last couple of months (may be some more )!
I personally didn't wanted to admit, that I don't have time nor motivation to work on TeaSpeak.
By now it has been over half a year without any progress and I don't want to let this software die like some other.
For this reason (as I promised from the beginning) I took the time
and made TeaSpeak fully open source. This includes the server and client source code including their dependencies.
You can now browse, edit and even compile your own version of TeaSpeak!
URL: https://git.did.science/TeaSpeak
The source code is available under GNU GPLv3.
Note:
I'm expecting a strong decrease of license sales, but I'm hoping that it will not average bellow the maintaining costs of all TeaSpeak services.
If so I may have to consider on downsizing them
PS:
I'll post an official statement the following days.
I really hope, someone finds the patios and time to continue TeaSpeak with me
PPS:
If there are any interested folks out there in further developing the project,
just reach out to me via E-Mail to [email protected]!
Best regards
Markus ~ WolverinDEV
Hello,
I'm sorry for postponing the project for the last couple of months (may be some more )!
I personally didn't wanted to admit, that I don't have time nor motivation to work on TeaSpeak.
By now it has been over half a year without any progress and I don't want to let this software die like some other.
For this reason (as I promised from the beginning) I took the time
and made TeaSpeak fully open source. This includes the server and client source code including their dependencies.
You can now browse, edit and even compile your own version of TeaSpeak!
URL: https://git.did.science/TeaSpeak
The source code is available under GNU GPLv3.
Note:
I'm expecting a strong decrease of license sales, but I'm hoping that it will not average bellow the maintaining costs of all TeaSpeak services.
If so I may have to consider on downsizing them
PS:
I'll post an official statement the following days.
I really hope, someone finds the patios and time to continue TeaSpeak with me
PPS:
If there are any interested folks out there in further developing the project,
just reach out to me via E-Mail to [email protected]!
Best regards
Markus ~ WolverinDEV
He just explained manwhy did you share the source code files?
i didn't understand what you meanHe just explained man
Really?i didn't understand what you mean
Yes, if there is no more compatibility with the 3.1 protocol, there will be no alternatives.is open source good?
if there is someone with your expertise (knowledge) to continue it is good!
But it's totally worth remembering that 90% of everyone here, we use teaspeak because of the 3.1 protocol, if there's no more update and this function is outdate the project will die.
when the licenses will drop yes and a lot, there will be no more reasons to buy them.
An alternative would be that you keep a plugin (or some premium addon linked with the license and with the 3.1 protocol and keep this function up to date) we will have a reason to have a premium license
this is my idea!
ps: I personally will keep my subscription premium until the 3.1 protocol is supported
Couldn't disagree more - security by obscurity is never a good way to improve security. If someone with ill intent would have liked to attack TeaSpeak servers before, there wouldn't be hindered by not having the source code, especially if there are tools like software decompilers for any language.Personally, I preffered that he didn't open source the WHOLE code, but relevant parts. Having TS3 protocol completely reversed and open sourced (client/server) is good in some ways but widens the attack surface of the current running servers, since now any hacker/cracker can look into the source to find vulnerabilities.
Security experts have rejected this view as far back as 1851, and advise that obscurity should never be the only security mechanism.
Well, I understand what you say and the arguments you said are strong. I didn't mean to refer that "it is strong because it is closed source" neither that "being closed source IMPROVES security". What I meant was that old versions are now subject to exploits because the possible flaws are open and easy to understand. This is because since the code is unknown (even though there is decompilers, they don't produce readable code, limiting the attack to only those who know how to debug etc), the exploits needs time and knowledge do get discovered, which straightens (even if just a little) the attack surface.Couldn't disagree more - security by obscurity is never a good way to improve security. If someone with ill intent would have liked to attack TeaSpeak servers before, there wouldn't be hindered by not having the source code, especially if there are tools like software decompilers for any language.
Maybe see Wikipedia regarding this topic, the second sentence literally is: