Goodness, I overlooked this message... Did I really not respond to this? Or did I just fail to answer to the mailing list?
On Mon, Oct 07, 2013 at 01:39:05PM +0200, J?rg F. Wittenberger wrote: > Hi all, > > nice to see some traffic here. Just as you said it, *poof* it's gone ;-O > I too got some questions about secu-share/psyc I always > wanted to ask. > > What I'm looking for is a replacement for some working code. > (Yeah, I know never touch a running system... But I view code > as a duty, not an asset. Whatever I can reuse would be a win.) > > Could I do the following reasonably using PSC? > > The code in question would be the communication protocol used for BALL. > http://ball.askemos.org/ Woah. This is complex. I am totally not getting what you are doing there. > (((BALL is in a way yet another "social network software", albeit > we seriously claim it being based on strange, 300 years old > ideas like democratic societies - much in contrast to the cloud-hosted > networks under control of their respective parent companies. > It also does not enforce any kind of application like news feeds etc. > onto it's users. Instead it just gives the user a choice of > programming languages to roll their own. All BALL does is kinda > web without servers. Applications run in the web caches instead.))) Amazing madness. Just tried to download from http://ball.askemos.org/A0cd6168e9408c9c095f700d7c6ec3224?_v=download but I get 404. So it is written in scheme? I will be barely capable of figuring out what it might be doing. I was led to this page saying it would contain a p2p messaging software.. but I see some linked data navigation: http://ball.askemos.org/Abb8999dd38524dcc113f977d378a9ee0?_v=footnote&_id=1159 Maybe it's the wrong time of day to do this. > That code layer I want to replace, does byzantine failure tolerance > and collaborative state transfer. This could be done atop of any > chat-alike protocol. It takes one channel (chat room) per state > machine to coordinate updates and distribute the current state in > case a node responsible to keep a state machine was offline during > some update. Ok, I managed to understand this paragraph. So you need the pubsub API tg is working on. psyced has that too, but it's not very P2P... only if i get it to run behind Tor. > Coordinating updates would be easy even using channels, which allow > only restricted character sets and small messages. It there are only > some hash codes and fixnums to be exchanged. However: there MUST > be some authentication (e.g., cryptographic signatures) for messages. > (Otherwise it would die fromthe first Sybill attack.) PSYC happily deals with binary content. > State transfer however is different. Currently it's a custom protocol > over HTTPs similar to bitorrent. When, say a SQLite database is updated, > it's written blockwise, those blocks are transferred one-by-one. (We > never update the blocks; theirs hash forms a Merkele tree and blocks > are replaced upon update.) I don't see this being efficient in non-binary > encoding. since you'Re doing your own state thing, you can keep it binary. > (((Side note: we have a few real users, who have no idea that there > is some distributed, fault tolerant database underneath their software. > They just expect "reasonable" performance when they post updates > under the expectation that "this is a web site". When replacing > parts, I should not break their experience.))) amazing.. we should probably get some hints from you... it's not my home turf at least. > On Oct 4 2013, K???ra wrote: > >On Tue, Sep 24, 2013 at 2:14 AM, carlo von lynX wrote: > >>so, congratulations to the Tent team for implementing something > > Please someone enlighten me about the "Tent" you are talking about > here!! I vaguely recall some "tent" team from about 20-30 yrs ago. > You don't mean that one, do you? > > Otherwise "tent" looks like a bad search term. :-/ I think we were talking about https://tent.io/ > For those reasons I "expand" from "my own computer" to "a known > set of computers". Ack. Sorry for the delay. -- [email protected] https://lists.tgbit.net/mailman/listinfo.cgi/secu-share
