-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 06/18/2015 01:17 PM, Mitar wrote: Git + node.js on the back end, but the front-end is HTML+JS. - -- The Doctor [412/724/301/703/415] [ZS] PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1 WWW: https://drwho.virtadpt.net/ I would rather be despised for what I am rather than worshipped for what I am not.

On Thu, Jun 18, 2015 at 1:17 PM, Mitar <mitar(a)tnode.com> wrote: You want serverless decentralized data structures? That only run in the browser? You might look at the in-browser webtorrent stuff. Also talk to substack and Dominic Tarr. If it exists they will know. -- marc/juul

Eek, bringing down the whole level of conversation here, but I wonder what Mitar thinks of boosting public library signals into communities. If he has something working in the coops, I'm wondering if we could put a tower on the Tool Library as proof of concept... On Thursday, June 18, 2015, Marc Juul <juul(a)labitat.dk> wrote: browser? You might look at the in-browser webtorrent stuff. Also talk to substack and Dominic Tarr. If it exists they will know. operation is a way for nodes to discover each-other.

Well I was under the impression this was a mailing list, not a forum, so "thread hijacking" is not a thing I would consider. I just see a bunch of replies in my mailbox. However, I'm from an older generation and perhaps technology and the culture around it has simply outpaced me. ~ Elisa On Thu, Jun 18, 2015 at 10:26 PM, Mitar <mitar(a)tnode.com> wrote:

Hi! Yes, there is the whole stack: https://github.com/ssbc/secure-scuttlebutt (data layer) https://github.com/ssbc/scuttlebot (networking layer) https://github.com/ssbc/phoenix (phoenix) phoenix really looks cool. A decentralized web application. I really like what they are doing here. Pretty nice design, security considerations, modern approach. Here is my idea what I would like to see: https://github.com/ssbc/phoenix/issues/394#issuecomment-113042724 Some related tickets: https://github.com/ssbc/scuttlebot/issues/183 https://github.com/ssbc/scuttlebot/issues/172 Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m

Hi! Yes, but depending on the application. One I have in mind is more a distributed real-time chat application which could be used in the case that Internet uplink is severed to allow users in the network to help each other. For example, telling what is the IP of some central server somebody deploys and so on. So it is more a backup communication channel what I have in mind. Yes. hyperboot is really amazing work! Yes, that would be the only thing which would run on nodes, but it is pretty easy for a node to have that information. Although, I am not familiar with details of the protocol. Does client only needs to know IP and port (which could be part of JSON feed or something), or is there some negotiation protocol involved so you need some binary on the node? Also, for smaller mesh networks (IPv4-based) maybe simply scanning the whole subnet could work? If port would be fixed? Good luck with that. But on the other hand, a motivated person could join a mailing list or two of standardized bodies and start nagging about that. It requires time and dedication, but it does work. (The only issue is that there are full-time people employed to nag into the other direction.) So yea, maybe we should do spend some time on standardization processes. But this is then like 5 years in the future. Also, for standardization is often important that you can first show a working example, a use case, which might use some workaround. (At least for JavaScript things it is often like that that you show implementation in JavaScript, and then you can claim that standardizing that would improve performance and behavior.) Heh, with multicast you would almost not even need routing protocols anymore. ;-) Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m