4 ms·

This subject is near and dear to me, but after clicking around for a few minutes I was left none-the-wiser about what it actually is. Is it a client? A server?

This subject is near and dear to me, but after clicking around for a few minutes I was left none-the-wiser about what it actually is. Is it a client? A server? A protocol? Your home page encourages the user to play what looks like a child's game, and your links to "specification" don't actually pull up a specification. I say this, truly, as constructive criticism: I am probably in your core audience and I bounced off the site.

andreasdz 3y ago
Thank you for this! We've heard that feedback from other people as well and totally agree. It's true that it is hard to explain what p2panda really is: It is three things at the same time: 1. a protocol specification 2. a reference implementation and 3. an SDK. We can do better at separating these worlds, maybe by giving it different names or a better website. End of our current funding period we dedicated some time for an overhaul. The specification you find here: https://p2panda.org/specification/ https://p2panda.org/specification/ The SDKs you find here: https://p2panda.org/libraries/ https://p2panda.org/libraries/ The reference node implementation you find here: https://github.com/p2panda/aquadoggo/ https://github.com/p2panda/aquadoggo/ For more details what a "client" and a "server" is: https://p2panda.org/learn/networks https://p2panda.org/learn/networks
- javajosh 3y ago
  Thank you for the response. I will spend some more effort reading your site and related documents. I have a similar problem communicating the value and content of a project myself in the p2p web space. I'm not as far along as y'all. My audience will likely be programmers at first so I'm going to focus on them - and that audience wants to be able to identify what a thing is as fast as possible. I'm a big fan of informal communication, but with this I've found that going out of my comfort zone to be more formal has had a good impact on comprehensibility. Informality is there, but in small doses. I think this helps underscore the seriousness of the endeavor, too, as old-fashioned as that seems.

andreasdz 3y ago

Thank you for this! We've heard that feedback from other people as well and totally agree. It's true that it is hard to explain what p2panda really is: It is three things at the same time: 1. a protocol specification 2. a reference implementation and 3. an SDK. We can do better at separating these worlds, maybe by giving it different names or a better website. End of our current funding period we dedicated some time for an overhaul. The specification you find here: https://p2panda.org/specification/ https://p2panda.org/specification/ The SDKs you find here: https://p2panda.org/libraries/ https://p2panda.org/libraries/ The reference node implementation you find here: https://github.com/p2panda/aquadoggo/ https://github.com/p2panda/aquadoggo/ For more details what a "client" and a "server" is: https://p2panda.org/learn/networks https://p2panda.org/learn/networks

javajosh 3y ago
Thank you for the response. I will spend some more effort reading your site and related documents. I have a similar problem communicating the value and content of a project myself in the p2p web space. I'm not as far along as y'all. My audience will likely be programmers at first so I'm going to focus on them - and that audience wants to be able to identify what a thing is as fast as possible. I'm a big fan of informal communication, but with this I've found that going out of my comfort zone to be more formal has had a good impact on comprehensibility. Informality is there, but in small doses. I think this helps underscore the seriousness of the endeavor, too, as old-fashioned as that seems.