Used_Gate

I would like to test a garlicphone varient. I'm not opposed to i2p, I am just alot more familiar with Tor integrations than i2p.

Onionphone uses prepackaged binaries from the guardian project. https://github.com/guardianproject/tor-android.

I would basically need to find the same thing, but for i2p.

I've put some thought into this. The biggest roadblock to P2P is 24/7 persistence. You have to be online.

I think the most straightforward path to this is having the ability to setup a mailbox sort of how the relay works but on a machine that's on a 24/7 stable connection. Because it's already cross compatible with Linux systems, it would make the most sense to have a dedicated mailbox there, and have it forward your messages that were missed while you were offline.

Once the mailbox is set up, it's just a matter of tieing the separate mailbox identity to forward messages to you once your online. Ideally integrate tors built in authorized client protocol to ensure only one person is authorized to the mailbox.

I need ideas for what everyone wants. Features and niceties to make the expirence more polished. I have a limited set of devices that I can test on so finding bugs and edge cases is something I can fix, but limited to my environments/devices.

I've played with the ability to have a dedicated secure database built in for contacts but unsure if it's really needed and worth implementing.

Happy to contribute! So, currently (only while in the app for now) you can activate the mic with a double pressdown on volume if the setting is enabled.

My attempts to trigger the mic while outside the app came with a few unwanted side affects so I removed it for now until I find a solid way to do that.

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?

Haha, nah. You can only revcieve calls when listening and users will need your address and shared secret to make contact.

Would be a low conversion rate for spammers.

Middle node seems best to me as well, then your supporting services like this. This doesn't use any exit nodes at all.

The bandwidth on this is so tiny. Tor can handle this. Unless everyone uses it which i doubt will happen. I didn't include files and images for a reason. That takes a lot of bandwidth away from the network.