Live data from Hacker News

Toxic – A distributed, secure, command-line based instant messenging client

github.com

31–40 of 91 posts

Re: Toxic – A distributed, secure, command-line based instant messenging client

#31

One of the links I posted above "mysteriously" disappeared. I have an archived version though. It's one of the key-points of the situation I exposed, so it's worth a read. https://archive.today/Y6LEw

Yeah, I deleted that Gist because you're using it out of context. I've talked with you one-on-one, and I've asked you to stop pasting it wherever someone mentions Tox.

Re: Toxic – A distributed, secure, command-line based instant messenging client

#32

Is Tox secure ? Compared to tinfoil chat

Tox still hasn't solved the serious metadata leakage issue. They tried to cover it up by adding onion-routing for friend requests, but ACTUAL MESSAGES are still done directly. Strong adversaries such as your ISP and agencies like the NSA, the GCHQ, etc. can still collect metadata about your conversations. The "Tox Foundation" tries to cover this up and pretend that "tox was never meant to be anonymous", but the truth…

Again, don't listen to this guy. He just copies and pastes this stuff from 4chan.

Re: Toxic – A distributed, secure, command-line based instant messenging client

#33
post #16

Earlier quoted context omitted.

Sounds like an extremely one-sided version of an argument. Why should we care about the devs? If the source is open and the software is good, I can tolerate Linus-tier rants if need be.

The issue is that if you use Tox you support their foundation, the Tox Foundation™ which deals with money in a shady way and deceive their users just in order to grow. I, for moral and ethical principles, don't want to have anything to do with such a thing and believe it's necessary to let people know about the situation. If they couldn't even respect an ex-developer privacy[0] how can we expect them to run a foundat…

> The issue is that if you use Tox you support their foundation

No, you really don't.

Your argument would have a lot more ground if you didn't sound like an off-the-street conspiracy theorist.

I guess that's what differenciates "conspiracy theorists" from the people who want you to believe vaccines causes autism and aspartame cancer. It's easy to dismiss something as crazy when the messenger sounds batshit insane, regardless of what the message is.

The tech community should know, what with Snowden and all.

Re: Toxic – A distributed, secure, command-line based instant messenging client

#34
post #32

Earlier quoted context omitted.

Tox still hasn't solved the serious metadata leakage issue. They tried to cover it up by adding onion-routing for friend requests, but ACTUAL MESSAGES are still done directly. Strong adversaries such as your ISP and agencies like the NSA, the GCHQ, etc. can still collect metadata about your conversations. The "Tox Foundation" tries to cover this up and pretend that "tox was never meant to be anonymous", but the truth…

Again, don't listen to this guy. He just copies and pastes this stuff from 4chan.

So what? It's a completely valid point.

Re: Toxic – A distributed, secure, command-line based instant messenging client

#35

DISCLAIMER: I am one of the many Tox ex-contributors, who used to work on it in the past. I don't want to be identified due to harassment other ex-contributors suffered in the past. The following message is my point of view on the project as a whole. Proplex, a long-time member of the Tox-Foundation and in charge of both infrastructure and marketing, called out tox devs because the 2 people in charge (irungentoo and…

You are just some troll trying to kill our project with fabrications and lies. You twist the truth to fit your own agenda. The guy in question tried to damage the project on his way out so yes I grepped our server logs for his ips because I wanted to know if he had tried anything weird. This guy posting this comment here is someone who decided to start this war against the project after I refused to kick someone who…

It doesn't help that you have zero clue how to answer professionally to actual trolls.

Hint: it involves replying to actual concerns rather than ad hominems. I mean, it's not like GP doesn't have any material on you, there's some pretty shitty stuff going on there.

Re: Toxic – A distributed, secure, command-line based instant messenging client

#36
post #32

Earlier quoted context omitted.

Tox still hasn't solved the serious metadata leakage issue. They tried to cover it up by adding onion-routing for friend requests, but ACTUAL MESSAGES are still done directly. Strong adversaries such as your ISP and agencies like the NSA, the GCHQ, etc. can still collect metadata about your conversations. The "Tox Foundation" tries to cover this up and pretend that "tox was never meant to be anonymous", but the truth…

Again, don't listen to this guy. He just copies and pastes this stuff from 4chan.

Which part of what he wrote is wrong? Please explain.

Re: Toxic – A distributed, secure, command-line based instant messenging client

#37

DISCLAIMER: I am one of the many Tox ex-contributors, who used to work on it in the past. I don't want to be identified due to harassment other ex-contributors suffered in the past. The following message is my point of view on the project as a whole. Proplex, a long-time member of the Tox-Foundation and in charge of both infrastructure and marketing, called out tox devs because the 2 people in charge (irungentoo and…

Also see #1229 (not much, but related): https://github.com/irungentoo/toxcore/issues/1229

Edit: I have no affiliation here, just an outside observer. I think it's relevant because, unlike the screenshot of #1228, the still alive 1229 issue (at least) shows that this happened nearly a month ago.

Whether or not the fact that it happened nearly a month ago matters I don't know, but at least it's a bit of extra context/info.

Re: Toxic – A distributed, secure, command-line based instant messenging client

#38
post #18

tox does not attempt to hide your ip. Every single friend you have added has your ip. This is by design.

That's partially true. However if you force TCP connections (in Toxic this is done with the -t flag) your IP is effectively hidden from your contacts because all your traffic gets relayed by TCP nodes in the network. The downside is that forced TCP connections are slower and less reliable.

Though to be properly anonymous you would need to run it through Tor: https://wiki.tox.im/Tox_over_Tor_(ToT)

The reason Tox doesn't have built in anonymity is because strong anonymity has a massive impact on quality (especially streaming data like audio/video). Our goal is to steal normal (non-paranoid) users from Skype and get everyone and their mother using strong encryption. In order to achieve that we need to have comparable quality rather than something that feels like you're using a 28.8k modem.

And again, anyone who actually wants anonymity still has that option.

Re: Toxic – A distributed, secure, command-line based instant messenging client

#39

DISCLAIMER: I am one of the many Tox ex-contributors, who used to work on it in the past. I don't want to be identified due to harassment other ex-contributors suffered in the past. The following message is my point of view on the project as a whole. Proplex, a long-time member of the Tox-Foundation and in charge of both infrastructure and marketing, called out tox devs because the 2 people in charge (irungentoo and…

One of the "proof"s given here is that a pull request changed a 2013 copyright to a 2013-2015 copyright, as though that's sinister somehow. I stopped reading after that.

Re: Toxic – A distributed, secure, command-line based instant messenging client

#40
My one experience with the Tox project was that I made a few (I thought) constructive suggestions. First, I suggested they use some form of static analysis or perhaps a 'safer' language to implement their core functionality - such as Rust or Go, instead of rather messy (at the time) C code.

Furthermore, having spent a lot of time researching parsers and how parser differentials can affect the security of systems, I suggested they use some tools, such as protocol buffers, to eliminate handwritten parsing code. The response I got was rather disheartening and downright hostile - it boiled down to the fact that protocol buffers involves C++ code which they are a priori against, without actually engaging in a factual argument (I wrote an article in the current USENIX login/ last years OSDI about parsers for binary protocols for anyone interested in background: https://www.usenix.org/system/files/conference/osdi14/osdi14... and github.com/jbangert/nail)

Post reply on HN