+- Sinisterly (https://sinister.ly)
+-- Forum: General (https://sinister.ly/Forum-General)
+--- Forum: The Lounge (https://sinister.ly/Forum-The-Lounge)
+--- Thread: tox.im (/Thread-tox-im)
Pages:
1
2
tox.im - Llebacc - 02-28-2014
I want to suggest the toxic project to anyone here using Skype for communication between other members of SL. Completely free, and protects privacy. That means no government data collection. It's much more secure than the mess Microsoft has going on with Skype already.
Users each have a unique ID that they trade should they want to add someone else to their list of contacts. It's very simple and easy to use.
The project is currently in early development, and as such currently only has a few features. Tox-core is the main project, with various clients, both CLI and GUI.
There is a FAQ Here.
The main site is www.tox.im.
My Tox ID is in my signature should anyone take interest to this. I like IRC better than tox, but #sinisterly on echonode is dead. I presume it's because Skype is more feature rich than IRC, in which case Tox is a good replacement.
RE: tox.im - Reiko - 02-28-2014
(02-28-2014, 06:37 AM)Llebacc Wrote: blah blah secure im
https://github.com/irungentoo/ProjectTox-Core
> We're using torrent-style DHT so that peers can find the IP of the other peers when they have their ID.
brb, tox resolver...
RE: tox.im - Llebacc - 02-28-2014
(02-28-2014, 06:40 AM)Starfall Wrote: https://github.com/irungentoo/ProjectTox-Core
> We're using torrent-style DHT so that peers can find the IP of the other peers when they have their ID.
brb, tox resolver...
"Tox must use UDP simply because hole punching with TCP is not as reliable.
Every peer is represented as a byte string (the public key of the peer [client ID]).
We're using torrent-style DHT so that peers can find the IP of the other peers when they have their ID.
Once the client has the IP of that peer, they start initiating a secure connection with each other. (See Crypto)
When both peers are securely connected, they can exchange messages, initiate a video chat, send files, etc, all using encrypted communications."
This is the rest of it. I'm sure there's exploits and vulnerabilities here, there are always going to be. The main part is avoidance of government data collection. A connection between peers should be secure.
RE: tox.im - Reiko - 02-28-2014
I'd like to make a suggestion to the developer but I don't wanna have to communicate with him/her/them directly. Why not use a telescoping onion routing network instead of pure P2P? It's still decentralized and no one can see or have any need for anyone's IP that way. It does introduce some latency but good voice codecs (see Opus) can handle it quite well, as can text messages.
RE: tox.im - Chromium - 02-28-2014
I don't recommend Tox as of now, especially with the security flaws it has had.
RE: tox.im - BreShiE - 02-28-2014
There are so many better options out there as of current, skype is a deadzone for hardchats. I'll continue to use XMPP with OTR.
RE: tox.im - w00t - 02-28-2014
Tox doesn't support a lot of things most people want. No easily sent nicknames, no good group chat system, and no good way to get anonymity AND security.
As for why onion routing wasn't built in, I shouldn't have to say much more than that it uses UDP.
RE: tox.im - Equinox - 02-28-2014
I don't really get why this is needed. Sure, it could stop people from seeing our shit, but there is always someone inside of your computer whether it be the NSA, a hecker, your parent, your girlfriend or of that sort.
RE: tox.im - Llebacc - 02-28-2014
Understandable, the project is nowhere near completion. I do think that tox will get more users as it proves itsself and gets all of the features potential users want.
RE: tox.im - w00t - 02-28-2014
(02-28-2014, 03:09 PM)Duubz Wrote: I don't really get why this is needed. Sure, it could stop people from seeing our shit, but there is always someone inside of your computer whether it be the NSA, a hecker, your parent, your girlfriend or of that sort.
Reasonable physical security and routine manual virus checks will prevent this.