Repository navigation
Replies: 4 comments 2 replies
|
Hi. You talk about join codes, but I'm wondering how you actually generate them? All I can see on the server I admin is a thing to generate a file or a TT link? Is it in the connection dialogue or somewhere? |
|
Hello. I agree that having encrypted communication should be a feature for everyone, regardless of whether it is paid for or not. |
|
|
I believe the correct approach is to remove the license and switch to a donation-based model. Since TT is open source, anyone can remove the license. This cannot be prevented unless TT is converted to closed source accessible only to the BearWare organization on GitHub. Additionally, while license conflicts would need to be checked, switching to a GPL-based model would allow for the application of many codecs and optimizations to FFmpeg. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I wanted to post this as a comment in the bearware.dk news page, but I receive an error about a captcha value not entered and the comment is never published, so I start this discussion after reading TeamTalk 5.22 announcement.
Join codes and UPNP support are excellent features that may fit perfectly into the pro server instead of encryption, which should be available for everyone. I haven't purchased the pro server yet because I don't want to host or resell servers professionally, nor spambots, nor Bearware logins, nor VPN blocking. I only want encryption for my personal server for personal use because I want that my communications go through a secure channel. Please, consider making this feature available also on the standard server. All other communication platforms available nowadays, free or paid, provide encryption as a basic feature which is not seen as a paid add-on for professionals. However, Teamtalk is the only software which has accessible desktop clients for most used operating systems, involves blind developers and users, and takes seriously screen reader support.
Regarding join codes, they are very useful and more intuitive than tt:// URLs or .tt files, but the connection information, including channels, channel passwords and login credentials, is shared with a central server. For privacy reasons, this should be explained in more detail in the warning dialog that is displayed when generating a code. A way to revoque codes should also be provided.
Hope you can take these suggestions into account. Thanks.
All reactions