121–130 of 147 posts
Earlier quoted context omitted.
Knowing the typical Arch/Gentoo tiling WM 8px console font anime wallpaper mindset on /g/, "bloat".
You say it like it's not a sign of a good developer who minds all the details. Though I'll admit I use a 16px font.
Earlier quoted context omitted.
How else would you connect to them in decentralized fashion? Your IP address isn't really useful information anyway. Note that being friends in this context means the users have added each other.
You could implement onion routing. But yes, you are right the IP address is usually a useless piece of information.
Earlier quoted context omitted.
You say it like it's not a sign of a good developer who minds all the details. Though I'll admit I use a 16px font.
It's not a reliable sign of a good developer at all, although you'd be hard-pressed to realize that if you're hip deep in the culture.
In my experience this shows that people actually care about the tech they work with. Which is a good sign.
Earlier quoted context omitted.
Starting a new, blue water distributed encryption system in a non-safe language is odd at this point. The protocol is being _noodled_ through and the code is in C. This is the coding style https://github.com/irungentoo/toxcore/commit/84c28337d248bad... this is openssl all over again https://github.com/irungentoo/toxcore/commit/1d6c3934736c369...
From a short look, I tend to agree with you. > memcpy(packet + 1, &con->ping_request_id, sizeof(uint64_t)); Copying multi-byte values into a network packet is a typical error made by novice developers - this will bite you hard as soon as somebody compiles the code on a Big Endian machine. Even if you might get away with this on opaque elements like a ping ID, the general approach should not be followed.
In all cases where it does matter, the values are converted.
Tox has been confirmed working on big endian machines by many people.
This project has largely disappointed me in many ways. I know HN doesn't care much about software licensing and that kind of stuff, but there are many legal issues behind the project that remain unsolved and have remained unsolved for majority of the project's lifetime. 1. The people behind Tox don't seem to be the copyright holders of their logo as admitted by one of the main developers[1]. The logo is the one also…
Earlier quoted context omitted.
the only thing I'm seeing from your posts is "I'm a fucking idiot who doesn't understand that C is safer than any interpreted pretend-you're-safe language"
When have you heard of a JavaScript dangling pointer problem? Buffer overrun? Segfault?
This project has largely disappointed me in many ways. I know HN doesn't care much about software licensing and that kind of stuff, but there are many legal issues behind the project that remain unsolved and have remained unsolved for majority of the project's lifetime. 1. The people behind Tox don't seem to be the copyright holders of their logo as admitted by one of the main developers[1]. The logo is the one also…
First, I suspect this is a concern troll named WubTheCaptain ( http://wubthecaptain.eu/ ), or a copycat of the concern trolling he originally did, that has hung around the tox threads because he craves attention and replies. But I'll reply to some of these even though I'm not a tox dev. 1. The logo was made, over many threads, by members of 4chan's /gd/ board for Project Tox to Do Whatever The Fuck You Want(tm) 7. A…
Although there was doxing, the issues slvr highlighted were entirely valid. IIRC, slvr had raised these in a private mailing list and they were then leaked to the public, at which point doxing occurred.
Earlier quoted context omitted.
First, I suspect this is a concern troll named WubTheCaptain ( http://wubthecaptain.eu/ ), or a copycat of the concern trolling he originally did, that has hung around the tox threads because he craves attention and replies. But I'll reply to some of these even though I'm not a tox dev. 1. The logo was made, over many threads, by members of 4chan's /gd/ board for Project Tox to Do Whatever The Fuck You Want(tm) 7. A…
> 7. A developer quit the project because she was harassed into quitting by another notorious troll, SaveTheInternet (the creator of an australian imageboard 4chon) and friends in the 4chon IRC. Basically, the arranagement at the time seemed to be quit and I take your dox down. Although there was doxing, the issues slvr highlighted were entirely valid. IIRC, slvr had raised these in a private mailing list and they we…
I did not imply that the issue raised was not valid, only that the pressure to quit was with troll(s) wielding dox and wub is being disingenuous like always with his concern trolling.
Earlier quoted context omitted.
> 7. A developer quit the project because she was harassed into quitting by another notorious troll, SaveTheInternet (the creator of an australian imageboard 4chon) and friends in the 4chon IRC. Basically, the arranagement at the time seemed to be quit and I take your dox down. Although there was doxing, the issues slvr highlighted were entirely valid. IIRC, slvr had raised these in a private mailing list and they we…
The concerns were public in IRC, github discussions and on the wiki, with a proposal to fix it: https://wiki.tox.im/Proposal:Slvr_Protocol_Rewrite I did not imply that the issue raised was not valid, only that the pressure to quit was with troll(s) wielding dox and wub is being disingenuous like always with his concern trolling.