From promike1987 at gmail.com  Tue Feb  2 23:05:52 2016
From: promike1987 at gmail.com (Mike Nagie)
Date: Wed, 3 Feb 2016 00:05:52 +0100
Subject: [General] Video FullScreen
Message-ID: <20160202230552.GA5894@arch.chello.hu>

Hi,

We use qTox (1.2.r344) which works quite well.
We would have liked to try the 'screen sharing' option, which is 
basically just a video call. It worked, but it was that small that I 
hardly saw anything.
How could I make it fullscreen?

Thanks in advance 
Mike


From mangholb at hotmail.com  Tue Feb  2 08:52:08 2016
From: mangholb at hotmail.com (L e)
Date: Tue, 2 Feb 2016 09:52:08 +0100
Subject: [General] Tox questions
Message-ID: <DUB127-W3454EAD5654988A7C9FB2C3DF0@phx.gbl>

Hello,I have found out about this tox project a while ago. I have a few questions.First of all, who is funding all these projects, and how? I'm asking mostly to understand the chances of survival of the project. It seems very intriguing, but unfortunately money rule the world...Second, why do all the clients have different names? Wouldn't it be easier for users if the names were consistent?How reliable are the apps currently? Will there ever be the possibility to sync contacts with one's phone numbers to automatically discover friends?I'm assuming you know Signal by Whispersystems. Why not adopt their encryption? Or why not help them with their project since they seem to be farther into development? Is it because it's centralized? (I'll be the first to admit I don't fancy my messages to go through amazon's servers...).Thank you for your time. 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tox.chat/pipermail/general/attachments/20160202/5300b88d/attachment.htm>

From aron.knifstrom at gmail.com  Wed Feb  3 08:49:00 2016
From: aron.knifstrom at gmail.com (=?UTF-8?Q?Aron_Knifstr=C3=B6m?=)
Date: Wed, 3 Feb 2016 09:49:00 +0100
Subject: [General] Tox questions
In-Reply-To: <DUB127-W3454EAD5654988A7C9FB2C3DF0@phx.gbl>
References: <DUB127-W3454EAD5654988A7C9FB2C3DF0@phx.gbl>
Message-ID: <CAEUogGnrYWjsA3-H9N2D3Nh+wqDrWTV-TO0WbpBP=eR=mE2N6g@mail.gmail.com>

Donations I guess, see the blog about the problems last year, after that
irungentoo had a personal fundraiser.

Tux are using NaCl, it's probably much better or equal compared to Signals
own encryption protocol.

Tux is of course all about being decentralized.

Best regards
Aron

2016-02-02 9:52 GMT+01:00 L e <mangholb at hotmail.com>:

> Hello,
> I have found out about this tox project a while ago. I have a few
> questions.
> First of all, who is funding all these projects, and how? I'm asking
> mostly to understand the chances of survival of the project. It seems very
> intriguing, but unfortunately money rule the world...
> Second, why do all the clients have different names? Wouldn't it be easier
> for users if the names were consistent?
> How reliable are the apps currently? Will there ever be the possibility to
> sync contacts with one's phone numbers to automatically discover friends?
> I'm assuming you know Signal by Whispersystems. Why not adopt their
> encryption? Or why not help them with their project since they seem to be
> farther into development? Is it because it's centralized? (I'll be the
> first to admit I don't fancy my messages to go through amazon's servers...).
> Thank you for your time.
>
> _______________________________________________
> General mailing list
> General at lists.tox.chat
> https://lists.tox.chat/listinfo/general
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tox.chat/pipermail/general/attachments/20160203/a0c02994/attachment.htm>

From gdr at gdr.name  Wed Feb  3 11:00:09 2016
From: gdr at gdr.name (GDR!)
Date: Wed, 3 Feb 2016 12:00:09 +0100
Subject: [General] Tox questions
In-Reply-To: <DUB127-W3454EAD5654988A7C9FB2C3DF0@phx.gbl>
References: <DUB127-W3454EAD5654988A7C9FB2C3DF0@phx.gbl>
Message-ID: <20160203120009.49e62738@gdr-desktop.gdr.name>

Hi,

I find your lack of formatting disturbing, but...

On Tue, 2 Feb 2016 09:52:08 +0100
L e <mangholb at hotmail.com> wrote:

> world...Second, why do all the clients have different names? Wouldn't
> it be easier for users if the names were consistent?

They're different clients, how do expect them to be named, the same?

That said, yeah, it would be nice to have an official client named Tox.

> How reliable are
> the apps currently? 

They're still in development.

uTox, for one, hasn't crashed for me in a very long time, but it has
lost ability to make (working) video calls somewhere around December,
perhaps they fixed it now.

Some time in 2015 there was a protocol change and all of the sudden,
oleder clients couldn't speak with newer ones (well, it was even more
interesting, older clients would see messages from newer ones, but with
first ~15 characters deleted, it was confusing).

So yeah, it's usable day to day but as long as you're willing to take
some time to fix things if they're wrong - downgrade to a latest
working version, etc. But bugs are usually quickly fixed.

> Will there ever be the possibility to sync
> contacts with one's phone numbers to automatically discover
> friends?

That's a question for devs, but I'll guess no, it won't. It is not
impossible to do it in a centralized manner (like tox-dns), but I doubt
somebody will start implementing this.

> I'm assuming you know Signal by Whispersystems. Why not adopt
> their encryption? Or why not help them with their project since they
> seem to be farther into development? Is it because it's centralized?

Well, if you use Tox it's usually because you believe that
decentralization is a good idea. There are plenty of messengers like
Signal, having plenty of developers working on them - because they're
relatively easy to implement, like all centralized apps are.

Note: I'm not a Tox dev.

> (I'll be the first to admit I don't fancy my messages to go through
> amazon's servers...).Thank you for your time.
> 	   		  


From dgncnbkr at gmail.com  Thu Feb  4 22:45:41 2016
From: dgncnbkr at gmail.com (Dogan Can BAKIR)
Date: Fri, 5 Feb 2016 00:45:41 +0200
Subject: [General] Concept of P2P DHT
Message-ID: <56B3D495.9000006@gmail.com>

Hi guys,
There is no enough documents out there to understand P2P DHT programming
perspective. And i'm almost getting crazy about this. Can you help me
with that with simple explanation? Yeah, i know there is key pair and
value per id/node etc. but i dont get the how this know each other and
how they are looking each other? like finding ip, port even if you give
them your node id value whatever.

Thanks.



From email at oranges.net.nz  Thu Feb  4 22:53:26 2016
From: email at oranges.net.nz (oranges)
Date: Fri, 5 Feb 2016 11:53:26 +1300
Subject: [General] Concept of P2P DHT
In-Reply-To: <56B3D495.9000006@gmail.com>
References: <56B3D495.9000006@gmail.com>
Message-ID: <56B3D666.8060508@oranges.net.nz>

Here is my high level understanding.

There is a distance function that defines for any given node, how
close a set of keys are to it (the closeness is arbitrary, it just
needs to be a consistent algorithm)

If your node is "close" to a key you store those key -> ipaddress
mappings on your machine. (To make this storage more robust, the key
-> ipadress mappings are a usually replicated on N machines, where N
is some arbitrary value of how resilient the DHT is.)

Now, you can't obviously know about all the nodes in a network. So
usually, you only know K nodes that are spread in either direction of
your "closeness value", i.e some will be closer to the zero, than you
and some will be closer to the infinity. (ideally half and half).
Although in this case I'm not sure exactly how tox chooses candidates
for you to know about (it may just be, the last K nodes I have spoken too)

To lookup a key, you find the 3 nodes that you know about that are
closest to the key that you want to find.

They may not actually know about the key, but what they can do is then
find the 3 closest nodes to the key that they know about and ask them.

This repeats and you eventually converge closer and closer to the key
you want until you find a node with the key -> ipaddress mapping and
it is returned to the original asker.

This is why when you first time you ever connect to the DHT you need
to use one of the bootstrap nodes at nodes.tox.chat, so that you can
"join" the DHT and become aware of at least some members of the network.

(Note that this simplifies the real situation as in tox.chat's case,
there is onion routing involved, so that you can't just trivially get
someones IP address by friend requesting them (they have to accept the
request)

Hopefully that clarifies a bit how the DHT works


From zero-one at tox.chat  Fri Feb  5 06:15:03 2016
From: zero-one at tox.chat (zero-one)
Date: Thu, 4 Feb 2016 22:15:03 -0800
Subject: [General] Concept of P2P DHT
In-Reply-To: <56B3D666.8060508@oranges.net.nz>
References: <56B3D495.9000006@gmail.com> <56B3D666.8060508@oranges.net.nz>
Message-ID: <56B43DE7.7000201@tox.chat>

You can also check out the toxcore documentation here
https://github.com/Tox-Docs/Text , but it's still relatively unpolished.

On 02/04/2016 02:53 PM, oranges wrote:
> Here is my high level understanding.
>
> There is a distance function that defines for any given node, how
> close a set of keys are to it (the closeness is arbitrary, it just
> needs to be a consistent algorithm)
>
> If your node is "close" to a key you store those key -> ipaddress
> mappings on your machine. (To make this storage more robust, the key
> -> ipadress mappings are a usually replicated on N machines, where N
> is some arbitrary value of how resilient the DHT is.)
>
> Now, you can't obviously know about all the nodes in a network. So
> usually, you only know K nodes that are spread in either direction of
> your "closeness value", i.e some will be closer to the zero, than you
> and some will be closer to the infinity. (ideally half and half).
> Although in this case I'm not sure exactly how tox chooses candidates
> for you to know about (it may just be, the last K nodes I have spoken too)
>
> To lookup a key, you find the 3 nodes that you know about that are
> closest to the key that you want to find.
>
> They may not actually know about the key, but what they can do is then
> find the 3 closest nodes to the key that they know about and ask them.
>
> This repeats and you eventually converge closer and closer to the key
> you want until you find a node with the key -> ipaddress mapping and
> it is returned to the original asker.
>
> This is why when you first time you ever connect to the DHT you need
> to use one of the bootstrap nodes at nodes.tox.chat, so that you can
> "join" the DHT and become aware of at least some members of the network.
>
> (Note that this simplifies the real situation as in tox.chat's case,
> there is onion routing involved, so that you can't just trivially get
> someones IP address by friend requesting them (they have to accept the
> request)
>
> Hopefully that clarifies a bit how the DHT works
> _______________________________________________
> General mailing list
> General at lists.tox.chat
> https://lists.tox.chat/listinfo/general



From dgncnbkr at gmail.com  Fri Feb  5 11:33:33 2016
From: dgncnbkr at gmail.com (Dogan Can BAKIR)
Date: Fri, 5 Feb 2016 13:33:33 +0200
Subject: [General] Concept of P2P DHT
In-Reply-To: <56B43DE7.7000201@tox.chat>
References: <56B3D495.9000006@gmail.com> <56B3D666.8060508@oranges.net.nz>
 <56B43DE7.7000201@tox.chat>
Message-ID: <56B4888D.5050308@gmail.com>

thank you guys, but i'm still confused so i'm gonna digging into Tox
Docs. ill be appreciate if u can send more resources.
thanks.

On 02/05/2016 08:15 AM, zero-one wrote:
> You can also check out the toxcore documentation here
> https://github.com/Tox-Docs/Text , but it's still relatively unpolished.
>
> On 02/04/2016 02:53 PM, oranges wrote:
>> Here is my high level understanding.
>>
>> There is a distance function that defines for any given node, how
>> close a set of keys are to it (the closeness is arbitrary, it just
>> needs to be a consistent algorithm)
>>
>> If your node is "close" to a key you store those key -> ipaddress
>> mappings on your machine. (To make this storage more robust, the key
>> -> ipadress mappings are a usually replicated on N machines, where N
>> is some arbitrary value of how resilient the DHT is.)
>>
>> Now, you can't obviously know about all the nodes in a network. So
>> usually, you only know K nodes that are spread in either direction of
>> your "closeness value", i.e some will be closer to the zero, than you
>> and some will be closer to the infinity. (ideally half and half).
>> Although in this case I'm not sure exactly how tox chooses candidates
>> for you to know about (it may just be, the last K nodes I have spoken too)
>>
>> To lookup a key, you find the 3 nodes that you know about that are
>> closest to the key that you want to find.
>>
>> They may not actually know about the key, but what they can do is then
>> find the 3 closest nodes to the key that they know about and ask them.
>>
>> This repeats and you eventually converge closer and closer to the key
>> you want until you find a node with the key -> ipaddress mapping and
>> it is returned to the original asker.
>>
>> This is why when you first time you ever connect to the DHT you need
>> to use one of the bootstrap nodes at nodes.tox.chat, so that you can
>> "join" the DHT and become aware of at least some members of the network.
>>
>> (Note that this simplifies the real situation as in tox.chat's case,
>> there is onion routing involved, so that you can't just trivially get
>> someones IP address by friend requesting them (they have to accept the
>> request)
>>
>> Hopefully that clarifies a bit how the DHT works
>> _______________________________________________
>> General mailing list
>> General at lists.tox.chat
>> https://lists.tox.chat/listinfo/general
> _______________________________________________
> General mailing list
> General at lists.tox.chat
> https://lists.tox.chat/listinfo/general



From rugk at posteo.de  Sun Feb 14 18:58:10 2016
From: rugk at posteo.de (rugk)
Date: Sun, 14 Feb 2016 19:58:10 +0100
Subject: [General] I love Free Software
Message-ID: <07671804da2550450c9f9e752a3dedda@posteo.de>

Hi,
today is I love Free Software day and I want to say thanks to all Tox 
contributors. Keep on the hard work! I just discovered this mailing list 
and thought subscribing would be a good idea. :)

Especially thanks to the main contributors: irungentoo for toxcore and 
tux3 for qTox, which is use mostly.
Keep on the good work and you'll finally be a secure and easy to use 
replacement for Skype!

I also posted this thanks you...
* on GNU Social: https://gnusocial.de/notice/7077065
* on Twitter: https://twitter.com/rugkme/status/698943727801393152

Best regards,
rugk

PS: Mailman send me the password I used for signing up to the mailing 
list. Can you turn this off? It is bad practise to send passwords in 
mails.
PPS: Would be nice to see you on GNUSocial too.

-- 
I offer PGP support. To send me a PGP-encrypted mail, please ask for my 
private mail address.


From zero-one at tox.chat  Sun Feb 14 21:04:08 2016
From: zero-one at tox.chat (zero-one)
Date: Sun, 14 Feb 2016 13:04:08 -0800
Subject: [General] I love Free Software
In-Reply-To: <07671804da2550450c9f9e752a3dedda@posteo.de>
References: <07671804da2550450c9f9e752a3dedda@posteo.de>
Message-ID: <56C0EBC8.7060009@tox.chat>

Happy "I Love Free Software Day"!

Install Gentoo,
David Zero

On 02/14/2016 10:58 AM, rugk wrote:
> Hi,
> today is I love Free Software day and I want to say thanks to all Tox
> contributors. Keep on the hard work! I just discovered this mailing
> list and thought subscribing would be a good idea. :)
>
> Especially thanks to the main contributors: irungentoo for toxcore and
> tux3 for qTox, which is use mostly.
> Keep on the good work and you'll finally be a secure and easy to use
> replacement for Skype!
>
> I also posted this thanks you...
> * on GNU Social: https://gnusocial.de/notice/7077065
> * on Twitter: https://twitter.com/rugkme/status/698943727801393152
>
> Best regards,
> rugk
>
> PS: Mailman send me the password I used for signing up to the mailing
> list. Can you turn this off? It is bad practise to send passwords in
> mails.
> PPS: Would be nice to see you on GNUSocial too.
>