Repository navigation
|
Hello, I'm the developer of TeamTalk VO Client, an accessibility-focused TeamTalk 5 client for blind and visually impaired users (macOS/Windows/Linux), built with a licensed copy of the TeamTalk 5 SDK. I have a licensing question before investing development time into a side project, and I'd rather ask upfront than guess. I've also sent this question by email to contact@bearware.dk, but I'm opening this issue as well in case that's a better channel for you. We're considering building an independent server application under a different product name, protocol-compatible with TeamTalk 5 so that existing TeamTalk clients (including our own) can connect to it. The goal is to experiment with additional features for our accessibility-focused user base (e.g. time-limited bans, which the current protocol/server doesn't support). To be clear about the intended approach: this would not be based on the TeamTalk5 Server source in this repository, which is published under the commercial License Key terms in Do you have any objection to this kind of independent, protocol-compatible server implementation for interoperability purposes? We'd rather have clarity from you than rely on assumptions, and we're happy to adjust our approach based on your feedback. Thanks for maintaining TeamTalk — it's been a solid foundation for our accessibility work. |
Replies: 1 comment
|
There is no restrictions on building your own TeamTalk server as long as it does not use source code from the TeamTalk project. -- Bjørn |
There is no restrictions on building your own TeamTalk server as long as it does not use source code from the TeamTalk project.
-- Bjørn