• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Information The future of TeaSpeak

Abrucci

New member
TeaSpeak is widely used to bypass Tea*Speak Server Slot Limitations. You want to commercialise TeaSpeak but already sell "cracks" with your Protocoll Keys. How does that makes sense?
 

uhpepee

New member
Hi, I need help enabling a bot it says "Music bots are not enabled! Please enable them via server settings!"
 

akkari

New member
Whats the current status? Is TeaSpeak dead?

TeaSpeak project seems to be dead by now. The last update on the client and server software was in may last year, admins don't respond to requests for over half a year and the forum seems to be deserted of staff/team members.

It was decided that TeaSpeak shouldn't belong to community (by not open sourcing it under a free license) for profit reasons, but was also seemingly dropped from the main developer @WolverinDEV .

Since this is the thread about the future of TeaSpeak, please update us: What is the current status and what are the plans in the for the near future of this project? Is it dead? Are you dead? Do plan on opening it up to the community? Is there still development going on? If this project keeps up staying and behaving like this, I and others are sooner or later gonna assume that TeaSpeak is officialy dead.

(For my part I bought a Tea_Speak license, because we cannot rely on TeaSpeaks current state any further, but I hope on being able to continue riding with TeaSpeak in the future if possible.)
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
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 contact@teaspeak.de!

Best regards
Markus ~ WolverinDEV
 

latters

Well-known member
Premium User
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 contact@teaspeak.de!

Best regards
Markus ~ WolverinDEV
if it's up to me, I'll keep helping, whether with $ or anything else!.
 

sstosic88

New member
Premium User
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 contact@teaspeak.de!

Best regards
Markus ~ WolverinDEV
Hi Markus,
nice to hear this , great news. As you mention free time to dedicate to this project is the biggest issue, but anyway you can count on me and I guess lot more people on this forum for further support and help.

Nice to her from you after very looooooooooooong time :) :) :)
 

heartles39

Fanatic member
Premium User
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 contact@teaspeak.de!

Best regards
Markus ~ WolverinDEV

why did you share the source code files?
 

Hoerli

Member
@WolverinDEV good decision!
Gather free coders and make this project a really great alternative to Tea*Speak!
Together, we can certainly push the project forward.


By the way: To all those who create forks, maybe link them here, so you can keep an overview.
Surely some will continue the work "elsewhere" and you will never find these works.
 
Last edited:

Saci

Fanatic member
Premium User
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
 

latters

Well-known member
Premium User
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
Yes, if there is no more compatibility with the 3.1 protocol, there will be no alternatives.

I also agree to continue paying premium license forever as long as it keeps working, even if it costs more than it currently is.
 

eduardoroeder

Fanatic member
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.

This could be potentially a security breach for all your current customers @WolverinDEV and then probably it will undermine the whole TeaSpeak infrastructure aswell.
 

akkari

New member
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.
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:
Security experts have rejected this view as far back as 1851, and advise that obscurity should never be the only security mechanism.
 

eduardoroeder

Fanatic member
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:
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.

This works well for the average software. But the one thing you didn't put in the equation is: this is an unmaintained software. Which means old versions are still running and open to exploits, where as people (exploiters) wouldn't need to invest their time into reversing and can just go into the source to find flaws. This creates a breach on the old versions and thus could be a security issue for the running users, potentially affecting the current userbase of the software.
 

kingston

Member
So just my 3 cents in 2022:

1. Never forget that people love free stuff and always crowd it. Thus no matter what you plan, you should absolutely focus on providing top-notch free functionality to magnet as many users as possible in the first place. The critical mass needs to be reached. More gaming and else communities need to hear about teaspeak. Promoting it through youtube could possibly help. Not many people really heard of it given millions of players worldwide.

2. Any hopes for some kind of discord bridge for teaspeak? I mean discord has become a monster. I don't have a clue regarding bridging teaspeak and discord, just a quick idea that something like that could bring lots of attention to it. The system should be both Tea*Speak and discord compatible.

3. I would never think that the software becomes open source. This is very generous of you, @WolverinDEV as I do realize how much effort you put into coding all of this. At the same time I'm worried because this means countless forks and attempts to monetize the project. But maybe I'm wrong. All in all I will be honored to take a look at the code.