Redecentralize

mint.com  is going to be embedded.  Though the embedding itself is done under control of the user at the client side, correct? Yes, that's correct. For the sake of brevity, I'll respond to Askemos' A) and B) alternatives by saying, they make sense /...\ integrity of each component is maintained (which I expect is what Askemos uses VMs to ensure) then it's a similar approach. The client uses a trust hierarchy, in which the Page is most-privileged, and all Workers are given least-possible privilege. Deciding which participant is the Page /...\ 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 which follows the protocol would link to itself with `rel=" askemos.org/rel/heartbeat

really don't think of it as a VPN. A VPN is typically used to connect two networks together, or to allow a disconnected client to incorporate itself into a network. ZT1's networks are first-order entities. Think of it as being like the difference between a VNC client /...\ virtual machine. Both allow you to use a different operating system on your local desktop. The first is a client that connects you to one running somewhere else, while the second actually runs one virtually. The closest thing out there to ZT1 is probably LogMeIn Hamachi, but it's closed /...\ about the ZT1 design: Supernodes in ZeroTier One are just regular nodes running the exact same code as the regular client that are running on fast cloud providers (Digital Ocean in this case) and designated as such. In Defaults.cpp there is a hard-coded list at the moment that designates

really don't think of it as a VPN. A VPN is typically used to connect two networks together, or to allow a disconnected client to incorporate itself into a network. ZT1's networks are first-order entities. Think of it as being like the difference between a VNC client /...\ virtual machine. Both allow you to use a different operating system on your local desktop. The first is a client that connects you to one running somewhere else, while the second actually runs one virtually. The closest thing out there to ZT1 is probably LogMeIn Hamachi, but it's closed /...\ about the ZT1 design: Supernodes in ZeroTier One are just regular nodes running the exact same code as the regular client that are running on fast cloud providers (Digital Ocean in this case) and designated as such. In Defaults.cpp there is a hard-coded list at the moment that designates

possible. WebRTC does not allow you to open arbitrary TCP or UDP sockets, which is what I think you're asking. Existing torrent clients will need updating -- at least, that is the plan. Feross ✩  blog | ✎  studynotes /...\ question about this... Can WebRTC Data Channels natively speak arbitary protocols, so they can just implement the regular BitTorrent protocol? Or will existing BitTorrent clients need updating? Francis On Sun, Dec 08, 2013 at 03:31:00PM -0800, Feross Aboukhadijeh wrote: > Hey everyone! I think Redecentralize is awesome /...\ wanted to share a bit about my new project, WebTorrent< http://webtorrent.io > > . > > I'm building a browser BitTorrent client that requires no install (no > plugin/extension/etc.) and fully-interoperates with the regular BitTorrent > network. We'll use WebRTC Data Channels for peer-to-peer

This language may be useful in the marketing of decentralization.  Trustable open clients can augment first-person human decisions based on untrusted, commercial third-party inputs. http://blogs.law.harvard.edu/vrm/2014/03/19/why-we-need-first-person-technologies-on-the-net/ --- There are social influences on how we use first person technologies, of course, just as there are social influences /...\ powerful Big Data analysts that they are, you look an awful lot like a bot. The real race isn’t over the client — the glasses, watches, phones, or goggles. It’s over the  servers . It’s over the operating system. The one that understands /...\ owned by anyone. (I have a spec I started. But nobody wants it. Money, remember?) Pshhht, rendering? We’ll get new client hardware, new client software. Big whoop. I’m a lot more worried about whose EULA is going to govern  my life

pairspace@gmail.com > wrote: This language may be useful in the marketing of decentralization.  Trustable open clients can augment first-person human decisions based on untrusted, commercial third-party inputs. http://blogs.law.harvard.edu/vrm/2014/03/19/why-we-need-first-person-technologies-on-the-net/ --- There are social influences on how we use first person technologies, of course, just as there /...\ powerful Big Data analysts that they are, you look an awful lot like a bot. The real race isn’t over the client — the glasses, watches, phones, or goggles. It’s over the  servers . It’s over the operating system. The one that understands /...\ anyone. (I have a spec I started. But nobody wants it. Money, remember?) Pshhht, rendering? We’ll get new clien t hardware, new client software. Big whoop. I’m a lot more worried about whose EULA is going to govern  my life . --- -- konklone.com | @konklone

been considering doing federation similar to that. You have some node which is essentially a dedicated DHT node and a bunch of clients which use it as a gateway to access the DHT instead of participating themselves. So you have a lot of ostensibly related clients all using the same /...\ when they want to contact each other they get one hop access and no Sybil exposure. And if the gateway is down the clients can still participate in the DHT themselves so it isn't a single point of failure. Yeah, that's basically the identical idea except in your

users, all useful for tracking and showing ads which brings monetization. 2. Easy Deployment: current web technology makes it easy to control the client-side code from a server (javascript/browsers), allowing to reduce latency and to do code upgrades without manual intervention on the client side. Just /...\ interoperate easily with other software built upon others. IP and open standards like HTTP, JSON, XML, etc. are designed for heterogenous ecosystems of interoperable clients and servers. > > The idea with ZeroTier was to be, as I said in my secret RSS feed, “a complicated thing that gets

systems at the homes of friends). (And yes: it delivers it's own website from those SoCs.) Downsides: the fuse client is not stable enough to be released publicly and WebDAV is no longer widely supported on client sides. While the whole thing should itself be able /...\ Android, nobody had the resources to actually compile for it. GUI client is just under development. Same for transition to elliptic curve (using tweetnacl) based encryption instead of SSL. So it's not ready for the casual end user to simply install. Best /Jörg > > I would

question about this... Can WebRTC Data Channels natively speak arbitary protocols, so they can just implement the regular BitTorrent protocol? Or will existing BitTorrent clients need updating? Francis On Sun, Dec 08, 2013 at 03:31:00PM -0800, Feross Aboukhadijeh wrote: > Hey everyone! I think Redecentralize is awesome /...\ wanted to share a bit about my new project, WebTorrent<http://webtorrent.io> > . > > I'm building a browser BitTorrent client that requires no install (no > plugin/extension/etc.) and fully-interoperates with the regular BitTorrent > network. We'll use WebRTC Data Channels for peer-to-peer /...\ transport, so the > entire client is basically one JavaScript file. > > Since WebTorrent is web-first, it's simple for users who do not understand > .torrent files, magnet links, NAT configuration, etc. to use BitTorrent. By > making it easier, we're making it accessible

which I don't like. I need to try Seafile !  It satisfies almost all my needs, except this : " CAUTION: The client side encryption is not work currently for mobile client, web browser and the cloud file browser of the desktop client

tracking > and showing ads which brings monetization. > > 2. Easy Deployment: current web technology makes it easy to control > the client-side code from a server (javascript/browsers), > allowing to reduce latency and to do code upgrades without > manual intervention on the client side. Just

Data Black Magic  at RealtimeConf! I wanted to share a bit about my new project, WebTorrent . I'm building a browser BitTorrent client that requires no install (no plugin/extension/etc.) and fully-interoperates with the regular BitTorrent network. We'll use WebRTC Data Channels for peer-to-peer transport /...\ entire client is basically one JavaScript file. Since WebTorrent is web-first, it's simple for users who do not understand .torrent files, magnet links, NAT configuration, etc. to use BitTorrent. By making it easier, we're making it accessible to new swathes of users who were previously intimidated, confused

effects: a) no more tracking (+) b) no money from tracking (-). > 2. Easy Deployment: current web technology makes it easy to control > the client-side code from a server (javascript/browsers), > allowing to reduce latency and to do code upgrades without > manual intervention on the client side. Just

follow that closely enough to comment? > > Regarding WebRTC's MITM vulnerability, I wonder about using > http://www.w3.org/TR/WebCryptoAPI/ someday to do client certs, though > tcpacek's FUD about client-side crypto is hard to ignore. Any counter > thoughts

seems that you not have the desire or ability to run a client somewhere that is globally accessible on a 24/7 basis? That is essentially what I do now with Camlistore, but that's true; I could :-). Perhaps I should /...\ Syncthing does also does not require a 'server' per se, it seems that you you not have the desire or ability to run a client somewhere that is globally accessible on a 24/7 basis

explain Tribler quickly. Basically we have a fully decentralised Youtube, 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 /...\ Frazee <pfrazee@gmail.com> wrote: > Hey Johan, > > Can you sell us/me on Tribler a bit? Looks like it's a bittorrent client > that you're putting behind TOR, plus an over-the-local-wifi feature. The two > things I wonder: what's the merit

explain Tribler quickly. Basically we have a fully decentralised Youtube, 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 /...\ Frazee < pfrazee@gmail.com > wrote: > Hey Johan, > > Can you sell us/me on Tribler a bit? Looks like it's a bittorrent client > that you're putting behind TOR, plus an over-the-local-wifi feature. The two > things I wonder: what's the merit

about namecoin. Anybody follow that closely enough to comment? Regarding WebRTC's MITM vulnerability, I wonder about using http://www.w3.org/TR/WebCryptoAPI/ someday to do client certs, though tcpacek's FUD about client-side crypto is hard to ignore. Any counter thoughts

Michiel, WebTorrent Desktop behaves similar to other torrent clients. You need to manually add torrents to the client. We don't want to make the client automatically download popular content, or seed it, or anything like that. The user should decide what to share since the content could be unencrypted

follow that closely enough to comment? > > Regarding WebRTC's MITM vulnerability, I wonder about using > http://www.w3.org/TR/WebCryptoAPI/ someday to do client certs, though > tcpacek's FUD about client-side crypto is hard to ignore. Any counter > thoughts

Data Black Magic  at RealtimeConf! I wanted to share a bit about my new project, WebTorrent . I'm building a browser BitTorrent client that requires no install (no plugin/extension/etc.) and fully-interoperates with the regular BitTorrent network. We'll use WebRTC Data Channels for peer-to-peer transport /...\ entire client is basically one JavaScript file. Since WebTorrent is web-first, it's simple for users who do not understand .torrent files, magnet links, NAT configuration, etc. to use BitTorrent. By making it easier, we're making it accessible to new swathes of users who were previously intimidated, confused

wait on some browser vendor to implement something? A web browser is a particularly stupid piece of kit as it is only effectively a client. To control one's micro payments what you need is a peer connection service rather than a client to multiple server services

user goes to citibank.com , they'd use an in-site UI to load Mint.com's application into a Web Worker. Now contained on the client-side, Mint would be given readonly access to the financial information, and read/write access to a section of the DOM for rendering /...\ extension area" where mint.com is going to be embedded.  Though the embedding itself is done under control of the user at the client side, correct? With Askemos we'd have two alternatives: A) citibank too could be an application run in byzantine fault tolerance.  (This had pros

about the ZT1 design: Supernodes in ZeroTier One are just regular nodes running the exact same code as the regular client that are running on fast cloud providers (Digital Ocean in this case) and designated as such. In Defaults.cpp there is a hard-coded list at the moment that designates /...\ 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 in netconf-service/ in the source tree. You're free to examine it. The netconf master can be made high-availability

Tahoe-LAFS might be good enough, since at least I could access my data from everywhere, but it doesn't even have an Android client! I self-host Camlistore, but its Android client is so out of date that it doesn't work anymore (I could build one from source

Data Black Magic  at RealtimeConf! I wanted to share a bit about my new project, WebTorrent . I'm building a browser BitTorrent client that requires no install (no plugin/extension/etc.) and fully-interoperates with the regular BitTorrent network. We'll use WebRTC Data Channels for peer-to-peer transport /...\ entire client is basically one JavaScript file. Since WebTorrent is web-first, it's simple for users who do not understand .torrent files, magnet links, NAT configuration, etc. to use BitTorrent. By making it easier, we're making it accessible to new swathes of users who were previously intimidated, confused

about the ZT1 design: Supernodes in ZeroTier One are just regular nodes running the exact same code as the regular client that are running on fast cloud providers (Digital Ocean in this case) and designated as such. In Defaults.cpp there is a hard-coded list at the moment that designates /...\ 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 in netconf-service/ in the source tree. You're free to examine it. The netconf master can be made high-availability

wait on some browser vendor to implement something? A web browser is a particularly stupid piece of kit as it is only effectively a client.   To control one's micro payments what you need is a peer connection service rather than a client to multiple server services

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 /...\ proponent of > decentralization and my personal contribution is in the form of > Converse.js (http://conversejs.org). It's an XMPP based webchat > client (similar to GTalk or facebook chat) that can be integrated > into any website (preferably with single-session support). > > I've just finished

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, or does it need to be integrated into one of the cited frameworks? I would be happy to integrate /...\ proponent of > decentralization and my personal contribution is in the form of > Converse.js ( http://conversejs.org ). It's an XMPP based webchat > client (similar to GTalk or facebook chat) that can be integrated > into any website (preferably with single-session support). > > I've just finished

wait on some browser vendor to implement something? A web browser is a particularly stupid piece of kit as it is only effectively a client. To control one's micro payments what you need is a peer connection service rather than a client to multiple server services

wrote a blog post talking about progressive web maps , which might give you an idea of our objectives. The (custom element) client can be installed for your web site (if you have bower) with : "bower install web-map". There are some map services available here:  http://geogratis.gc.ca/mapml/en/ 

nice for us to be present on your site :-) It will be a good opportunity to explain our business models and present our clients and perspectives. I am sure the community will be able to provide good feedbacks, so I definitely think it is very valuable

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 Am Do, 2. Jan, 2014 um 4:41 schrieb Eric Mill <eric@konklone.com>: > Besides Bitcoin, or potentially

proponent of decentralization and my personal > contribution is in the form of Converse.js (http://conversejs.org). It's an > XMPP based webchat client (similar to GTalk or facebook chat) that can be > integrated into any website (preferably with single-session support). > > I've just finished

apps have a bottom up approach: we have a crypto protocol, let's build a UI around. That's what we saw with GPG, client cert authentication, etc. When you take a top down approach, you design the interaction of your system, then adapt cryptosystems there

protocol for semantic data interchange) wich is promoted by the startup Respect Network . We have a B2B2C business model, we have some promising clients (OVH, Orange, La Poste) and we have just finished our fund raising. => if it make sense for you do discuss about our two projects

developments. I'm working towards the P2P equivalent of the ubiquitous "blog" demo for web frameworks or "ToDo" lists for client side JS frameworks. Perhaps a simple P2P chat application. If such projects are to get traction with developers they need to be very simple

uses a centralized zero-knowledge server for tracking the IPs and open port numbers of people or devices connected to said network, which chat clients somehow query so they know where the IM should be sent. In this scenario, do you think it's possible for me to get this

user goes to citibank.com , they'd use an in-site UI to load Mint.com's application into a Web Worker. Now contained on the client-side, Mint would be given readonly access to the financial information, and read/write access to a section of the DOM for rendering

Johan, Can you sell us/me on Tribler a bit? Looks like it's a bittorrent client that you're putting behind TOR, plus an over-the-local-wifi feature. The two things I wonder: what's the merit of bittorrent as a replacement communication structure when applications don't communicate

idea of having secure Bitcoin wallet backups by doing N-of-M secret-sharing. I would like to add that the Bitcoin Armory client already seems to be able to something similar. See "Using Fragmented Backups" at the website ([2], scroll down on the page). Regards Martin

proponent of decentralization and my personal contribution is in the form of Converse.js (http://conversejs.org). It's an XMPP based webchat client (similar to GTalk or facebook chat) that can be integrated into any website (preferably with single-session support). I've just finished a blogpost on the topic

Syncthing. And ironically I'm having to run a copy on my own personal server (i.e. a central server) to be sure all my clients (on phones and laptops) can get through whatever firewalls they're behind. What are you using? Francis

protocol for semantic data interchange) wich is promoted by the startup Respect Network . We have a B2B2C business model, we have some promising clients (OVH, Orange, La Poste) and we have just finished our fund raising. => if it make sense for you do discuss about our two projects

think the tech behind it is more interesting than Bitcoin itself. It reminds me of the web. Hypertext, browsers, and the new hybrid thin client model they led to was interesting. The internet was certainly damn interesting. But pets.com and flooz? Not so much. I still need to take

think the tech behind it is more interesting than Bitcoin itself. It reminds me of the web. Hypertext, browsers, and the new hybrid thin client model they led to was interesting. The internet was certainly damn interesting. But pets.com and flooz? Not so much. Agreed. It's interesting because

interoperate easily with other software built upon others. IP and open standards like HTTP, JSON, XML, etc. are designed for heterogenous ecosystems of interoperable clients and servers. The idea with ZeroTier was to be, as I said in my secret RSS feed, “a complicated thing that gets

also has also trended in that direction. Although the web's design left the door wide open to centralisation by separating out client and server functionality which was a consequence of a design choice for broken 'hyper' links.  That simplification was pivotal and not always in a good

also has also trended in that direction. Although the web's design left the door wide open to centralisation by separating out client and server functionality which was a consequence of a design choice for broken 'hyper' links.  That simplification was pivotal and not always in a good

WebTorrent Desktop ( https://webtorrent.io/desktop ) as a torrent client, almost daily.  I also use Instant ( https://instant.io ) to send files to friends without using a centralized service, or an app you need to install like Dropbox. I've used Patchwork ( https://ssbc.github.io/patchwork/

particular use case for file sharing. So I'm not inclined to cover it. I am looking at Resilio (BTSync). Any other torrent-related clients that you recommend? ZeroTier - yes! Is there a place that says the common use cases people have for it now? Francis