I don’t agree with that. Both sides are acting as a server and a client, connecting via a onion service to either parties rendezvous. And then when you include the fact that you can become a relay, that is clearly self hosting a server in a pure sense.

There are no exit nodes involved in onion services. It all stays within the network.

Yes, I am seeking that out to put it on fdroid and actually tried but ran into a few roadblocks.

I am tracking changes since v1.0.0 in the changelog. From here on out the changes are all public. The initial commit has no history because it was brand new, and the architecture was forked from terminal phone for cross compatibility.

Latency is a huge issue, but it goes away with the PTT model. I tried full duplex on initial prototyping but it was trash.

PTT solves this by simply forcing the listen, digest, then respond. You can expect about 2-3 seconds of delay from when you release the ptt, to when the other side hears it.

Self hosting your own private P2P voice service.

Optionally use your device as a Audio relay for group calls, in which case you become the ‘server’ to all connected clients.

Be mad at apple. This application would never work on the iPhone platform. To many gate keepers and restrictions on the OS.

The bandwidth is low by design. I’ve excluded files and images to keep it down as well. You could talk 24/7 only use MBs.

If we want Tor to grow we need useful applications useful for everyone. I doubt this will be widely adopted.

I’ve contributed a large amount of bandwidth to the network so why can’t I use some?