We’ve had enough of digital monopolies and surveillance capitalism. We want an alternative world that works for everyone, just like the original intention of the web and net.

We seek a world of open platforms and protocols with real choices of applications and services for people. We care about privacy, transparency and autonomy. Our tools and organisations should fundamentally be accountable and resilient.


Paul Frazee [LibreList] Re: [redecentralize] Applying User-Agent Behaviors in Web Applications to Enable Runtime Extension 2014-03-09 09:25:35 (6 years 7 mons 22 days 10:19:00 ago)
Yes, they are similar. To answer, I'll first mention that two additional posts were uploaded that explain more of the architecture:

"In-Application Sandboxing with Web Workers" http://pfraze.github.io/2014/03/08/in-application-sandboxing-with-web-workers.html
"Communicating with Web Workers using HTTP" http://pfraze.github.io/2014/03/08/communicating-with-web-workers-using-http.html

Askemos appears to solve trust in distributed application-state, correct? I'll need to read more deeply.

The trust question I'm investigating is application-integrity during third-party extension. Autonomy means, in this case, freedom to introduce new software without the host's blessing, like how an OS protects its kernel so that 3rd party code can execute without auditing by the OS vendor. Like an OS, the effectiveness will then rely on a well-designed permissions model.

Regarding shared state, the client/server model is continued, and so server nodes still maintain state authority, but the user may change which servers are used. Likewise, the permission model is still origin-based, but it treats all components of the app (page, remote hosts, worker plugins) as part of the network, and so origin is more granular. Servers may apply clustering algorithms to share state authority, and so (I suspect) Askemos' protocols should be applicable to them. Servers remain a network primitive for more complex topologies.

Another notable aspect of trust is data-containment, which Workers solve by executing in the user's environment, with all APIs removed but for postMessage (no xhr). This excites me for applications like Mint.com, which really needs proper isolation to function ethically.

I'm having trouble loading some of Askemos' docs, but I look forward to digging in a bit. Ping me in #stackvm on freenode (pfraze) sometime.

Be well,
Paul F

> On Mar 9, 2014, at 4:40 AM, "Jörg F. Wittenberger" <Joerg.Wittenberger@softeyes.net> wrote:
> Am 08.03.2014 23:01, schrieb Paul Frazee:
>> Wrote a post summarizing an interface model I've been researching for 
>> the past two years. In the scheme of redecentralizing, it's part of an 
>> architecture which supports social extension of web applications in 
>> order to provide autonomy from hosting organizations.
> That "autonomy" piece caught my interest.  After all, it's what 
> askemos.org is about.
>> If anybody has questions on the approach, feel free to ask; I'll post 
>> a few more articles in the near future.
>> http://pfraze.github.io/2014/03/08/applying-user-agent-behaviors.html
> After reading I can see that this is pretty much in line with the model 
> proposed under the name Askemos.  From a practical point of view it also 
> looks much like the way we program our agents.
> However I'm left with one question: how does this relates to autonomy 
> from hosting organizations?
> Towards this end we require active replication of the "server" end, such 
> that any peer may fail (with malice) any time harming at most itself.
> Best
> /Jörg