Text archives Help


Re: [projectvrm] The swing toward decentralized, distributed and hierarchical solutions


Chronological Thread 
  • From: Dan Blum < >
  • To: Michael Powers < >
  • Cc: Doc Searls < >, ProjectVRM list < >, Jeremie Miller < >, Adriana Cronin-Lukas < >, Keith Hopper < >, Jon Udell < >, Phil Windley < >
  • Subject: Re: [projectvrm] The swing toward decentralized, distributed and hierarchical solutions
  • Date: Thu, 10 Apr 2014 09:28:56 -0400

The Respect Network (and the Extensible Data Interchange (XDI) standard) provides a hybrid solution for  naming, addressing and communications topology 

- Personal clouds (which may be self-hosted or CSP-hosted) communicate peer to peer with each other, and with business clouds
- Cloud addresses are decentralized, expressed as UUIDs in XDI syntax
- Cloud names are stored in an XDI registry to allow for opt-in discovery and for reputation management. You can have multiple and/or pseudonymous names. Multiple names shouldn't be corelatable by other members but we do maintain one reputation for a member's names.
- The architecture allows for multiple, distributed peer registries and reputation systems in the future. 

Please see this blog post - Finding Heterarchy - for more information.
Best regards,
Dan Blum
Respect Network
Chief Privacy and Security Architect 



On Tue, Apr 8, 2014 at 11:45 AM, Michael Powers < " target="_blank"> > wrote:
We've been lurking while in development, but now we're expanding our
alpha test, so I wanted to add:

Trsst Project
<https://www.trsst.com>

In short, it looks and feels like Twitter, but you create and own your
own accounts, keys, and data.  You can either host yourself or choose
a vendor to host your content with no lock-in.  The hosting providers
are simply dumb http servers serving atom feeds via a rest API backed
by dumb storage.

This gives us a happy side-effect of being able to 'follow' all
existing RSS and Atom feeds, so there's a rich content ecosystem
out-of-the-box, and we leverage existing content workflows and
interop.  You can get a taste here:

https://home.trsst.com

The protocol is AtomPub plus XML-Sig and XML-Enc, so anyone can
support it, and we have a completely open Apache-licensed stack ready
for play here:

https://github.com/trsstproject/trsst

You can read more in one convenient place on our Knight News Challenge
entry -- please do click the little "Applause" button at the bottom of
that page if you like what we're doing.

https://www.newschallenge.org/challenge/2014/feedback-review/trsst-a-distributed-secure-blog-platform-for-the-open-web

Thanks, all.

On Tue, Apr 8, 2014 at 10:50 AM, Doc Searls
< " target="_blank"> > wrote:
> The latest is Etherium...
> <https://www.ethereum.org>
>
> Also in our midst, telehash:
> <http://telehash.org>
>
> CozyCloud:
> <http://cozy.io>
>
> CloudOS:
> <https://github.com/windley/CloudOS-Todo-Demo>
>
> Quiet but still ready, The Mine! Project:
> <http://themineproject.org>
>
> Your solution I'm forgetting here:
> <>
>
> Additional background:
>
> Escaping the black holes of centralization:
> <http://blogs.law.harvard.edu/doc/?p=8093>
>
> Distributed + Systems:
> <http://www.windley.com/tags/distributed+systems>
>
> Seven ways to think like the Web & more:
> <http://blog.jonudell.net/2011/01/24/seven-ways-to-think-like-the-web/>
> <http://www.wired.com/tag/jon-udell/>
>
> Others? Independent personal clouds and servers, I would imagine. (Reminder to self: hook up the SpaceMonkey: <https://www.spacemonkey.com>.)
>
> Maybe we should create a category for them in the wiki.
>
> Thoughts? Cc'ing a few others who might want to weigh in, including ones whose work is cited above.
>
> And, lest we think only along (what some among us might call) a libertarian vector here, let's also think about how distributed independence for individuals works for all those (and they are many) pulling VRM toward CRM and vice versa, for example by building CX (customer experience) systems and methods in the middle.
>
> Doc
>
>
>
>




Archive powered by MHonArc 2.6.19.