Redecentralize

answer is that data must be encoded in the feed. Say, for a twitter-like app, when you follow someone, you'd post a message saying "i followed $DavidGeib" (where "$DavidGeib" is the hash of your public key) and probably also include in this message /...\ data-structures >> > as well, or we rely on central nodes to keep data-bases. Then, the >> > messages >> > that construct the datasets need to be verifiable, so that Alice can >> > rehost >> > messages from Bob without possibly /...\ altering them. So there are three >> > distinct challenges: authentication, message-verification, and dataset >> > coordination. >> > >> > Bitcoin, for example, solves all three of these problems. Broadly... >> > >> > - Authentication: RSA keypairs

prevent the agent from doing stupid things like removing all notaries. > 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. Which is pretty much /...\ layer some past state) of the application at the place. It is the unit of replication. I.e., a SSB feed corresponds to a place. Message&message is another interesting topic. We have two: http://askemos.org/index.html?_v=search&_id=1302 > The id is just the hash > of the public key used /...\ 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. That's a laudable goal. With Askemos we are looking especially toward "long term

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On 07/08/14 10:31, Jörg F. Wittenberger wrote: > Am 06.08.2014 13:58, schrieb Nicholas H.Tollervey: >> >> Items stored in the drogulus are designed to stand on their own >> and be self-verifiable through cryptographic signing /...\ Once we have the DHT, what do we do with it? I'd like it to handle > my conversation and business. Publications, private messages, > archive+backup, calendar, notes etc. > Quite... the drogulus is supposed to be application agnostic. > So I need an environment where /...\ agents (be them accounts > representing human users or automated, autonomous processes) > communicating via asynchronous, unreliable, unidirectional > messages. That's how we observe human interaction in writing. > Humans or juristic persons sending letters, registered mail etc. > Again, quite. Actually, it's not just humans

such. > or we rely on central nodes to keep data-bases. Let's outright rejected that for not being decentralized. > Then, the messages that construct the datasets need to be verifiable, > so that Alice can rehost messages from Bob without possibly altering them /...\ that the data matches the checksum. (At least that the way BALL implements the concept.) > So there are three distinct challenges: authentication, > message-verification, and dataset coordination. > > Bitcoin, for example, solves all three of these problems. Broadly... > > - Authentication: RSA keypairs. > (https://en.bitcoin.it/wiki/Address#Proving_you_receive_with_an_address). /...\ Message-verification: transaction signatures. > - Dataset coordination: the global blockchain and total ordering via PoW. Bitcoin – it's a bit tiring. Sure it does solve these things in some way. It has to. The only thing we do slightly different is the data set coordination. PoW is just

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 to be verifiable, so that Alice can rehost > messages from Bob without possibly altering them. So there are three /...\ distinct challenges: authentication, message-verification, and dataset > coordination. > > Bitcoin, for example, solves all three of these problems. Broadly... > >  - Authentication: RSA keypairs. > ( https://en.bitcoin.it/wiki/Address#Proving_you_receive_with_an_address ). >  - Message-verification: transaction signatures. >  - Dataset coordination: the global blockchain and total ordering

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 to be verifiable, so that Alice can rehost messages from Bob without possibly altering them. So there are three distinct challenges: authentication /...\ message-verification, and dataset coordination. Bitcoin, for example, solves all three of these problems. Broadly...  - Authentication: RSA keypairs. ( https://en.bitcoin.it/wiki/Address#Proving_you_receive_with_an_address ).  - Message-verification: transaction signatures.  - Dataset coordination: the global blockchain and total ordering via PoW. After all that, you need to deal with abusive

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 to be verifiable, so that Alice can rehost > messages from Bob without possibly altering them. So there are three /...\ distinct challenges: authentication, message-verification, and dataset > coordination. > > Bitcoin, for example, solves all three of these problems. Broadly... > > - Authentication: RSA keypairs. > (https://en.bitcoin.it/wiki/Address#Proving_you_receive_with_an_address). > - Message-verification: transaction signatures. > - Dataset coordination: the global blockchain and total ordering via PoW. > > After

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 What's the project? Briar is a messaging app designed for activists, journalists, and anyone else who needs a safe, easy and robust way to communicate. Unlike traditional messaging tools such as email or Twitter, Briar doesn't rely on a central server - messages

project, so here I am :) We work on a decentralized "social network" based on XMPP (XMPP is not only about instant messaging contrary to a popular belief). The good point about this is that we are standard and so compatible with other projects (the 2 only other XMPP /...\ projects able to manage blogging - to my knowledge - are Movim and Jappix). Our project do instant messaging, (micro)blogging, file sharing, games, end 2 end encryption (only OTR for instant messaging so far), and is multi-interfaces (web, desktop, command line, console). We have many planed projects like a micro /...\ AGPL v3+, and made with Python (2.7 so far, we start to think about Python 3 port). Ok, that's enough for a first message, you can check the website for more information: http://salut-a-toi.org or, if by any chance you are at FrOSCon, come to see us. Ah, last

have a mental image of what it might look like, and the protocol is designed to enable it with only the addition of new message types-- existing protocol messages should work fine and not need to be altered much (if at all). A bit about the ZT1 design: Supernodes /...\ communicating (unless you successfully NAT-traverse and connect directly) but cannot read your traffic. Relay nodes assist in NAT traversal by sending a RENDEZVOUS message to both peers periodically if they are being relayed that says "hey, you two, go talk to each other <here>." This enables reliable

specs. By publishing Askemos' protocols as reltypes, you standardize the protocols. For a simple example, if Askemos used a "heartbeat" protocol in which ping messages need to be exchanged regularly, you'd write a spec for the client and the server and upload it at, say, askemos.org/rel/heartbeat . A server /...\ inclined to say our projects solve fairly different problems. Let me step through the Mint.com example to hopefully clarify the differences. Reading your message I'd agree.  Looks like our projects solve kinda complementary problems, which makes us deal with similar issues.  Just you're concerned /...\ However that would happen before the resulting HTML is feed into the browser for display/interaction. The User-Agent behaviors and HTTP messaging handle the question of IPC between the Citibank page and the Mint worker. Typed links are used to export/discover the interfaces between those two threads

have a mental image of what it might look like, and the protocol is designed to enable it with only the addition of new message types-- existing protocol messages should work fine and not need to be altered much (if at all). A bit about the ZT1 design: Supernodes /...\ communicating (unless you successfully NAT-traverse and connect directly) but cannot read your traffic. Relay nodes assist in NAT traversal by sending a RENDEZVOUS message to both peers periodically if they are being relayed that says "hey, you two, go talk to each other <here>." This enables reliable

have a mental image of what it might look like, and the protocol is designed to enable it with only the addition of new message types-- existing protocol messages should work fine and not need to be altered much (if at all). A bit about the ZT1 design: Supernodes /...\ communicating (unless you successfully NAT-traverse and connect directly) but cannot read your traffic. Relay nodes assist in NAT traversal by sending a RENDEZVOUS message to both peers periodically if they are being relayed that says "hey, you two, go talk to each other <here>." This enables reliable

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 /...\ 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

have a mental image of what it might look like, and the protocol is designed to enable it with only the addition of new message types-- existing protocol messages should work fine and not need to be altered much (if at all). A bit about the ZT1 design: Supernodes /...\ communicating (unless you successfully NAT-traverse and connect directly) but cannot read your traffic. Relay nodes assist in NAT traversal by sending a RENDEZVOUS message to both peers periodically if they are being relayed that says "hey, you two, go talk to each other <here>." This enables reliable

section of the DOM for rendering its UI, and no other privileges. This solves the data-containment issue. The User-Agent behaviors and HTTP messaging handle the question of IPC between the Citibank page and the Mint worker. Typed links are used to export/discover the interfaces between those two threads /...\ Insofar your sandboxing text reads very related to our implementation. Obviously. Ah, yeah: applications in Askemos can communicate with each other. By passing asynchronous messages. The implementation makes sure that in - case the group of nodes maintaining the receiving application is not the same as the group of the sending /...\ messages are transparently forwarded to all nodes commissioned to run the receiving app. > 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. Hm.  This seems like "almost identical".  Correct

inspiration: Once we have the DHT, what do we do with it? I'd like it to handle my conversation and business. Publications, private messages, archive+backup, calendar, notes etc. So I need an environment where I see agents (be them accounts representing human users or automated, autonomous processes) communicating /...\ asynchronous, unreliable, unidirectional messages. That's how we observe human interaction in writing. Humans or juristic persons sending letters, registered mail etc. Side note: Tuns out documents like contracts (which is what "business" boils down into) could seen as a finalized subclass of agents which just /...\ peer hardware and maybe more. Nothing technological means can judge; it's a judgment about those very means among more. Ergo: publications and messages may leave the commissioned set, private data will never. Eventually I wonder how much effort it would be to maintain those expire times

with okfestival. Please go to  https://github.com/No9/peerconf-2013/issues/1#issuecomment-31490267 and pass on some thoughts if your interested.  Thanks --- Original Message --- From: "Eric Mill" <eric@konklone.com> Sent: 3 January 2014 02:59 To: redecentralize@librelist.com Subject: Re: [redecentralize] Intros and current projects Yeah, it was only pretty recently that Docker /...\ than the official install process. -- Eric On Thu, Jan 2, 2014 at 7:00 PM, Jacob Cook < jacob@jcook.cc > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 It certainly sounds like an interesting proposition. I've been holding off because Docker hasn't yet been reliably working

note: the following message has been posted also to cypherpunks and to unsystem lists, some comments have already been received like 'don't use github!' <sigh> this is more or less a cry for help on real ways to redecentralize EVERYTHING and get EVERYBODY (or most internet users /...\ this in a way that makes sense to a lot of people. A lot more than currently. OK I am done for now. [this message has also been posted to cypherpunks and unsystem lists] your thoughts please

working you can swap it out with something else. Then as long as you have [anything] that can perform the necessary function (e.g. message relay or lookup database), everything requiring that function can carry on working. > Yep. It's one of the reasons I don't think Bitcoin /...\ destination provide an authenticated confirmation of receipt. Then if there is no confirmation you ask some different trusted peer(s) to relay the message. That way all misplaced trust costs you is efficiency rather than security. If a trusted peer defects then you try the next one. Then even

integrated in CyanogenMod as the default SMS provider without any UX degradation, and they just moved beyond SMS to a more full-featured messaging system. And unlike Telegram, they're doing it all as 100% open source , and even experimenting with ways of incentivizing and crowdfunding contributions. So when /...\ link to something about > Telegram's travails? I'm interested. > > There's the potential for a dangerous wave of slickly designed messaging > apps that adopt the mantle of security without truly prioritizing it. I had > a frustrating interaction with the Tox team here, for example

Forwarded Message Date:    Tue, 19 Jun 2018 06:22:00 +0000 From:    =?utf-8?Q?Tom=20and=20Gary=27s=20Decentralized=20Dance=20Party?= <Dece /...\ MailChimp    unsubscribe from this list | update subscription preferences * ------- End of Forwarded Message Here are some of the referenced webpages  2. [5f64bd4a-e6eb-4f88-a5a4-2b535be19edd]     https://theddp.us5.list-manage.com/track/click?u=41ff3b5e83e66fffdf53475f0&id=259b9f1bc9&e=     bc2d3e9f9f  3. D10e / Startup Societies Summit

community's ideas. Anybody else? On Tue, Jan 14, 2014 at 2:14 PM, Odinn Cyberguerrilla < odinn.cyberguerrilla@riseup.net > wrote: [note: the following message has been posted also to cypherpunks and to unsystem lists, some comments have already been received like 'don't use github!' <sigh> this /...\ this in a way that makes sense to a lot of people. A lot more than currently. OK I am done for now. [this message has also been posted to cypherpunks and unsystem lists] your thoughts please

incentive is: whoever finds the hash collision to validate a new block of transactions will be awarded with the right to send a promoted message. Promoted messages have a certain probability of being displayed by twister client." Spam As A Service ;-) _Martin

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 26/07/14 23:18, David Burns wrote: > I think the complaining lasts too long. I get depressed thinking > about that stuff, I want to hear about what we can do. Maybe the > talk got there eventually, but I stopped watching before /...\ thought and analysis from rather hand-wavy philosophical problems to some of the concrete technical work we've been doing on FriendSecure (the message passing system) and the drogulus (the universal DHT). You say you want to hear about what we can do: How about thinking carefully and deeply about

BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/02/2015 08:43 AM, Robert Tischer wrote: > > The code will eventually be open read-only source. How's that for > innovation! > Hi, I just subscribed to this list after watching an interview of the organizers of this project /...\ quite surprised to read, in the first message I receive from the list, the sentence above. How is "redecentralization" compatible with proprietary software at all? "open read-only source" sounds like you're trying to get free work (as in gratis) from your users, without letting

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Dave, Heh... no nerves scraped, but I did want to address your complaint about complaining and, tbh, it's interesting and fun to engage with people who are critical. Best wishes, Nicholas. On 28/07/14 07:49, David Burns wrote: > Apparently I scraped /...\ analysis from rather hand-wavy philosophical problems to some of > the concrete technical work we've been doing on FriendSecure (the > message passing system) and the drogulus (the universal DHT). > > You say you want to hear about what we can do: > > How about thinking

partner and I were designing together and we had to keep track of our comments and their depths. best regards, Robert rtischer@hiveware.com -----Original Message----- From: redecentralize@librelist.com [mailto:redecentralize@librelist.com] On Behalf Of hellekin Sent: Wednesday, September 2, 2015 2:33 PM To: redecentralize@librelist.com Subject: Re: [redecentralize] Check out Hiveware's decentralized /...\ platform (as in no servers) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/02/2015 02:49 PM, Robert Tischer wrote: > Robert, the fact you're using non-standard ways to quote email and that you don't edit replies makes it quite difficult to follow. The "> " prefix

Original Message----- From: redecentralize@librelist.com [mailto:redecentralize@librelist.com] On Behalf Of hellekin Sent: Wednesday, September 2, 2015 12:07 PM To: redecentralize@librelist.com Subject: Re: [redecentralize] Check out Hiveware's decentralized platform (as in no servers) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/02/2015 12:05 PM, Robert Tischer wrote

Insofar your sandboxing text reads very related to our implementation. Obviously. Ah, yeah: applications in Askemos can communicate with each other. By passing asynchronous messages. The implementation makes sure that in - case the group of nodes maintaining the receiving application is not the same as the group of the sending /...\ messages are transparently forwarded to all nodes commissioned to run the receiving app. > 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. Hm. This seems like "almost identical". Correct? Except that

therefore it's a waste of time... > Then as long as you have [anything] that can perform the necessary function (e.g. message relay or lookup database), everything requiring that function can carry on working. You can have your cake and eat it too. It's easy. Just make /...\ destination provide an authenticated confirmation of receipt. Then if there is no confirmation you ask some different trusted peer(s) to relay the message. That way all misplaced trust costs you is efficiency rather than security. If a trusted peer defects then you try the next one. Then even

notary (you can just add or remove them like here http://ball.askemos.org/A876f1fe6998ca9d43f2e66c11a3f0d4a?do=notaries&version=17&login=public ) So the solution is RSA keypairs. If users sign their messages, it matters less who hosts and carries them. I could jump between yahoo and gmail any time. I could jump to any number of applications /...\ here: this seems to replicate data.  Does it protect against malicious updates too? It creates a verifiable log only -- the content of the messages is an application concern. We're looking at CRDTs to deal with convergence, but the systemic model for security is the reputation system. CRDT = "Cambodian

inclined to say our projects solve fairly different problems. Let me step through the Mint.com example to hopefully clarify the differences. Reading your message I'd agree.  Looks like our projects solve kinda complementary problems, which makes us deal with similar issues.  Just you're concerned with them /...\ rearrange it.  However that would happen before the resulting HTML is feed into the browser for display/interaction. The User-Agent behaviors and HTTP messaging handle the question of IPC between the Citibank page and the Mint worker. Typed links are used to export/discover the interfaces between those two threads

call up my friends. But maybe I prefer yahoo's interface? Well, tough luck. So the solution is RSA keypairs. If users sign their messages, it matters less who hosts and carries them. I could jump between yahoo and gmail any time. I could jump to any number of applications /...\ this seems to replicate data.  Does it protect against malicious updates too? It creates a verifiable log only -- the content of the messages is an application concern. We're looking at CRDTs to deal with convergence, but the systemic model for security is the reputation system. CRDT = "Cambodian

Doesn't help much with keeping data secret when attackers already own a peer.  Still at least no website defacement, no attacker sending messages in your name. On Tue, Jun 3, 2014 at 2:29 AM, Jörg F. Wittenberger < Joerg.Wittenberger@softeyes.net > wrote /...\ Steve On Mon, Jun 2, 2014 at 1:04 AM, Francis Irving < francis@flourish.org > wrote: FireChat, an iPhone app that does mesh network messaging, had an article in the Economist this month (can't find it to link to, and paywalled anyway). It seems

more coverage of remotestorage :) Ross > On 6 Aug 2014, at 08:33, Pierre Ozoux <pierre.ozoux@gmail.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all! > > I run this meetup [0] since 6 months now, and I'd like

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/01/14 00:45, Piers Sturley wrote: > Is there a date for the February meetup yet? I'd like to suggest Wednesday 5 February as a provisional date for a London meetup combining Redecentralize, Spring of Code and TA3M. (TA3M meetings are usually

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/01/14 12:09, Michael Rogers wrote: > On 15/01/14 00:45, Piers Sturley wrote: >> Is there a date for the February meetup yet? > > I'd like to suggest Wednesday 5 February as a provisional date for > a London

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/01/14 14:10, David Miller wrote: > Best way to get the date you want is to volunteer to organise. > EOM. > > p.s. This is not my way of volunteering. :-D OK... I volunteer to suggest that the next meeting

everyone know. Thanks Ross On 15 Jan 2014, at 14:16, Nicholas H.Tollervey <ntoll@ntoll.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 15/01/14 14:10, David Miller wrote: >> Best way to get the date you want is to volunteer to organise

sense. There are a lot of other useful tools that we may use, like ArkOS on the raspberry's the Serval project for free messages and call's inside a city by using a hybrid "android access point". And many, many more that are here on your site. Eventually

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/01/14 14:17, Ross Jones wrote: > Hey Nick, > > That’s great news, do you have a venue organised as well? If you > could let us know the details we can let everyone know. > > Thanks

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jer, Hello Holger, Greetings Redecentralizers, Apologies for the tardy response time on my part, I wanted to do you the courtesy of thinking about the content of this email rather than simply dashing something off. Of course, with a young family, I have

touch with person who can book C4CC :) On 15 January 2014 14:20, Nicholas H.Tollervey < ntoll@ntoll.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/01/14 14:17, Ross Jones wrote: > Hey Nick, > > That’s great news, do you have a venue organised

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/01/14 14:56, Ira wrote: > I can give someone access to the eventbrite pages to get that going > (or simply duplicate last event if we are agreed on date!). At the > last meetup, Frederik specifically was happy to organise

separate thread with specific peoples to organise off list On 15 January 2014 15:32, Nicholas H.Tollervey < ntoll@ntoll.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/01/14 14:56, Ira wrote: > I can give someone access to the eventbrite pages to get that going > (or simply

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm happy to kick in 20 quid towards beer/wine/snacks - it would be nice not to charge if possible, so as not to deter broke hackers. I can volunteer to organise on the 5th, 6th or 7th, but I'm busy

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21/01/14 10:15, Ross Jones wrote: > > Just thought I should let you know that the latest blog posts are > up (from Francis and Mike) and are at > http://redecentralize.org/blog/ - if anybody has anything they’d > like

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 *bump* Shall we have a London meetup next week? Cheers, Michael On 15/01/14 16:39, Ira wrote: > Booking C4CC will be free. Someone needs to sponsor the beer! I > think Malcolm was volunteering... Anyone else? Foods/wine? Or > charging for tickets

topic of your choice. Any takers? Cheers Ross On 31 Jan 2014, at 12:11, Michael Rogers < michael@briarproject.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 *bump* Shall we have a London meetup next week? Cheers, Michael On 15/01/14 16:39, Ira wrote: Booking C4CC will be free. Someone

topic of your choice. Any takers? Cheers Ross On 31 Jan 2014, at 12:11, Michael Rogers < michael@briarproject.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 *bump* Shall we have a London meetup next week? Cheers, Michael On 15/01/14 16:39, Ira wrote: Booking C4CC will be free. Someone

topic of your choice. Any takers? Cheers Ross On 31 Jan 2014, at 12:11, Michael Rogers < michael@briarproject.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 *bump* Shall we have a London meetup next week? Cheers, Michael On 15/01/14 16:39, Ira wrote: Booking C4CC will be free. Someone

Michael Rogers <michael@briarproject.org> wrote: > > > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA256 > >> > >> *bump* > >> > >> Shall we have a London meetup next week? > >> > >> Cheers

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 and to be easy to use, Avatar is implemented via JavaScript

Michael Rogers < michael@briarproject.org > wrote: > > > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA256 > >> > >> *bump* > >> > >> Shall we have a London meetup next week? > >> > >> Cheers

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 and to be easy to use, Avatar is implemented via JavaScript

Michael Rogers <michael@briarproject.org> wrote: >>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA256 >>>> >>>> *bump* >>>> >>>> Shall we have a London meetup next week

Original Message----- From: redecentralize@librelist.com [mailto:redecentralize@librelist.com] On Behalf Of holger krekel Sent: Wednesday, September 2, 2015 8:49 AM To: redecentralize@librelist.com Subject: Re: [redecentralize] Check out Hiveware's decentralized platform (as in no servers) On Wed, Sep 02, 2015 at 07:43 -0400, Robert Tischer wrote: > Redecentralizers

mind posting a link to something about Telegram's travails? I'm interested. There's the potential for a dangerous wave of slickly designed messaging apps that adopt the mantle of security without truly prioritizing it. I had a frustrating interaction with the Tox team here, for example: https://github.com

mind posting a link to something about Telegram's travails? I'm interested. There's the potential for a dangerous wave of slickly designed messaging apps that adopt the mantle of security without truly prioritizing it. I had a frustrating interaction with the Tox team here, for example: https://github.com

link to something about > Telegram's travails? I'm interested. > > There's the potential for a dangerous wave of slickly designed messaging > apps that adopt the mantle of security without truly prioritizing it. I had > a frustrating interaction with the Tox team here, for example

BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/02/2015 12:05 PM, Robert Tischer wrote: > > RT>"open source" for me is tantamount to promiscuous copying without > regards to ownership of intellectual property rights. Only the early > days of communism believed this was an ideal

about Telegram's travails? I'm interested. > >     There's the potential for a dangerous wave of slickly designed messaging apps that adopt the mantle of security without truly prioritizing it. I had a frustrating interaction with the Tox team here, for example

BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/02/2015 02:49 PM, Robert Tischer wrote: > Robert, the fact you're using non-standard ways to quote email and that you don't edit replies makes it quite difficult to follow. The "> " prefix is something most email software

They did this at the Colorado meetup, so could ask for hints as to what worked. But basically, install TeleHash and send each other messages and play with simple apps on top of it. http://www.meetup.com/SolidStateDepot/events/154226712/ Francis On Mon, Mar 17, 2014 at 07:10:55AM +0000, Nonmonotonix wrote

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/03/14 15:01, Ross Jones wrote: > It’s been mentioned already, but .. > > Just in case anyone was considering making a submission for the > latest Knight Challenge ( > https://www.newschallenge.org/challenge/2014/submissions ) but > was procrastinating

Looks good Eric. https://www.newschallenge.org/challenge/2014/submissions/httplocal-a-framework-for-open-architecture-web-applications On Tue, Mar 18, 2014 at 10:23 AM, Nicholas H.Tollervey < ntoll@ntoll.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/03/14 15:01, Ross Jones wrote: > It’s been mentioned already, but .. > > Just in case anyone was considering

Looks good Eric. https://www.newschallenge.org/challenge/2014/submissions/httplocal-a-framework-for-open-architecture-web-applications On Tue, Mar 18, 2014 at 10:23 AM, Nicholas H.Tollervey < ntoll@ntoll.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/03/14 15:01, Ross Jones wrote: > It’s been mentioned already, but .. > > Just in case anyone was considering

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Loomio is a really cool project! After struggling with Liquid Democracy it was really a breath of fresh air. I'd like to talk to you about how we might build similar tools on top of decentralised p2p infrastructure. Here's my Knight submission

been hearing great stuff about Briar! On Tue, Mar 18, 2014 at 4:41 PM, Michael Rogers < michael@briarproject.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Loomio is a really cool project! After struggling with Liquid Democracy it was really a breath of fresh air. I'd like

time to chat if you like :) rich@loomio.org On 19 March 2014 09:41, Michael Rogers < michael@briarproject.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Loomio is a really cool project! After struggling with Liquid Democracy it was really a breath of fresh air. I'd like to talk

Next planning call is tonight at 8pm. Come! On Mon, 14 Sep 2015 at 15:25 hellekin < hellekin@gnu.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/14/2015 08:32 AM, Benjamin Heitmann wrote: > > are there any updates on the date and format of the un-conference

technology they're setting up/using. -- Anish On Thu, Sep 17, 2015 at 7:47 PM, hellekin < hellekin@gnu.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/17/2015 09:52 AM, Anish Mangal wrote: > > I believe the problem has atleast two aspects - educating people and > engaging them

other people run similar sessions on the other tools people most want (see survey on Redecentralize.org homepage) eg on state of instant messaging alternatives.    Francis    On Thu, 15 Oct 2015, at 06:25 PM, will.sch wrote:     Hi,   I'm Will

those who haven't seen the now-dormant list, it was active in early part of the 00 decade. 7000+ messages on P2P and decentralization:     http://groups.yahoo.com/neo/groups/decentralization/conversations/messages

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cory Doctorow - I didn't realise this but in 1999 he was one of the three people behind OpenCola (a P2P content sharing/searching product see: https://en.wikipedia.org/wiki/Opencola_%28company%29). N. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJSpfAuAAoJEP0qBPaYQbb6MBUIAI3nEi/VAyD88Xd8j9RyKHk4

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Since no one else has mentioned it on this list, snaffle up a ticket here: https://www.eventbrite.co.uk/e/redecentralize-january-london-meetup-registration-9841361778 N. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJSsWJRAAoJEP0qBPaYQbb6KEgH/RKRUqqbeMVjy0VsSFttYxIB 7XO5sn6C28FAyUnqZ+jRYLy2VReS5H+AMhfyqHx2OGsQmubbC/b1plOgAT0uOVVU MIn4IwdxUHKIi2epZL13s18ekr7GMF6hAYvHeqquyJdJj1wZsKsXNvAFInatF9qa S0x5Tm9X9337IpssgsDDJtWuqSs3tPK9ZLUh5owOhfdgkdrMEyRUvB6z7w48KNfj PwWvekim1/wMVuSOYS3zkzKjPUSyCohhE+RC8wlVe2IUAhsrHq3/PLNwJnbFAGsQ k8jy7h54UB38dsHw00Ii039zs2npCEVGy7TJok0z1B+zly3oTpplle3shGyedfA= =/v5s

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Well, that was fun. Irina talked about possible sponsorship and alternative locations for the meetup, so I was happy to make the acquaintance of Alison Powell (@a_b_powell) who works at LSE which appears to have lots of spare rooms

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, There are at least three groups trying to organise regular London meetups for people working on technology for social change: Techno Activism Third Mondays, Redecentralize, and Spring of Code. I'd like to suggest that we pool our efforts and have

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This: http://www.techcityinsider.net/redecentralization/ Featuring Ira and Smári. Enjoy. N. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJS0CxUAAoJEP0qBPaYQbb6mesH+gMPW7p+7XGVyax0L0KshX0J Qa6nTm5HKMMONUuRmnUIJP3CqL6V/k8iYsLUsKSix1cXqrWYN8aaggAWTYyl1XyC ZbXZU/MjgXRvUXQ/H0wgnx+W2vH/C/LJQz+WhUbaeyxo/FHMmdkQkHy5Bk3DwR9W T45P/FJqf74YZYn3dSc8N4K57VMG4Ol1lHbb2wJuBOTNBIO1lHxsx3QKDVShj8RU C8nIUItdyYNK4VlQZJXSEcbC3hPTSQhz1g6HwXjm9ssO95z+xoGorWMxMR56eHuo cwvVhh0Vbr71yN6Vhx4zh0EdIcUYUvapJe+ggUZ3NVfCvWzi1t5iJOLutPNXv4g= =Zocy -----END PGP SIGNATURE

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 and to be easy to use, Avatar is implemented via JavaScript

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, There's lots of interesting things going on but we're all so (physically) far apart. For example, I live in the middle-of-nowhere rural England and, earlier this week, Francis was in Liverpool (miles away from me) giving a talk about

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, This is my first email to this list so here's a short introduction :) I am a free-software and open-education volunteer mainly working on the XSCE (short for School Server Community Edition) project. I've volunteered for the OLPC project

Hello Everyone, my first message to this list so please be gentle :) I'm the CCO for Ethereum. If you're not 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

sense. There are a lot of other useful tools that we may use, like ArkOS on the raspberry's the Serval project for free messages and call's inside a city by using a hybrid "android access point". And many, many more that are here on your site. Eventually

FireChat, an iPhone app that does mesh network messaging, had an article in the Economist this month (can't find it to link to, and paywalled anyway). It seems to be one app of a thing called OpenGarden, which is a meshnetwork thingy for iPhones: http://opengarden.com/faq#faq-general-001 The Economist

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List! I gave a talk about politics and peer-to-peer at this week's EuroPython conference in Berlin. https://www.youtube.com/watch?v=xxSKmecZ09E As always, comments, suggestions and critique most welcome! All the best, Nicholas. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! I run this meetup [0] since 6 months now, and I'd like to do a blog (that might be translated in portuguese also) I was thinking to join your effort, and maybe publish from your platform? What do you think? Would

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm heading up to London next week for the FLOSS4P2P unconference and I'm wondering if there is any one else heading there? P.S. why is this news group so quiet? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU+5/fAAoJENbYHrR5e4vCzv4QAIukbTW5VHHov2U2SlXAqEbz CL+lcy1xv049yx79OJtLAIHzwN9L1gKa7gr0ixuA1cIG5RMUbJdHY+BiBYi3iHs5

other people run similar sessions on the other tools people most want (see survey on Redecentralize.org homepage) eg on state of instant messaging alternatives.    Francis    On Thu, 15 Oct 2015, at 06:25 PM, will.sch wrote

area, sounds super interesting! Jer On Apr 25, 2014, at 7:50 AM, Stephan Tual < stephan@ethereum.org > wrote: Hello Everyone, my first message to this list so please be gentle :) I'm the CCO for Ethereum. If you're not familiar with this project, here's a quick summary

sense. There are a lot of other useful tools that we may use, like ArkOS on the raspberry's the Serval project for free messages and call's inside a city by using a hybrid "android access point". And many, many more that are here on your site. Eventually

sense. There are a lot of other useful tools that we may use, like ArkOS on the raspberry's the Serval project for free messages and call's inside a city by using a hybrid "android access point". And many, many more that are here on your site. Eventually

Steve On Mon, Jun 2, 2014 at 1:04 AM, Francis Irving < francis@flourish.org > wrote: FireChat, an iPhone app that does mesh network messaging, had an article in the Economist this month (can't find it to link to, and paywalled anyway). It seems

Steve On Mon, Jun 2, 2014 at 1:04 AM, Francis Irving < francis@flourish.org > wrote: FireChat, an iPhone app that does mesh network messaging, had an article in the Economist this month (can't find it to link to, and paywalled anyway). It seems

Steve On Mon, Jun 2, 2014 at 1:04 AM, Francis Irving < francis@flourish.org > wrote: FireChat, an iPhone app that does mesh network messaging, had an article in the Economist this month (can't find it to link to, and paywalled anyway). It seems

Steve On Mon, Jun 2, 2014 at 1:04 AM, Francis Irving < francis@flourish.org > wrote: FireChat, an iPhone app that does mesh network messaging, had an article in the Economist this month (can't find it to link to, and paywalled anyway). It seems

Steve On Mon, Jun 2, 2014 at 1:04 AM, Francis Irving < francis@flourish.org > wrote: FireChat, an iPhone app that does mesh network messaging, had an article in the Economist this month (can't find it to link to, and paywalled anyway). It seems

port 80 is HTTP to block the people running other apps on it. Result: All the apps start actually using HTTP, now your messaging app is vulnerable to XSRF for no good reason. Meanwhile they add kitchen sink support to the HTTP protocol in order to support all of this

port 80 is HTTP to block the people running other apps on it. Result: All the apps start actually using HTTP, now your messaging app is vulnerable to XSRF for no good reason. Meanwhile they add kitchen sink support to the HTTP protocol in order to support all of this

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Adam, This is a great post. I share your frustration with the difficulty of building decentralised systems that are usable, efficient and secure. But I have some doubts about your argument. I don't think the Tsitsiklis/Xu paper tells us anything about centralisation

first 5 minutes so rewatching now :) Great talk. On 25 July 2014 10:32, Nicholas H.Tollervey < ntoll@ntoll.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List! I gave a talk about politics and peer-to-peer at this week's EuroPython conference in Berlin. https://www.youtube.com/watch?v=xxSKmecZ09E

first 5 minutes so rewatching now :) Great talk. On 25 July 2014 10:32, Nicholas H.Tollervey < ntoll@ntoll.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List! I gave a talk about politics and peer-to-peer at this week's EuroPython conference in Berlin. https://www.youtube.com/watch?v=xxSKmecZ09E

first 5 minutes so rewatching now :) Great talk. On 25 July 2014 10:32, Nicholas H.Tollervey < ntoll@ntoll.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List! I gave a talk about politics and peer-to-peer at this week's EuroPython conference in Berlin. https://www.youtube.com/watch?v=xxSKmecZ09E

first 5 minutes so rewatching now :) Great talk. On 25 July 2014 10:32, Nicholas H.Tollervey < ntoll@ntoll.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List! I gave a talk about politics and peer-to-peer at this week's EuroPython conference in Berlin. The Return

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/08/14 00:07, Adam Ierymenko wrote: > I just started a personal blog, and my first post includes some > thoughts I've wanted to get down for a while: > > http://adamierymenko.com/decentralization-i-want-to-believe/ > Bravo Adam, You have succinctly put into

join.  Anybody can participate.  With Askemos you get close-join.  Like WhatsApp: the owner needs to accept the other party before messages are taken. Actually I'm currently gathering more info towards a fair comparison.  Comments welcome: http://ball.askemos.org/?_v=wiki&_id=1786

Sorry, this was supposed to be a private message. (But hitting "reply" instead of "reply to list" sends it to the list anyways.) One more question: am I correct to understand that zerotier serves essentially the same purpose as cjdns? https://github.com/cjdelisle/cjdns Thanks

Wittenberger < Joerg.Wittenberger@softeyes.net > wrote: Sorry, this was supposed to be a private message. (But hitting "reply" instead of "reply to list" sends it to the list anyways.) One more question: am I correct to understand that zerotier serves essentially the same purpose as cjdns? https://github.com/cjdelisle/cjdns Thanks

Wittenberger < Joerg.Wittenberge r@softeyes.net > wrote: Sorry, this was supposed to be a private message. (But hitting "reply" instead of "reply to list" sends it to the list anyways.) One more question: am I correct to understand that zerotier serves essentially the same purpose as cjdns? https://github.com/cjdelisle/cjdns Thanks

Wittenberger < Joerg.Wittenberge r@softeyes.net > wrote: Sorry, this was supposed to be a private message. (But hitting "reply" instead of "reply to list" sends it to the list anyways.) One more question: am I correct to understand that zerotier serves essentially the same purpose as cjdns? https://github.com/cjdelisle/cjdns Thanks

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/08/14 13:56, Jörg F. Wittenberger wrote: > Nicholas: does Drogulus have an idea about contracts? Should I include > it in the comparison or does it not qualify? I'm not sure. See here: > http://ball.askemos.org/?_v=wiki&_id=1786

away. If the large majority of the nodes are Sybils that's where the inefficiency comes from. You would essentially have to broadcast the message in order to find a path that contains no Sybils. Trust should be able to solve the problem by making available several "trusted" paths only

agents (be them accounts >> representing human users or automated, autonomous processes) >> communicating via asynchronous, unreliable, unidirectional >> messages. That's how we observe human interaction in writing. >> Humans or juristic persons sending letters, registered mail etc. >> > Again, quite. Actually

Without that it's just self-signed certificates. By contrast, broadcasting could theoretically solve the availability problem for everyone. If anyone can broadcast a message and have it be received by everyone else then you've essentially solved the problem. The trouble is the efficiency. That's just the nature

take the human intent out of the game.  (In our model, agents representing users may be free send arbitrary messages.  Akin to no regulation and freedom of expression.) I can use software to break the law, and I can use the law to break software

this seems to replicate data.  Does it protect against malicious updates too? It creates a verifiable log only -- the content of the messages is an application concern. We're looking at CRDTs to deal with convergence, but the systemic model for security is the reputation system

here: this seems to replicate data.  Does it protect against malicious updates too? It creates a verifiable log only -- the content of the messages is an application concern. We're looking at CRDTs to deal with convergence, but the systemic model for security is the reputation system. CRDT = "Cambodian

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 06/09/14 19:23, P S wrote: > Has anyone used Tribler or reviewed the protocols and technical > papers? > > https://github.com/Tribler/tribler/wiki I'm a part-time member of the research group that produces Tribler - I don't work on Tribler

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 19/08/14 20:52, Adam Ierymenko wrote: > Getting to this a bit belatedly… :) Likewise. :-) > If you’ve been reading the other thread, we’re talking a lot about > trust and I’m starting to agree with David

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 20/10/14 00:59, Dominic Tarr wrote: > hello redecentralizers > > If you happen to be handy to Paris in mid-december, then you may be > interested in attending squatconf, or speaking there! > November the 15th according to the site. Unfortunately

being organized in #squatconf on freenode On Mon, Oct 20, 2014 at 10:53 AM, Nicholas H.Tollervey < ntoll@ntoll.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 20/10/14 00:59, Dominic Tarr wrote: > hello redecentralizers > > If you happen to be handy to Paris in mid-december

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 That's what I did! http://redecentralize.org/interviews/2013/07/15/01-ntoll-drogulus.html (them interviewing me) and... http://redecentralize.org/about/ (me interviewing them) I think this is a great idea. :-) N. On 01/12/14 10:23, Steve Phillips wrote: > /"Everyone’s time is valuable, and often

other words, you're AMAZING. Thanks!!! -- nando 2014-12-01 12:10 GMT+01:00, Nicholas H.Tollervey <ntoll@ntoll.org>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > That's what I did! > > http://redecentralize.org/interviews/2013/07/15/01-ntoll-drogulus.html > (them interviewing

other words, you're AMAZING. Thanks!!! -- nando 2014-12-01 12:10 GMT+01:00, Nicholas H.Tollervey < ntoll@ntoll.org >: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > That's what I did! > > http://redecentralize.org/interviews/2013/07/15/01-ntoll-drogulus.html > (them interviewing

sake of simplicity. See you there ! Le 08/03/2015 02:03, Nick B-T a écrit : -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm heading up to London next week for the FLOSS4P2P unconference and I'm wondering if there is any one else heading there

BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/17/2015 09:52 AM, Anish Mangal wrote: > > I believe the problem has atleast two aspects - educating people and > engaging them in conversation which was the thing I had in mind when I > shared this email, and second, the larger

crit : > How is "redecentralization" compatible with proprietary software at all? It is not. I think this is the first message of this kind received on the list. > In the interview, I had understood that the project was about "open > source" solutions. Now, open

BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/02/2015 09:06 AM, Julien Rabier wrote: > > I think you're in the right place, people trying to sell proprietary > stuff are not. > > Welcome here hellekin ! > > taziden > Hey taziden! Glad to see you here

BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/14/2015 08:32 AM, Benjamin Heitmann wrote: > > are there any updates on the date and format of the un-conference? > I already have a train going to London on the 16th and leaving on the 19th. So I hope

BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/16/2015 02:14 PM, Jos Poortvliet wrote: > Hi, > > Now the ownCloud Conf is over I'm trying to wrap things up. There was one > announcement I think you folk find interesting: https://owncloud.org/c onnect/ > They use Pagekite

blame faulty text completion/correction for any rudeness! On Sep 16, 2015 9:16 PM, "hellekin" < hellekin@gnu.org > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 09/16/2015 02:14 PM, Jos Poortvliet wrote: > > Hi, > > > > Now the ownCloud Conf

BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/17/2015 03:09 AM, Jos Poortvliet wrote: > > Oh, that is an interesting point, yes. And with the .onion > domain, one can be reached from the 'normal' web, too? > 'Normal' Web users only use DNS to resolve their names

other people run similar sessions on the other tools > people most want (see survey on Redecentralize.org homepage) eg on state > of instant messaging alternatives. > > Francis > > On Thu, 15 Oct 2015, at 06:25 PM, will.sch wrote

spaces which will have various things going on. If people want use Periscope as well I think it's a good idea. Will -------- Original Message -------- Subject: Re: [redecentralize] Webcasts / Periscope Time (UTC): October 16 2015 4:21 pm From: joakimstai@gmail.com To: redecentralize@librelist.com +1, I'd be very grateful

want me to have it done (only a mailing list, no fancy stuff!). And sorry if I have hurt someone with my previous message, but yeah, I don't like Google. I know that it's difficult to live without them but at least concerning the mailing list

bulk of the internet, so it would be very interesting to see more on decentralized self-publishing platforms. For personal use, cross-platform secure/private/anon messaging and calls would be fantastic

pairspace@gmail.com > wrote: For those who haven't seen the now-dormant list, it was active in early part of the 00 decade. 7000+ messages on P2P and decentralization:     http://groups.yahoo.com/neo/groups/decentralization/conversations/messages -- konklone.com | @konklone

nowhere... But note the usability requirement! Which very few things pass. Alas, not even Signal - in my experience it doesn't reliably deliver messages. Francis

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A Pythonista buddy Tarek has written about de-Googling / de-Facebooking his life (he's works for Mozilla): http://ziade.org/2013/06/24/shutting-down-facebook-amp-google/ Maybe some interesting stuff in there... N. On 09/12/13 13:22, Francis Irving wrote: > Whats the list of services you're using

thought and analysis from rather hand-wavy philosophical problems to some of the concrete technical work we've been doing on FriendSecure (the message passing system) and the drogulus (the universal DHT). You say you want to hear about what we can do: How about thinking carefully and deeply about

pairspace@gmail.com > wrote: For those who haven't seen the now-dormant list, it was active in early part of the 00 decade. 7000+ messages on P2P and decentralization:     http://groups.yahoo.com/neo/groups/decentralization/conversations/messages -- konklone.com | @konklone

pairspace@gmail.com > wrote: For those who haven't seen the now-dormant list, it was active in early part of the 00 decade. 7000+ messages on P2P and decentralization:     http://groups.yahoo.com/neo/groups/decentralization/conversations/messages -- konklone.com | @konklone -- konklone.com | @konklone

anyone is arround, ping me ! Benjamin ANDRE - +33 (0)6 86 25 36 66 - Cozy.io 2013/12/15 Nicholas H.Tollervey < ntoll@ntoll.org > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone known any friendly Icelanders who may like to help..? N. On 14/12/13 22:18, Ira wrote: > Wooo conference in Iceland

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I can write something for a blog post - probably about the p4p2p work done at the sprint in Germany in November (see http://p4p2p.net/). It'd be good to know who's writing what so we avoid collisions of subject matter

January would be fine). Decentralizly :-) Benjamin ANDRE - +33 (0)6 86 25 36 66 - Cozy.io 2013/12/18 Nicholas H.Tollervey < ntoll@ntoll.org > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I can write something for a blog post - probably about the p4p2p work done at the sprint in Germany in November

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone known any friendly Icelanders who may like to help..? N. On 14/12/13 22:18, Ira wrote: > Wooo conference in Iceland! I can't wait ;) > > > On 10 December 2013 08:45, Ross Jones <ross@servercode.co.uk > <mailto:ross@servercode.co.uk

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello everyone! My name is Jacob Cook, you may know me from the interview I did with Irina for Redecentralize.org. I work on arkOS, the free and open source self-hosting server platform. (that's a mouthful :D) Geared toward easily managing/hosting your websites

Francis Irving <francis@flourish.org>wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Wow, that's a pretty hardcore diagram! > > > > Any key projects on it that are missing from this list? > > https://github.com/redecentralize/alternative-internet

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 It certainly sounds like an interesting proposition. I've been holding off because Docker hasn't yet been reliably working on the Pi, but it sounds like it is getting better all the time and should be considered "stable" fairly soon

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 18/12/13 08:52, Nicholas H.Tollervey wrote: > Since no one else has mentioned it on this list, snaffle up a ticket here: > > https://www.eventbrite.co.uk/e/redecentralize-january-london-meetup-registration-9841361778 > > N. > Yeah, I thought this stuff would be advertised on the newsletter list

anyone is arround, ping me ! Benjamin ANDRE - +33 (0)6 86 25 36 66 - Cozy.io 2013/12/15 Nicholas H.Tollervey < ntoll@ntoll.org > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone known any friendly Icelanders who may like to help..? N. On 14/12/13 22:18, Ira wrote: > Wooo conference in Iceland

anyone is arround, ping me ! Benjamin ANDRE - +33 (0)6 86 25 36 66 - Cozy.io 2013/12/15 Nicholas H.Tollervey < ntoll@ntoll.org > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone known any friendly Icelanders who may like to help..? N. On 14/12/13 22:18, Ira wrote: > Wooo conference in Iceland

anyone is arround, ping me ! Benjamin ANDRE - +33 (0)6 86 25 36 66 - Cozy.io 2013/12/15 Nicholas H.Tollervey < ntoll@ntoll.org > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone known any friendly Icelanders who may like to help..? N. On 14/12/13 22:18, Ira wrote: > Wooo conference in Iceland

anyone is arround, ping me ! Benjamin ANDRE - +33 (0)6 86 25 36 66 - Cozy.io 2013/12/15 Nicholas H.Tollervey < ntoll@ntoll.org > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone known any friendly Icelanders who may like to help..? N. On 14/12/13 22:18, Ira wrote: > Wooo conference in Iceland

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/01/14 10:14, Ross Jones wrote: > For the benefit of those of us that couldn’t make it, but might be > interested in events in Germany … could you elucidate? > Yes. At last year's Europython Holger Krekel

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wow, that's a pretty hardcore diagram! Any key projects on it that are missing from this list? https://github.com/redecentralize/alternative-internet Francis On Sun, Dec 29, 2013 at 06:08:24PM +0000, Benjamin Heitmann wrote: > Hello there, > > I found this

other approaches.  Scott On Sun, Dec 29, 2013 at 2:24 PM, Jacob Cook < jacob@jcook.cc > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello everyone! My name is Jacob Cook, you may know me from the interview I did with Irina for Redecentralize.org. I work on arkOS

hard to ignore. Any counter thoughts? On Sun, Dec 29, 2013 at 7:49 PM, Francis Irving < francis@flourish.org > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wow, that's a pretty hardcore diagram! Any key projects on it that are missing from this list? https://github.com/redecentralize/alternative-internet Francis

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Tim, I can't make it to January's meetup, but it should be straightforward to convert a fingerprint into a QR code using the ZXing library, and then to extend that into a basic PGP fingerprint exchange app. http://stackoverflow.com/a/5505053

Francis Irving < francis@flourish.org >wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Wow, that's a pretty hardcore diagram! > > > > Any key projects on it that are missing from this list? > > https://github.com/redecentralize/alternative-internet

those who haven't seen the now-dormant list, it was active in early part of the 00 decade. > > 7000+ messages on P2P and decentralization: > > http://groups.yahoo.com/neo/groups/decentralization/conversations/messages > > > -- Do *you* have an awesome idea you never quite manage to do? http://www.awesomefoundation.org/en/chapters/liverpool/

those who haven't seen the now-dormant list, it was active in early part of the 00 decade. > > 7000+ messages on P2P and decentralization: > >     http://groups.yahoo.com/neo/groups/decentralization/conversations/messages > > > -- Do *you* have an awesome idea you never quite manage

those who haven't seen the now-dormant list, it was active in early part of the 00 decade. >> >> 7000+ messages on P2P and decentralization: >> >> http://groups.yahoo.com/neo/groups/decentralization/conversations/messages > > -- > Do *you* have an awesome idea you never quite manage

haven't seen the now-dormant list, it was active in early part of the 00 decade. > >> > >> 7000+ messages on P2P and decentralization: > >> > >> http://groups.yahoo.com/neo/groups/decentralization/conversations/messages > > > > -- > > Do *you* have an awesome idea

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 and to be easy to use, Avatar is implemented via JavaScript

BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, o Scott Jenson on 12/30/2013 04:26 AM: > Hello, > > I'm Scott Jenson. I'm on a quest to unleash the web from the URL > bar. I want any smart device to be able to broadcast

than the official install process. -- Eric On Thu, Jan 2, 2014 at 7:00 PM, Jacob Cook < jacob@jcook.cc > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 It certainly sounds like an interesting proposition. I've been holding off because Docker hasn't yet been reliably working

Anish, welcome to the list :) On Wed, 2 Sep 2015 at 17:32 Anish Mangal < anishmg@umich.edu > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, This is my first email to this list so here's a short introduction :) I am a free-software and open-education volunteer

than the official install process. -- Eric On Thu, Jan 2, 2014 at 7:00 PM, Jacob Cook < jacob@jcook.cc > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 It certainly sounds like an interesting proposition. I've been holding off because Docker hasn't yet been reliably working

Germany … could you elucidate? Thanks Ross On 8 Jan 2014, at 10:12, Nicholas H.Tollervey <ntoll@ntoll.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > Well, that was fun. > > Irina talked about possible sponsorship and alternative locations

working :) Jer > On Jan 8, 2014, at 3:49 AM, "Nicholas H.Tollervey" <ntoll@ntoll.org> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> On 08/01/14 10:14, Ross Jones wrote: >> For the benefit of those of us that couldn

BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi JC, Thanks for introducing yourself! I'm very pleased to hear about your XMPP webchat client. Does it have a standalone version, or does it need to be integrated into one of the cited frameworks? I would be happy to integrate a standalone

centralized hosting removed optionality. Agree/disagree? On Tue, Jan 14, 2014 at 9:16 AM, Jacob Cook < jacob@peakwinter.net > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi JC, Thanks for introducing yourself! I'm very pleased to hear about your XMPP webchat client. Does it have a standalone version

Steve On Mon, Jun 2, 2014 at 1:04 AM, Francis Irving < francis@flourish.org > wrote: FireChat, an iPhone app that does mesh network messaging, had an article in the Economist this month (can't find it to link to, and paywalled anyway). It seems