Redecentralize

reason for doing it is slightly different than Adam's.<br> <br> Yes, it is HARD to get a distributed systems to work, but only if we try to treat them as a single system! Lots of distributed systems research is based on this notion /...\ abandon this notion where it makes sense, then it becomes much easier. Why are DHT hard? Because we want to distribute a hash table across machines and treat it like one! But then again, do we need one hash table? And if we do, should it be distributed /...\ propose we abandon the notion that a all distributed system should act like one system. Probably the only reason we think so is because corporations really care about this notion. But a free society?<br> <br> There are four modes of communication we do, public/anonymous, private/anonymous

pfrazee@gmail.com > wrote: > Adding some thoughts to Dominic's -- > > The challenge to decentralizing the application layer is that it involves > distributing authority. > > For instance, we need to authenticate users. The only distributed auth in > wide use right now is PKI. Since PKI only /...\ live within the orgs. That's a centralizing effect > that would still occur in an open IP/routing layer. > > After you've distributed identities, you need to distribute data-structures > as well, or we rely on central nodes to keep data-bases. Then, the messages > that /...\ sufficient to address. >> >> Security. >> >> Building truly p2p systems must deal with not only regular distributed >> systems problems, >> but also the problem of incenting the participants in the network to >> behave properly. >> This is trivial

Adding some thoughts to Dominic's -- The challenge to decentralizing the application layer is that it involves distributing authority. For instance, we need to authenticate users. The only distributed auth in wide use right now is PKI. Since PKI only works well for organizations, the user-identities have to live /...\ within the orgs. That's a centralizing effect that would still occur in an open IP/routing layer. After you've distributed identities, you need to distribute data-structures as well, or we rely on central nodes to keep data-bases. Then, the messages that construct the datasets need /...\ another challenge to decentralization that simply having addressability is not sufficient to address. Security. Building truly p2p systems must deal with not only regular distributed systems problems, but also the problem of incenting the participants in the network to behave properly. This is trivial if I own all the computers

pfrazee@gmail.com> wrote: > Adding some thoughts to Dominic's -- > > The challenge to decentralizing the application layer is that it involves > distributing authority. > > For instance, we need to authenticate users. The only distributed auth in > wide use right now is PKI. Since PKI only /...\ live within the orgs. That's a centralizing effect > that would still occur in an open IP/routing layer. > > After you've distributed identities, you need to distribute data-structures > as well, or we rely on central nodes to keep data-bases. Then, the messages > that /...\ sufficient to address. >> >> Security. >> >> Building truly p2p systems must deal with not only regular distributed >> systems problems, >> but also the problem of incenting the participants in the network to >> behave properly. >> This is trivial

challenge to decentralizing the application layer is that it >> > involves >> > distributing authority. >> > >> > For instance, we need to authenticate users. The only distributed auth >> > in >> > wide use right now is PKI. Since /...\ effect >> > that would still occur in an open IP/routing layer. >> > >> > After you've distributed identities, you need to distribute >> > data-structures >> > as well, or we rely on central nodes to keep data-bases. Then /...\ Security. >> >> >> >> Building truly p2p systems must deal with not only regular distributed >> >> systems problems, >> >> but also the problem of incenting the participants in the network to >> >> behave properly

netconf master" for the network and a random 24-bit ID. The netconf master is a node resposible for doing things like distributing configuration, creating and signing authentication certificates for private network membership, and assigning IP addresses. This too runs the same code as regular clients plus a service located /...\ plan to have both an open source / free component and a commercial component. ZeroTier One supports the creation of arbitrary distributed LANs. There will be a few public wide-open ones that will be free for unlimited use, but you can also create private distributed LANs. I plan to charge /...\ users to create private distributed LANs that are administrated by ZeroTier's own servers... basically you're paying for a reliable infrastructure that I manage and a nice web GUI to admin them. Nothing prevents you from running your own netconf-master but you'd have to create your

netconf master" for the network and a random 24-bit ID. The netconf master is a node resposible for doing things like distributing configuration, creating and signing authentication certificates for private network membership, and assigning IP addresses. This too runs the same code as regular clients plus a service located /...\ plan to have both an open source / free component and a commercial component. ZeroTier One supports the creation of arbitrary distributed LANs. There will be a few public wide-open ones that will be free for unlimited use, but you can also create private distributed LANs. I plan to charge /...\ users to create private distributed LANs that are administrated by ZeroTier's own servers... basically you're paying for a reliable infrastructure that I manage and a nice web GUI to admin them. Nothing prevents you from running your own netconf-master but you'd have to create your

netconf master" for the network and a random 24-bit ID. The netconf master is a node resposible for doing things like distributing configuration, creating and signing authentication certificates for private network membership, and assigning IP addresses. This too runs the same code as regular clients plus a service located /...\ plan to have both an open source / free component and a commercial component. ZeroTier One supports the creation of arbitrary distributed LANs. There will be a few public wide-open ones that will be free for unlimited use, but you can also create private distributed LANs. I plan to charge /...\ users to create private distributed LANs that are administrated by ZeroTier's own servers... basically you're paying for a reliable infrastructure that I manage and a nice web GUI to admin them. Nothing prevents you from running your own netconf-master but you'd have to create your

netconf master" for the network and a random 24-bit ID. The netconf master is a node resposible for doing things like distributing configuration, creating and signing authentication certificates for private network membership, and assigning IP addresses. This too runs the same code as regular clients plus a service located /...\ plan to have both an open source / free component and a commercial component. ZeroTier One supports the creation of arbitrary distributed LANs. There will be a few public wide-open ones that will be free for unlimited use, but you can also create private distributed LANs. I plan to charge /...\ users to create private distributed LANs that are administrated by ZeroTier's own servers... basically you're paying for a reliable infrastructure that I manage and a nice web GUI to admin them. Nothing prevents you from running your own netconf-master but you'd have to create your

another challenge to decentralization that simply having addressability is not sufficient to address. Security. Building truly p2p systems must deal with not only regular distributed systems problems, but also the problem of incenting the participants in the network to behave properly. This is trivial if I own all the computers /...\ prisons, and a millitary to protect your property system from neibouring property systems... Given the property system, it's easy to build a distributed system, you just have a datacenter, and you can hire people to run it, and build it and if theyfdo not do as you wish /...\ know where the other computers are, except very approximately, and you can't exactly send a computer to jail There is the distributed systems problems, but this is the easy part. What if my blog post becomes insanely popular? will my laptop have to serve terabytes of data? what happens

simply > having addressability is not sufficient to address. > > Security. > > Building truly p2p systems must deal with not only regular distributed > systems problems, > but also the problem of incenting the participants in the network to > behave properly. > This is trivial /...\ well aware that I'm skipping here a lot of issues, but that's what it boils down to. > There is the distributed systems problems, but this is the easy part. > What if my blog post becomes insanely popular? will my laptop have to > serve terabytes /...\ data? > what happens while I am disconnected from wifi inbetween cafes? > Obviously the answer is to distribute the data - prehaps you can get > my blog post from > other people who have read it, not just from me. If a few hundred > people from around

plan to have both an open source / free component and a commercial component. ZeroTier One supports the creation of arbitrary distributed LANs. There will be a few public wide-open ones that will be free for unlimited use, but you can also create private distributed LANs. I plan to charge /...\ users to create private distributed LANs that are administrated by ZeroTier's own servers... basically you're paying for a reliable infrastructure that I manage and a nice web GUI to admin them. Nothing prevents you from running your own netconf-master but you'd have to create your /...\ guessing because of the subscription model that it has some central coordinator? What I imagine doing with ZeroTier is running private web services and distributing the names (" http://couchdb.paul ") among my virtual LAN. Is that feasible? Paul On Mon, Jan 6, 2014 at 12:30 PM, Adam Ierymenko < adam.ierymenko@zerotier.com

plan to have both an open source / free component and a commercial component. ZeroTier One supports the creation of arbitrary distributed LANs. There will be a few public wide-open ones that will be free for unlimited use, but you can also create private distributed LANs. I plan to charge /...\ users to create private distributed LANs that are administrated by ZeroTier's own servers... basically you're paying for a reliable infrastructure that I manage and a nice web GUI to admin them. Nothing prevents you from running your own netconf-master but you'd have to create your /...\ guessing because of the subscription model that it has some central coordinator? What I imagine doing with ZeroTier is running private web services and distributing the names (" http://couchdb.paul ") among my virtual LAN. Is that feasible? Paul On Mon, Jan 6, 2014 at 12:30 PM, Adam Ierymenko < adam.ierymenko@zerotier.com

schrieb Paul Frazee: > Adding some thoughts to Dominic's -- > > The challenge to decentralizing the application layer is that it > involves distributing authority. > > For instance, we need to authenticate users. The only distributed auth > in wide use right now is PKI. Since PKI only /...\ make simple for the user. (I'm really short on good ideas how to hide this from users.) > > After you've distributed identities, you need to distribute > data-structures as well, This would be the easy part. We just create the data structures at all commissioned peers

another challenge to decentralization that simply having addressability is not sufficient to address. Security. Building truly p2p systems must deal with not only regular distributed systems problems, but also the problem of incenting the participants in the network to behave properly. This is trivial if I own all the computers /...\ prisons, and a millitary to protect your property system from neibouring property systems... Given the property system, it's easy to build a distributed system, you just have a datacenter, and you can hire people to run it, and build it and if theyfdo not do as you wish /...\ know where the other computers are, except very approximately, and you can't exactly send a computer to jail There is the distributed systems problems, but this is the easy part. What if my blog post becomes insanely popular? will my laptop have to serve terabytes of data? what happens

gmail any time. I could jump to any number of applications and hosts. That's how it works. But we haven't nailed certfile-distribution at scale yet, so that's why I call it an unsolved problem. I think the web-of-trust is inevitably what we'll need /...\ fact. If there's been a keypair compromise, the owner has to publish a revocation cert (you... did make a revocation cert, right?) and distribute it before too much damage is done. For two (2) there's only one kind of relationship in PGP's WoT, the "verified /...\ establish trust"?  (Though once I have that agreement, reconciliation is relevant only for nodes which missed the update itself.) After you've distributed identities, you need to distribute data-structures as well, This would be the easy part. Exactly. Identity is the unsolved problem for decentralization. Don't understand

could jump between yahoo and gmail any time. I could jump to any number of applications and hosts. But we haven't nailed certfile-distribution at scale yet, so that's why I call it an unsolved problem. I think the web-of-trust is inevitably what we'll need /...\ fact. If there's been a keypair compromise, the owner has to publish a revocation cert (you... did make a revocation cert, right?) and distribute it before too much damage is done. For two (2) there's only one kind of relationship in PGP's WoT, the "verified /...\ establish trust"?  (Though once I have that agreement, reconciliation is relevant only for nodes which missed the update itself.) After you've distributed identities, you need to distribute data-structures as well, This would be the easy part. Exactly. Identity is the unsolved problem for decentralization

London workshop in March, gathering FLOSS projects that are building software for peer production and organization, with a focus on distributed platforms. Scholarships to attend are offered to grassroots communities. ** Context ** We know that the Internet was originally decentralized, with protocols and services built by hackers. However, with the arrival /...\ Social: communication e.g. social-networking, microblogging, reworked email Social: collaboration e.g. wikis, pads, wave, shared file hosting, multimedia repositories Alternative to proprietary choices Federated / Distributed / Interoperable Open Standards Secure / Encrypted Encouraging Peer Production communities Encouraging the construction/maintenance of Commons Potential cases for discussion: Diaspora (federated social network) Wave (federated real /...\ time collaboration) Lorea (federated social network) DarkWallet (distributed wallet & social network) Ethereum (P2P infrastructure) MaidSafe (P2P infrastructure) Sandstorm.io (facilitates federated sw) Mailpile (encripted email) MediaGoblin (federated multimedia repository) OwnCloud (file hosting) … (your case) ** Scholarships ** There are a few scholarships for potential participants who wish to attend the event

possible to achieve economies of scale that can make things like storage and compute cheaper in bulk there than they are in a distributed system. They can also be more reliable. I host many things in the cloud because it almost never goes offline, while my home Internet connection /...\ funding, it's easier to monetize centralized services so more venture capital is poured into creating them. The other post mentions technical difficulties, distributed systems are hard and getting them to work even when you trust each piece to act in good faith is difficult. Writing a distributed system which

feel I'm missing something basic. Like a super-simplified paragraph of the over-all idea. > Askemos appears to solve trust in distributed application-state, correct? I'll need to read more deeply. I'm not a native English speaker. Notably here I'm inclined /...\ handled (ignored). (At least while there are less than 1/3 bad nodes.) Hence I'm inclined to say "Askemos solves trust BY distributing application state". Especially by distributing it to parties having a stake in either a) correct results b) conflicting interests iff they where trying to play

have minimal consequences for the others. That's one of the reasons web of trust is so problematic. Using web of trust for key distribution is desperation. Key distribution is the poster child for applying multiple heterogenous methods. It's the thing most necessary to carry out external /...\ shut down or compromise that will take most of the network with it, and there is nothing preventing a non-supernode from trusting (i.e. distributing their trust between) more than one supernode. Then you can have the supernode operators each decide which other supernodes they trust which shrinks

availa bility nodes. I think we have two different problems here and it makes sense to distinguish them. The first problem is the key distribution problem, which is an authentication problem. You have some name or other identity and you need a trustworthy method of obtaining the corresponding public /...\ some path that can be trusted to reliably deliver the request. Traditional broadcast media can actually solve both of them in different ways. Key distribution has the narrower solution. If you're The New York Times or CBS then you can e.g. print the QR code of your public /...\ issue. A reader who picks up an issue from a random news stand can have good confidence that the key isn't forged because distributing a hundred thousand forged copies of The New York Times every day or setting up a 50KW transmitter on a frequency allocated to CBS would

judge how successful that ambition has been.   The design team I led put together a peer to peer application infrastructure to support targeted distribution and clearing of news, events and distribution of background materials and personal interest preferences from anywhere in the world with each other that worked over /...\ others took it over and what to do about that. One observation is key institutions can't think let alone act in decentralised or distributed ways.  So even a bullet proof decentralised service tends to become centralised to suit the organisational and cultural expectations of such organisations. There

possible to achieve economies of scale that can make things like storage and compute cheaper in bulk there than they are in a distributed system. They can also be more reliable. I host many things in the cloud because it almost never goes offline, while my home Internet connection /...\ funding, it's easier to monetize centralized services so more venture capital is poured into creating them. The other post mentions technical difficulties, distributed systems are hard and getting them to work even when you trust each piece to act in good faith is difficult. Writing a distributed system which

This is a funky Distributed Autonomous Corporation which lets you pay for distributed storage in a distributed way. https://github.com/wetube/bitcloud/blob/master/Bitcloud%20Nontechnical%20White%20Paper.md It does something funky called "proof of bandwidth" (a type of proof of stake) to measure the bandwidth people are providing without them able to cheat

missing something basic.  Like a super-simplified paragraph of the over-all idea. > Askemos appears to solve trust in distributed application-state, correct? I'll need to read more deeply. I'm not a native English speaker. Notably here I'm inclined to say "yes", but then /...\ spotted and handled (ignored). (At least while there are less than 1/3 bad nodes.) Hence I'm inclined to say "Askemos solves trust BY distributing application state".  Especially by distributing it to parties having a stake in either a) correct results b) conflicting interests iff they where trying

possible to achieve economies of scale that can make things like storage and compute cheaper in bulk there than they are in a distributed system. They can also be more reliable. I host many things in the cloud because it almost never goes offline, while my home Internet connection /...\ funding, it's easier to monetize centralized services so more venture capital is poured into creating them. The other post mentions technical difficulties, distributed systems are hard and getting them to work even when you trust each piece to act in good faith is difficult. Writing a distributed system which

judge how successful that ambition has been. The design team I led put together a peer to peer application infrastructure to support targeted distribution and clearing of news, events and distribution of background materials and personal interest preferences from anywhere in the world with each other that worked over PSTN /...\ others took it over and what to do about that. One observation is key institutions can't think let alone act in decentralised or distributed ways.  So even a bullet proof decentralised service tends to become centralised to suit the organisational and cultural expectations of such organisations. There

sure you get invited first for tickets. > > http://redecentralize.org/conference/ > > It seems slightly odd having a centralized meetup for a distributed > group of distributed Internet groups. But it makes sense, and some > groups are organising team meetups around the same time. > > Please

make sure you get invited first for tickets.   http://redecentralize.org/conference/   It seems slightly odd having a centralized meetup for a distributed group of distributed Internet groups. But it makes sense, and some groups are organising team meetups around the same time.   Please share the conference page

funding, it's easier to monetize centralized services so more venture capital is poured into creating them. The other post mentions technical difficulties, distributed systems are hard and getting them to work even when you trust each piece to act in good faith is difficult. Writing a distributed system which

Cozy.io 2014/1/3 Eric Mill < eric@konklone.com > Yeah, it was only pretty recently that Docker announced they can now run on any Linux distribution . I will say that the learning curve on creating Docker containers is still a bit high for how conceptually simple (and beautiful!) Docker /...\ Austin on a project called Grimwire that's in this realm. I'm >>> also involved in the distributed systems community here, though >>> mostly as an enthusiast (I'm not implementing paxos or >>> anything). >>> >>> Nice meeting

contact with the centre - they must either stop operating until they re-establish contact, or continue to operate without the centre's guidance. A distributed system with a centre is still a distributed system - you can't escape the CAP theorem by putting a crown on one of the nodes

redecentralize@librelist.com Subject: Re: [redecentralize] Intros and current projects Yeah, it was only pretty recently that Docker announced they can now run on any Linux distribution . I will say that the learning curve on creating Docker containers is still a bit high for how conceptually simple (and beautiful!) Docker /...\ Austin on a project called Grimwire that's in this realm. I'm >>> also involved in the distributed systems community here, though >>> mostly as an enthusiast (I'm not implementing paxos or >>> anything). >>> >>> Nice meeting

familiar with this project, here's a quick summary: "Ethereum is a platform that makes it possible for any developer to write and distribute next-generation decentralized applications. Borrowing the concept of distributed consensus and cryptographic proof that makes cryptocurrencies such as Bitcoin so effective in trustless payments, Ethereum extends

come up which fuel the next decade of predator capitalism. Instead I would propose, for example, to found an organisation under public law to distribute literature like Amazon is doing with its services. Not only literature from the public domain but also new literature. But the central stock would /...\ literal heritage which is only very slowly digitalized, in Germany at least. This organisation would distribute public domain E-Books for free and printed books from the public domain for a cost-covering fee. And it would give authors and readers the possibility to sell and buy books directly, just

familiar with this project, here's a quick summary: "Ethereum is a platform that makes it possible for any developer to write and distribute next-generation decentralized applications. Borrowing the concept of distributed consensus and cryptographic proof that makes cryptocurrencies such as Bitcoin so effective in trustless payments, Ethereum extends

schrieb Francis Irving: > > http://redecentralize.org/conference/ > > It seems slightly odd having a centralized meetup for a distributed > group of distributed Internet groups. But it makes sense, and some > groups are organising team meetups around the same time. It's not odd, if used

schrieb Francis Irving: >> >> http://redecentralize.org/conference/ >> >> It seems slightly odd having a centralized meetup for a distributed >> group of distributed Internet groups. But it makes sense, and some >> groups are organising team meetups around the same time

address problems. As a direct outcome of the human model, we might look at community size. This depends on the facilities being offered. Distributed search, YaCy, for example, could have a very large number of users. Social networks, on the other hand, might need very focused small communities /...\ groups that overlap. Problems can then be resolved through side channels and appropriate server management tools. (and a 'server' could be a collection of distributed nodes, of course) OK, that'll do from me. Thanks for listening. Mike

Yeah, it was only pretty recently that Docker announced they can now run on any Linux distribution . I will say that the learning curve on creating Docker containers is still a bit high for how conceptually simple (and beautiful!) Docker is. I was a little taken aback. But they acknowledge /...\ Austin on a project called Grimwire that's in this realm. I'm >>> also involved in the distributed systems community here, though >>> mostly as an enthusiast (I'm not implementing paxos or >>> anything). >>> >>> Nice meeting

possible. Trust is the hard part in all of this. Once you have trust, then book-keeping is eventual consistency. After you've distributed identities, you need to distribute data-structures as well, This would be the easy part. Exactly. Identity is the unsolved problem for decentralization. What

establish trust"?  (Though once I have that agreement, reconciliation is relevant only for nodes which missed the update itself.) After you've distributed identities, you need to distribute data-structures as well, This would be the easy part. Exactly. Identity is the unsolved problem for decentralization. Don't understand

Hello Everyone,   Want to share with you the launch of a new distributed Content Distribution Network (CDN), primarily intended for video broadcast on demand. It's free to use (View) but requires registration to become a broadcaster. It scales to unlimited viewing hours for free! Broadcasters never upload

value of the compound key (based upon the public_key and >> name fields) used as the actual key on the distributed hash >> table. * signature - a cryptographic signature generated using >> the creator's private key with the fields described above. > > When it comes /...\ practice a > fuse mounted directory at my desktop is just yet another such > agent, certainly changing state. > Hah... a trivial distributed "Dropbox" clone built with fuse is one of my target "quick example" applications (a la "create a blog

shut down or compromise that will take most of the network with it, and there is nothing preventing a non-supernode from trusting (i.e. distributing their trust between) more than one supernode. Then you can have the supernode operators each decide which other supernodes they trust which shrinks

fuse mounted directory at my desktop is just yet another such >> agent, certainly changing state. >> > Hah... a trivial distributed "Dropbox" clone built with fuse is one of > my target "quick example" applications (a la "create a blog

time. But I don’t think it’s a huge leap. The question Tsitsiklis/Xu were looking at was storage allocation in a distributed storage pool (or an idealized form of that problem). Their research was backed by Google, who obviously is very interested in storage allocation problems

even harder to grow sustained decentralized deployments of software and services. But we also need to consider monetization or economical sustainability, easy software distribution and well evolved forms of collective deployments of software. best, holger > > Take Twitter for example. It lets me post tweets and follow other peoples

harder to grow sustained decentralized deployments of > software and services. But we also need to consider monetization or > economical sustainability, easy software distribution and well evolved > forms of collective deployments of software

Thanks! I am trying to fight the meme war and I think techno babbly phrases like Cloud Computing need a distributed counterpart :). I want people say "cloud computing? that's like soooo 2014". Max Jeremie Miller wrote: > Max, this is *great*, I love "grass computing

mempko@gmail.com > wrote: Jer, Thanks! I am trying to fight the meme war and I think techno babbly phrases like Cloud Computing need a distributed counterpart :). I want people say "cloud computing? that's like soooo 2014". Max Jeremie Miller wrote: > Max, this is *great*, I love "grass computing

Thanks! I am trying to fight the meme war and I think techno babbly > phrases like Cloud Computing need a distributed counterpart :). I want > people say "cloud computing? that's like soooo 2014". > > Max > > > Jeremie Miller wrote: >> Max, this

else publish it as a draft standard?). It is, very pragmatically, built on REST and WebDAV and TLS - no fancy  global distributed hashtable stuff (though we actually are looking into that to create a global 'address book' for this). The plus side is of course that it works

session on youtube, so apologies if I'm adding redundant info here. In the late 90s I was playing with the concept of a distributed search engine, but due to lack of time it just remained a 'future work' idea in a chapter of my degree's final year project

very expensive, so this cost is often a lot less than the cost of manually maintaining things. Decentralization is not just about networking, distributed systems, and data replication. It's also about solving a long list of more mundane problems that contribute indirectly... like this

sample sites that actually look pretty good. And dynamic, hmm, how does that work... https://zeronet.readthedocs.org/en/latest/using_zeronet/sample_sites/ Looks like there's some kind of distributed sql backend? I'm having trouble finding details on that

Donnerstag, 7. April 2016 19:23:04 UTC+2 schrieb Paul Frazee: Looks like there's some kind of distributed sql backend? I'm having trouble finding details on that Each site is backed by a sqlite database which is synchronized between the hosting peers. Quoting the documentation

value of the compound key (based upon the public_key > and name fields) used as the actual key on the distributed hash table. > * signature - a cryptographic signature generated using the creator's > private key with the fields described above. When it comes to contracts, one might find

might already have heard of it. There is a new project called Avatar [1] built by two finnish guys. It aims to create a distributed and secure P2P network which allows for messaging and data storage, among others. In order to be able to run on as many platforms

restrict. I work solo in Austin on a project > called Grimwire that's in this realm. I'm also involved in the > distributed systems community here, though mostly as an enthusiast > (I'm not implementing paxos or anything). > > Nice meeting you all, and I look

Austin on a project called Grimwire that's in this realm. I'm >>> also involved in the distributed systems community here, though >>> mostly as an enthusiast (I'm not implementing paxos or >>> anything). >>> >>> Nice meeting

used for evil so we should think about the ends not just the means For me, this means focusing on decentralising power by distributing control, knowledge and capability to the network Also considering what values we can enshrine through the use of technology - such as promoting agency, privacy, collaboration

restrict. I work solo in Austin on a project > called Grimwire that's in this realm. I'm also involved in the > distributed systems community here, though mostly as an enthusiast > (I'm not implementing paxos or anything). > > Nice meeting you all, and I look

protocols like GNUnet that HTTP absolutely can't mimic. Regarding WebRTC, the central dependency is signal routing and IP discovery. You can distribute that system with lots of HTTPS hosts, but you still need to address vulnerabilities in DNS and SSL and consider the possibility of a compromised host. That

tend to restrict. I work solo in Austin on a project called Grimwire that's in this realm. I'm also involved in the distributed systems community here, though mostly as an enthusiast (I'm not implementing paxos or anything). Nice meeting you all, and I look forward to seeing

work solo in Austin on a project >> called Grimwire that's in this realm. I'm also involved in the >> distributed systems community here, though mostly as an enthusiast >> (I'm not implementing paxos or anything). >> >> Nice meeting

Austinites I'd encourage to join the Distributed Systems Enthusiasts ( www.meetup.com/Distributed-Systems-Enthusiasts/ ) On Thu, Jan 2, 2014 at 5:55 PM, Virgil Griffith < i@virgil.gr > wrote: Talk to the TRSST people.  They are DC area. On Jan 2, 2014 6:13 PM, "Eric Mill" < eric@konklone.com

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

guessing because of the subscription model that it has some central coordinator? What I imagine doing with ZeroTier is running private web services and distributing the names (" http://couchdb.paul ") among my virtual LAN. Is that feasible? Paul On Mon, Jan 6, 2014 at 12:30 PM, Adam Ierymenko < adam.ierymenko@zerotier.com

ownership is a determining category in our societies. Otherwise Google, Twitter, FB and the likes could claim to be decentralized because they operate large distributed CDNs and other technical decentralization techniques. Clearly, as soon as an entity commercially captures interactions between humans and their machines there is a centralization

became less  anti-fragile once hosting became more complex than creating marked-up documents." At that point, you couldn't easily distribute the hosting media, so end-users couldn't create redundant hosts, and the centralized hosting removed optionality. Agree/disagree

fantasy. I'm not aware of any meshnet that would not be vulnerable to a well funded and very smart attacker's distributed DDOS or other disruption efforts. Technology can only be at best half the fix for the panopticon problem. The other half has to be political

fantasy. I'm not aware of any meshnet that would not be > vulnerable to a well funded and very smart attacker's distributed DDOS or > other disruption efforts. > > Technology can only be at best half the fix for the panopticon problem. > The other half

fantasy. I'm not aware of any meshnet that would not be > vulnerable to a well funded and very smart attacker's distributed DDOS or > other disruption efforts. > > Technology can only be at best half the fix for the panopticon problem. > The other half

fantasy. I'm not aware of any meshnet that would not be > vulnerable to a well funded and very smart attacker's distributed DDOS or > other disruption efforts. > > Technology can only be at best half the fix for the panopticon problem. > The other half

fantasy. I'm not aware of any meshnet that would not be > vulnerable to a well funded and very smart attacker's distributed DDOS or > other disruption efforts. > > Technology can only be at best half the fix for the panopticon problem. > The other half

fantasy. I'm not aware of any meshnet that would not be > vulnerable to a well funded and very smart attacker's distributed DDOS or > other disruption efforts. > > Technology can only be at best half the fix for the panopticon problem. > The other half

fantasy. I'm not aware of any meshnet that would not be > vulnerable to a well funded and very smart attacker's distributed DDOS or > other disruption efforts. > > Technology can only be at best half the fix for the panopticon problem. > The other half

part of the equations, there are plenty of free software project addressing this need, and they have no need to restrain use, modification, distribution, or access to their source code in any way to do so. Moreover, as you must know, peer-to-peer systems work best when more people

might already have heard of it. There is a new project called Avatar [1] built by two finnish guys. It aims to create a distributed and secure P2P network which allows for messaging and data storage, among others. In order to be able to run on as many platforms

meetup resource for redecentralize? I think people would respond with more interest if they knew the .org was behind it. We have the Distributed Systems Enthusiasts (on meetup.com ) for a near approximation in the mean-time. On Mon, Feb 3, 2014 at 10:41 AM, Francis Irving < francis@flourish.org

might already have heard of it. There is a new project called Avatar [1] built by two finnish guys. It aims to create a distributed and secure P2P network which allows for messaging and data storage, among others. In order to be able to run on as many platforms

ownership is a determining category in our societies. Otherwise Google, Twitter, FB and the likes could claim to be decentralized because they operate large distributed CDNs and other technical decentralization techniques. Clearly, as soon as an entity commercially captures interactions between humans and their machines there is a centralization

part of the equations, there are plenty of free software project addressing this need, and they have no need to restrain use, modification, distribution, or access to their source code in any way to do so. Moreover, as you must know, peer-to-peer systems work best when more people

doesn't mean that it is non-seeable or non-usable by others. > Well, it's non-modifiable and non-distributable, so it's proprietary, by definition. There are quite a number of free software projects that don't allow any modification that they don't like. But they

Data and P2P : peer to peer is the core of a decentralization of the internet. Being able to make some request over a distributed individual databases (personal clouds) solves the issues of big data (privacy, quality of data, centralization of power over a few actors being able to collect data

doesn't mean > that it is non-seeable or non-usable by others. > Well, it's non-modifiable and non-distributable, so it's proprietary, by definition. There are quite a number of free software projects that don't allow any modification that they don't like

friends at http://eQualit.ie (the people behind https://deflect.ca too) have put out a proposal for a new kind of decentralized and distributed data hosting/communication system: https://www.newschallenge.org/challenge/2014/submissions/lightweb-an-unbreakable-internet Take a look! Jacob Cook <jacob@peakwinter.net> https://peakwinter.net On 18/03/14 11:01 AM, Ross Jones wrote

plus are doing anonymous streaming tests now. Tribler is not merely a streaming Bittorrent client, we build various things on top of our P2P distributed database, such a wiki-style editing of metadata. We do not use the TOR network, we enhanced their protocol to make it compatible with

plus are doing anonymous streaming tests now. Tribler is not merely a streaming Bittorrent client, we build various things on top of our P2P distributed database, such a wiki-style editing of metadata. We do not use the TOR network, we enhanced their protocol to make it compatible with

blockchain will handle only identification and some metadata for all personal chains. http://datacoin.info/index.php?id=faq I'm not sure of the value above a distributed filestore more like Drogulus. And yet, it seems at least interesting to be aware of. Francis

tend to restrict. I work solo in Austin on a project called Grimwire that's in this realm. I'm also involved in the distributed systems community here, though mostly as an enthusiast (I'm not implementing paxos or anything). Nice meeting you all, and I look forward to seeing

parts to communicate directly without involving a third party translator or intermediary. (3) Physical decentralization A physically decentralized system is one that is distributed and robust from a physical point of view. Its parts can be split, moved around geographically, parts can fail without impacting the whole (too badly

might already have heard of it. There is a new project called Avatar [1] built by two finnish guys. It aims to create a distributed and secure P2P network which allows for messaging and data storage, among others. In order to be able to run on as many platforms

live in the middle-of-nowhere rural England and, earlier this week, Francis was in Liverpool (miles away from me) giving a talk about Distributed Autonomous Corporations (DACs). I can't get to Liverpool and I'm already in the UK. :-( Getting an interesting and diverse group of people together

have selected ClearOS for deeper & tighter integration. ClearOS is a cloud-connected Server, Network, and Gateway operating system designed for homes and distributed organizations. ClearOS is a central component of Tiki Suite and has a very large number of well integrated features to choose from: Mail & Webmail, LDAP

Twister is a blockchain Twitter alternative. http://twister.net.co/ Zeronet and Twister use implementations of the blockchain technology and Bittorrent to setup the netwerk and distribute the content. While Twister is limited to microblogging functionality Zeronet aims to setup all kind of services and websites. I would like to hear your

Public beta testing of our Android app, starting work on the desktop UI. Long term: Use Briar's data synchronization capabilities to support secure, distributed applications including blogging, crisis mapping and collaborative document editing. What are you excited about? The project is one of 54 semi-finalists in the Knight

definitely. Homomorphic crypto could have a *lot* of uses. It opens up the potential for things like black box certificate authorities that could be distributed as open source software. The CA signs your key. With what? A key pair it generated internally that cannot *ever* be viewed by *anyone*. :) -Adam

value of the compound key (based upon the public_key and name fields) used as the actual key on the distributed hash table. * signature - a cryptographic signature generated using the creator's private key with the fields described above. The public_key field is used to validate the signature value

protocol and the implementation of the neat idea of block chain is on the basis of twister. The block chain provides a sort of distributed notary service, certifying who owns a given nickname. The name is associated with a specific key pair, which is used for authentication and cryptography