Onionphone is a native Android application for anonymous, end-to-end encrypted push-to-talk voice and text communication over the Tor network. No servers, no accounts, no phone numbers — your .onion address is your identity.
Cross-platform compatible with Terminalphone — call between Android and Linux/Termux using the same protocol.
Optionally use your connection as a relay for ephermeral group channels.
Find the release page for version 1.0.2 which supports custom bridges for accessing censored networks.
Probably a bad idea to congest the limited bandwidth of Tor with voice chat.
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?
Plain speech can be compressed pretty well. I’m not an expert by any means, but I suspect latency would be the bigger issue.
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.
Yeah, unless they use specific nodes given by the community, i think it’s a bad idea
What’s the selfhosted component of this?
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.
Self hosting […] P2P
You do realise that’s a contradiction, right?
Unless you’re hosting a TOR node (which is outside of the scope here and, in the case of exit nodes, extremely risky), there’s nothing here that’s relevant to self-hosting.
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.
@Used_Gate I suggest getting this in f-droid if you want to see more usage.
Also, it looks like the actual development happens in private and then is thrown over the fence; https://gitlab.com/here/_forawhile/onionphone/-/commit/2c4afc462a42852f0d54dda0b333db9019f3d69e
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.
Extremely annoyed at devs who think everyone has Android phones when most people in the US have iPhones. Making an app incompatible with the majority of smartphones means you have not made an app
Extremely annoyed at users that think everyone has iOS phones, when most of the world have Android. Thinking that the US is the only relevant place means you have serious tunnel vision. /s
Oh and blame Apple. They are extremely hostile to open-source devs publishing apps on their platform.
Be mad at apple. This application would never work on the iPhone platform. To many gate keepers and restrictions on the OS.
Lol. Your post is pure US defaultism. The US only has 5% of the world wide population. Worldwide Android has around 71% market share while iOS only has around 27%.
Be better mister American.
Not OPs fault you’ve picked the wrong os ¯\(ツ)/¯
It’s roughly split in OS in US. I fell most security conscious users are android users. Sold might initially give slightly better initial privacy, android is far more customizable to the point there’s no contest.
Plus, I buy my phones outright so I’m not stuck with a $1000+ phone in a contract or subsidized phone plan making payments.
