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.
Jorg, Ah I had not heard of BALL, I have been reading through the documents at the "whilepaper" link. I think I can vaguely see where you are doing with this, but I would like to understand how your replication algorithm works. Do have have a link to a description of the algorithm? Also, regards your notary system: how are notaries assigned to officiate a particular "place" (is that correct Askemos terminology?) The data model in secure-scuttlebutt is very simple. There are messages, feeds, and ids. a feed is an append-only singly linked list of messages, owned by an id. The id is just the hash of the public key used to sign the messages in a feed. A feed may not be signed by mutliple keys and the key may not be reassigned. The idea is to optimize for simplicity even over convenience. This make both replication and verification conceptually simple. It is not necessary to trust any devices you do not have in your physical control. I think this will be enough to implement "web 2.0" style "social" applications such as twitter. Maybe not as convenient as twitter, but decentralized, and ultimately more flexible. More flexible, because not having centralized control over the service means I will not be tempted to prevent other people building on top of it, as twitter and it's like are increasingly doing. Do you have documentation on how your notary system and data replication works? Dominic On Sat, Sep 6, 2014 at 12:56 AM, Jörg F. Wittenberger <Joerg.Wittenberger@softeyes.net> wrote: > Boah, what a mistake I made! > > It's NOT 80kLOC it's 80Kbyte. > 60% for the HTML user interface, 932 lines "real code", including all > the SQL and non-essential functionality. > Only about 230 lines (pur functional code and again a lot HTML) one > would ever want to manually verify to be sure it does not violate the > required invariants. > > After all: it's supposed to be easy to audit, not prohibitive expensive > and error prone! > > Sorry for the noise, I had to correct that. > /Jörg > > Am 06.09.2014 08:34, schrieb Jörg F. Wittenberger: >> The payment system (current draft) for instance is here >> http://ball.askemos.org/A876f1fe6998ca9d43f2e66c11a3f0d4a >> that is, this is one wallet of it. You want to log in using "public" to >> find the actual thing. It's controlled by a single (though having >> 80kLOC large) source file: >> http://ball.askemos.org/Aa176138e655369f8c01c3044ced70cfc >> (be sure to read that in whitespace preserving source mode, do NOT let >> the browser mangle it and skip XML comments). >