Intro to Yada Project - An Open Source p2p Social Network (proof of concept)
1–10 of 34 posts
Re: Intro to Yada Project - An Open Source p2p Social Network (proof of concept)
#2edit: Namely, how do you securely add a friend without prior knowledge of his public key?
Re: Intro to Yada Project - An Open Source p2p Social Network (proof of concept)
#3Sorry, but I don't understand how this works without a central server. edit: Namely, how do you securely add a friend without prior knowledge of his public key?
But in short, you can make friends with your friend's friends or you can be friends with an indexer, which will list a bunch of people you may or may not know that you can request to be friends with as well.
When you send a request through a friend, your connection is done securely through that already established relationship. Then that friend passes the request to the friend you want to be friends with that they are already friends with. Once that request reaches that friend and they accept, they will have the public / private key pair you originally generated. They will also have your IP address information and begin making secure connections directly to you without the need for the friend or indexer which you sent the request through.
Re: Intro to Yada Project - An Open Source p2p Social Network (proof of concept)
#41. A requirement seems to be the ability to make and receive socket connections. How would you address the typically restrictive home firewalls/NATs that most people are living with?
2. In the responses, a commenter raises this issue: With the above example of two users and 56 connections it seems like there could be scaling issues and or perormance issues. They may be less obvious on computers but mobile devices with more limited bandwidth and sometimes quotas may suffer for those users with muilple devices and their multi device highly connected friends.
The response from admin is: "Correct, this technology will have to scale along with hardware. I don’t believe we are too far off with 4g, more inexpensive memory and the like."
That doesn't inspire much confidence in the idea as a proof of concept.
You're also claiming to solve a far more fundamental problem: that of creating and maintaining a reliable distributed peer-to-peer network without any central servers at all. If you do have a practical solution to this problem, then a bunch of other difficult problems (like tracker-less Bittorent, for example, which currently relies on distributed hash tables) reduce to yours. Are you sure you're able to make that claim?
Re: Intro to Yada Project - An Open Source p2p Social Network (proof of concept)
#5There appear to be a number of problems with this proof of concept: 1. A requirement seems to be the ability to make and receive socket connections. How would you address the typically restrictive home firewalls/NATs that most people are living with? 2. In the responses, a commenter raises this issue: With the above example of two users and 56 connections it seems like there could be scaling issues and or perormance…
IPv6 is already being deployed from top tier mobile carriers and that allows globally rout-able addresses even behind NATs.
"That doesn't inspire much confidence in the idea as a proof of concept."
This technology is a little ahead of its time, but not by much. And by the time an end-user ready core is developed, we'll we be there.
"Are you sure you're able to make that claim?"
yes, the technical hurdles are only time consuming, not insurmountable.
Re: Intro to Yada Project - An Open Source p2p Social Network (proof of concept)
#6Sorry, but I don't understand how this works without a central server. edit: Namely, how do you securely add a friend without prior knowledge of his public key?
Checkout the how-to page and watch that video. It gives more detail. But in short, you can make friends with your friend's friends or you can be friends with an indexer, which will list a bunch of people you may or may not know that you can request to be friends with as well. When you send a request through a friend, your connection is done securely through that already established relationship. Then that friend pass…
How do you intend to solve the chicken and the egg problem this network will encounter?
Re: Intro to Yada Project - An Open Source p2p Social Network (proof of concept)
#7Earlier quoted context omitted.
Checkout the how-to page and watch that video. It gives more detail. But in short, you can make friends with your friend's friends or you can be friends with an indexer, which will list a bunch of people you may or may not know that you can request to be friends with as well. When you send a request through a friend, your connection is done securely through that already established relationship. Then that friend pass…
How do you intend to tackle NAT, dynamic IP addresses, and devices that aren't always on, or devices only accessible to some machines but not others? How do you intend to solve the chicken and the egg problem this network will encounter?
If you have no social graph on yada, then your very first connection to a friend may have to be unencrypted, but not in every case.
Re: Intro to Yada Project - An Open Source p2p Social Network (proof of concept)
#8Is that a joke? Seriously?
Re: Intro to Yada Project - An Open Source p2p Social Network (proof of concept)
#9There appear to be a number of problems with this proof of concept: 1. A requirement seems to be the ability to make and receive socket connections. How would you address the typically restrictive home firewalls/NATs that most people are living with? 2. In the responses, a commenter raises this issue: With the above example of two users and 56 connections it seems like there could be scaling issues and or perormance…
"1. A requirement seems to be the ability to make and receive socket connections. How would you address the typically restrictive home firewalls/NATs that most people are living with?" IPv6 is already being deployed from top tier mobile carriers and that allows globally rout-able addresses even behind NATs. "That doesn't inspire much confidence in the idea as a proof of concept." This technology is a little ahead of…
With all due respect, if your solution depends on the following developments in the real-world:
(1) Everyone upgrades their cheap DSL/cable home modems to something that supports IPv6 (2) Cell carriers allow incoming mobile data connections (can you say mobile DoS?) (3) People modify their firewalls (again, nothing to do with IPv4 or IPv6) to allow incoming connections (4) You devise some way of allowing static or otherwise identifiable IPv6 IPs, even when the ISP doesn't give you a static IPv6 IP
then I would say you have a number of challenges ahead of you. Assuming that device X and connect to device Y on the Internet, for consumer devices, is a very difficult proposition.