Discord is banned from Türkiye since 9 october 2024. And talking from your device is a must for gaming, tiny-projects management, chatting with friends. I decided to create a voice chat app that works on terminal, no login required, no server in the middle. The first one to host session becomes coordinator and they talk in between by a mesh between the room. Tincan which comes from tincan phones from our childhoods. There is 2 tincan and there is a rope between them. In our app, devices are tincans and rope is the app. We added this rope to TUI too. There is nobody that listens your talkings. The content is private since we use QUIC TLS 1.3 and there is no key to relay. And there is no account, mail or phone number too. The weak part about privacy is IPs. iroh gives IPs under public key to who access your hosted session. Mesh that we use over 1 host actually limits how many people can talk at 1 session. It is not efficent to connect over 6 people in one single session. We use RNNoise for noise cancellation. And it automaticly adds 10ms delay. The invitation code is 63 characters but we fixed these by derive it to a session name and a password. You can store 200 lines on hosts device and distribute it to other by host. I couldn't test it on real Windows, there is test ofc but I don't know if it will run without bug. Let me know if you find anything about windows part. We are now v0.3.0 and
I am planning to keep developing it
Discord is banned from Türkiye since 9 october 2024. And talking from your device is a must for gaming, tiny-projects management, chatting with friends. I decided to create a voice chat app that works on terminal, no login required, no server in the middle. The first one to host session becomes coordinator and they talk in between by a mesh between the room. Tincan which comes from tincan phones from our childhoods. There is 2 tincan and there is a rope between them. In our app, devices are tincans and rope is the app. We added this rope to TUI too. There is nobody that listens your talkings. The content is private since we use QUIC TLS 1.3 and there is no key to relay. And there is no account, mail or phone number too. The weak part about privacy is IPs. iroh gives IPs under public key to who access your hosted session. Mesh that we use over 1 host actually limits how many people can talk at 1 session. It is not efficent to connect over 6 people in one single session. We use RNNoise for noise cancellation. And it automaticly adds 10ms delay. The invitation code is 63 characters but we fixed these by derive it to a session name and a password. You can store 200 lines on hosts device and distribute it to other by host. I couldn't test it on real Windows, there is test ofc but I don't know if it will run without bug. Let me know if you find anything about windows part. We are now v0.3.0 and I am planning to keep developing it