Posts with keyword: pcaa


dApps Are About Control, Not Blockchains

Decentralized applications, where the identity and application data are both controlled by the person using the app, provide the means of disintermediting companies who leverage their privileged position to work for their own interests and against ours.
Continue reading {dApps Are About Control, Not Blockchains}


Picos: Persistent Compute Objects

This brief introduction to picos and the components that make up the pico ecosystem is designed to make clear the high-level concepts necessary for understanding picos and how they are programmed.
Continue reading {Picos: Persistent Compute Objects}


Silo-Busting MyWord Editor is Now Public

The MyWord Editor and nodeStorage system are a perfect example of what I call a personal cloud application architecture.
Continue reading {Silo-Busting MyWord Editor is Now Public}


MyWord!

Dave Winer has been developing applications that support users owning their own data. His latest is a blog page rendering system he calls MyWord.io.
Continue reading {MyWord!}


nodeStorage and the Personal Cloud Application Architecture

Dave Winer has released a new, general-purpose app backend called nodeStorage. I'm very bullish on this model.
Continue reading {nodeStorage and the Personal Cloud Application Architecture}


Fargo and Personal Cloud Application Architectures

Fargo, a new outliner from Dave Winer is an excellent example of what I call "personal cloud application architectures" (PCAAs). PCAAs have benefits for users and developers alike and are cheaper and easier to build than traditional Web 2.0 applications.
Continue reading {Fargo and Personal Cloud Application Architectures}


Complex Pico Structures: Guard Tours

We've recently been working on a large project that we architected using picos, CloudOS, and the Personal Cloud Application Architecture. I'm pleased with how this turned out and the lessons that we learned.
Continue reading {Complex Pico Structures: Guard Tours}


Pico APIs: Events and Queries

A pico's API is not RESTful, rather it follows a pattern we might call Event-Query. KRL provides clear distinction in code for handling events and queries in a segregated manner. This has important implications for developers building picos and designing applications that use them.
Continue reading {Pico APIs: Events and Queries}