If you’d like to out in bringing Plexus to life – or have a recommendation to make – please leave a comment on this post. Automatic posting of comments is turned off, so your information will be kept private and secure – unless you indicate otherwise. Helpers should leave their name and email address – and any other relevant contact points. Any other contribution is up to you.
Thanks!
Posts
Sign me up to help, I love everything about it. I’ll be getting in touch soon.
That slideshow was impressive! If you’ve really built a working prototype of this thing in a week and a half, this may well be the final excuse I need to learn python.
I’m in.
I built the prototype in *four days*. Yes, Python is that good.
A fantastic concept, and something that would sit well with the other emergent social networking tool I’m following with interest, diaspora*
I’d certainly be interested in helping out. My development skills lie somewhere in the middle ground between front & back end, so I may be put to good use in building one of the first interfaces / clients to the service. The talk was both interesting & inspiring. I couldn’t make it to the BOF as I was involved in the Django BOF, tables away from you (but I tried to listen in as best I could). Count me in.
Im in, this is something that the world really needs, and I will be proud to contribute what I can.
Brilliant concept. I definitely would like to help if I can.
I’d like to help. Been doing python since 1.52
I’m thinking about how Plexus, Appleseed, Diaspora,Clique, and OneSocialWeb all do and don’t fit together. I think there are two key issues.
One is management. We all have lots of ways to share out to the world. One of Facebook’s killer features is controlled sharing. If Plexus is going to be a meaningful replacement, it needs to be able to share to a subset. It seems at the moment that the Plex only deals with public inputs and outputs.
The second big issue is data custodianship. Diaspora especially moves the data itself from a central server to the individual’s node. Plexus seems unique at the moment in that it separates connection management from data storage.
Is there a long range plan for Plexus to share data in a less than fully public way?
This is a good point and something that hasn’t been made clear: the client API (front-end) can determine exactly who gets what. When you pass along some media to be shared, you can pass it along promiscuously, so that everyone gets it, or with a specific set of individuals (which get translated into Sharer connection points) so that just a specific subset of individuals see the message. That capability is designed into Plexus from the start.
Wow! I’ve been thinking about this problem myself from quite some time and had the feeling that the right solution would be in this direction.
It’s such a great thing to read that you had that same idea, but thought it out a lot more, gave it a much defined form (translated that same ‘notion’ into a real ‘idea’.
I would really like to get involved, I know Python and been doing web development for quite some time.
I would like to use Plexus as my preventative, health improvent-strategy. I envision nutritonists’, philosophers, physical therapists, accountants, doctors in my plexus: all listening & sharing small contributions that finely tune every aspect of the context I view myself and my life/soul.This will contribute to a ongoing re-creation of my optimal-self. Physiology calls this: dynamic-equilibrium. Except, its now enhanced by the hyper-intelligence and hyper connectedness of my health cloud. E X C I T I N G!