10 ms·
Peer-to-peer technologies not only make Skype obsolete, but also make it much harder to spy on people. By the way, use WebRTC or some completely peer-based vid
by ilaksh 13y ago
Peer-to-peer technologies not only make Skype obsolete, but also make it much harder to spy on people.
By the way, use WebRTC or some completely peer-based video conferencing (WebRTC still uses central servers to establish connections). Don't use Skype. Doesn't make any sense from a technology standpoint or from a privacy standpoint or anything.
I am actually amazed by how little discussion there is on Hacker News and reddit about peer-to-peer technologies for things like video conferencing, publishing and realtime data collaboration.
This whole NSA thing should be enough to push things like named data networking/content centric networking, WebRTC and meshnets (http://www.reddit.com/r/darknetplan http://www.reddit.com/r/darknetplan) into the mainstream.
I believe that we are going to move away from a lot of traditional ways of doing things pretty soon. For one, obviously centralized servers have to go. Replace that with encrypted, privacy-focused data oriented networking.
Replace centralized internet backbones with wifi meshnets, private laser systems, even private fiber networks, etc.
Its very nice to have a simple programming language and API available with things like Webkit and Mozilla browsers, but that still puts too much power in the hands of a few companies, and locks us into particular implementations, and also traps us within the browser.
Programmers and businesses do need easy-to-use, cross-platform and cross-device APIs and programming languages. I think we can port a lot of the Web APIs to a language-neutral, binary-neutral, implementation-neutral semantic representation. Dump as much of the unnecessary complexity from Web APIs as possible.
Take a look at what HTML/SVG etc. provide and re-engineer a more general purpose solution for representing all kinds of things _including_ software source code that is based on truly semantic representation inspired by description logics which separates presentation from display/editing.
- randallu 13y ago> WebRTC still uses central servers to establish connections WebRTC without a signalling server: http://blog.printf.net/articles/2013/05/17/webrtc-without-a-signaling-server/ http://blog.printf.net/articles/2013/05/17/webrtc-without-a-...
- brianchu 13y agoThat is not even close to a solution. Then problem of establishing a connection (sharing connection info with both parties) remains in its entirety. The user still has to manually give the other user signaling information. The suggestion given is instant messaging chat (which requires a server). Not to mention that a STUN server is still needed for NAT traversal, as the author acknowledges.
- jnbiche 13y agoWhat do you think about http://openpeer.org/ http://openpeer.org/ as a possible solution to the signaling problem?
- burntsushi 13y ago> This whole NSA thing should be enough to push things like named data networking/content centric networking You're damn right. It wasn't even a few days after this whole thing broke that I started working on a simple, distributed and automatic file synchronization program. No third parties and open source. I was absolutely stunned to find out that nothing out there meets those criteria (despite my best efforts). The only thing that was close was git-annex assistant, but I don't want to use git for simple file synchronization (particularly for large files). There's also Bittorrent Sync, but it's completely locked down. :-/
- pwnna 13y agoThis is all good but the biggest thing right now is that there is no coordinated effort to build a system that's easy to use, secure, and open source. Everyone can spend their time working on their own solution but no one would use it as everyone's work will be incompatible with each other. This means no one (or rather, not enough people) will use any solutions that are developed and revert back to something like Skype, FB message, etc. I think what we need is to establish a foundation that coordinates the development efforts for these secure and reliable software packages with a few centralized projects that become a standard (here's hope for WebRTC).
- Fixnum 13y agoOut of curiosity, what's wrong with Unison?
- burntsushi 13y agoThat's what I use now. But it's not automatic and is designed for use between two end points. I want it to be automatic across N end points. (And I intend to use a bittorrent-like protocol to achieve that, rather than an rsync-like protocol that unison uses.) [EDIT] I forgot one of my most frustrating nits with unison: you need to have the same version on both ends. It's solvable by building the right version yourself, but it's damn annoying.
- erikpukinskis 13y ago
- nemothekid 13y ago>I believe that we are going to move away from a lot of traditional ways of doing things pretty soon. For one, obviously centralized servers have to go This is a pretty bold statement, and I'd like to hear your reasoning for it. I've always seen that centralized is better than decenteralized, just because its easier. Which is why when we see github go down, some teams can't continue to work even though git itself is decentralized. One click solutions, and decentralized applications tend to not go hand in hand. I'll agree, if we want to maintain privacy these things will have to be decentralized. However I have a hard time making the case that decentralization will become the defacto standard. Even the web has a psuedo-central hub - DNS.
- krichman 13y agoI would say centralised is easier but usually worse instead of better. Most people use some centralised middleman out of convenience. Decentralisation is universally better IMO because there is no single point of failure and no choke point to nickel-and-dime users to death. > some teams can't continue to work even though git is decentralized. I think you mean some teams won't continue to work because they don't know how to use git. If the de facto center goes down, a team is still able to use git to share changes with each other. And IPv4/6 is decentralised, DNS makes it convenient for regular people to use. I would say DNS is decentralised as well, just the allocation of domain names comes from a few sources.
- parsnips 13y agoA nitpick, but decentralized & distributed systems do not guarantee "no single point of failure". For example, Skype switched from pure p2p because of a software bug which affected the whole network (ie the client software was the single point of failure)...
- flyinRyan 13y agoThat's not true. The whole network was effected because the centralization point they chose had a client bug and since the whole network had to use these nodes it took them down. To take down a decentralized network with a bug you'd have to have every user on the exact same version and no way for them to simply role back to the previous version. I.e. nearly impossible.
- Locke1689 13y agoThis whole NSA thing should be enough to push things like named data networking/content centric networking, WebRTC and meshnets (http://www.reddit.com/r/darknetplan http://www.reddit.com/r/darknetplan) into the mainstream. I've tried multiple times to engage on this topic. From my experience, the people set of people who are interested in these topics for "freedom" reasons and the set of people who are technically informed enough to contribute even minimally to technical discussions are non-overlapping.
- wavefunction 13y agoDon't be so sure. In the great game there must be gambits and feints, misdirections and intentional losses. Some things are better left unsaid in public places with many ears. Certainly not speaking about myself, but that's the sense I get from talking to people whose interests overlap like you'd hope.
- chris_mahan 13y agoReminds me of this: http://www.paulgraham.com/say.html http://www.paulgraham.com/say.html
- Locke1689 13y agoYeah, this is mostly bullshit. The people who hide away are the same as the people who want you to sign an NDA before they talk about their startup because it's just too revolutionary and cranks who invent new crypto algorithms in their basement. DS design is extremely complex and requires the coordinated effort of a lot of really smart people to get right. Anyone building these systems in secret just has no idea how terrible they are at it.
- stephengillie 13y agoThe people I talk with about this, who also have the technical acumen to build these things, or those with the political connections to drive change, are both groups of people who have known this level of spying has been going on through their lifetimes, and are unconcerned. The response on HN has been an order of magnitude larger than the response from any person I know. Of everyone I know, I'm more concerned about the NSA spying than anyone else, and I'm less concerned than most commenters. I begin to wonder if this isn't some kind of nerd-sniping paranoia-groupthink.
- nano111 13y agoeverything still goes through your ISP when using peer to peer... but yes to encryption.
- igravious 13y agoSome entity (or service) has to provide your internet access. So perhaps you are always going to need an ISP to some extent. Or you are thinking mesh? Maybe in the future ISPs will compete on privacy issues and concerns in addition to how they compete now: bandwidth and cost. Maybe we'll have municipal WiFi, maybe we'll have mesh. We should work towards a mix of mesh and muni as well as a more privacy-focused ISP model. One can dream :)
- pfraze 13y agoCheck out http://blog.grimwire.com/#2013-04-04-grimwire.md http://blog.grimwire.com/#2013-04-04-grimwire.md
- lnanek2 13y agoI have a friend who is really into WebRTC, and help him with debugging sometimes. Honestly, I've never found a network I use often that it works on. Doesn't work on my AT&T LTE except for presence. Doesn't work at all on my work internet. Video doesn't work on my work guest internet outside our firewall. Doesn't work from my hotel internet. I haven't tried at home, but I'm only home a couple weekends a month, so that's useless anyway. WebRTC depends on things non-home internet filters out or prevents, so it is useless. The way to get around that? Use central servers and make your traffic look like HTTP. Heck, even STUN protocols admit there are cases where it won't work, but WebRTC fans seem to think they'll always be able to get a P2P connection. The technology is just naive as far as I'm concerned. Something that only works on home internet and a few open networks is worthless.
- rdl 13y agoSure, but as long as there's federation or something like it, you get to pick your choice of a server (including running your own). That's good enough for me.
- jokoon 13y agoThose techs are not taking off because there are no standards.
- nkoren 13y ago> This whole NSA thing should be enough to push things like named data networking/content centric networking, WebRTC and meshnets (http://www.reddit.com/r/darknetplan http://www.reddit.com/r/darknetplan) into the mainstream. Mozilla is looking at making a foray into this with its "Firecloud" initiative[1]. While Firecloud itself appears to be a relatively innocuous endeavour, it would lay the infrastructure for P2P RTC-based meshnets, which are something I've been hoping to see for a while now. 1: http://literaci.es/firecloud http://literaci.es/firecloud
- seclorum 13y ago>>>>Its very nice to have a simple programming language and API available with things like Webkit and Mozilla browsers, but that still puts too much power in the hands of a few companies, and locks us into particular implementations, and also traps us within the browser. Programmers and businesses do need easy-to-use, cross-platform and cross-device APIs and programming languages. I think we can port a lot of the Web APIs to a language-neutral, binary-neutral, implementation-neutral semantic representation. Dump as much of the unnecessary complexity from Web APIs as possible. Well, this is exactly why I am a huge fan of technologies like MOAI (http://getmoai.com/ http://getmoai.com/) where the VM is under the control of the implementor, whose efforts to put the working VM on Platform-[X] results in a single codebase that will run on all Platform[s]. In my opinion, it pretty much matches your requirements, from the simple language, easy to use API, and more importantly: control over the host environment. The only issue is that competence in MOAI in developing a cross-platform truly 100% compatible code base means you have to scale your attention from the up-front App, down to the lower-level host code. Or else. But thats 100% of the fun, imho .. Note that this is just one of many such solutions to the issues you describe, and it is indeed a fertile playground for anyone with as much affinity for Lua - and similar tools - as one must have, to suffer the platform wars pleasantly, these days ..
- dhimes 13y agoBear in mind that there are at least five spying programs going on. One is server-based (PRISM), but the others (FAIRVIEW, BLARNEY, and two others whose names were redacted) apparently monitor the pipes. This isn't so much of a technical problem as a political one. Although, in principle I agree- I would much rather have p2p so I could at least have a fighting chance via encryption.
- pthatcherg 13y agoWhy do you think WebRTC puts too much power in the hands of a few companies? It's completely open source and can do everything you want. You can take all the source code from either webrtc.org or chromium.org and use it to build your own end-to-end full encrypted communication system that no one can hack (as far as we know, and assuming you have secure device and OS). The implementation at webrtc.org gives you cross-platform, cross-device source code in C++. You can build any API on top of that, in any language you want. It's already really easy to use if you an to use the HTML5 WebRTC API built into Chrome (and the same API in Firefox). It seems to me that you have everything you want, or at least all the pieces of the puzzle. Someone just needs to do the work of assembling them the way you want them, and then of convincing the people with whom you want to talk (your friends, family, or business associates) to use your securely built communication system. Technology-wise it's possible, even fairly easy if you know what you want. But the social aspect (convincing others to use it) is more difficult. (Full Disclosure: I work at Google, and I have worked both on Hangouts and WebRTC)
- ilaksh 13y agoI'm actually really excited about WebRTC and have a project using it. I was talking more generally about Web browsers and web APIs, not specifically WebRTC. I still see the web platform as currently the most open, practical solution we have. However, the reality is that Google IS still a business. And so quite a lot of this key infrastructure, although it is open source, is still being packaged up by a giant private company. Yes, we can use the web platform including things like WebRTC to do what we want, but I believe the the medium and long-term future will move away from specific implementations by a few companies and towards open machine-processable specifications. I believe that the way forward will be to move away from textual programming languages and into truly semantic representations of programs, protocols, and implementations. Obviously it will be many years before this is mainstream.
- wmf 13y agoP2P is harder to build and harder to monetize than client-server, so it's like poison to startups. Crackpots are still into it, but they don't give a good appearance.
- drivebyacct2 13y ago"Crackpots"? Is this a serious, honest comment? Or is a crackpot anyone who doesn't choose and create philosophically and technically inferior products for the sake of "Just one more social network that will surely be worth millions if I can make it centralized and proprietary and non-inter-operable and get just enough users." SOUNDS GREAT. "P2P is harder to build" is an equally loaded statement, though you've caught my intrigue. I wrote a WebRTC signaling server in a weekend that is capable of letting peers establish N:N connections with each other for video conferencing. Outside of cases where TURN would have been necessary, the clients were all connected, P2P with encrypted connections. (And even with TURN, I believe end-to-end encryption could be ensured, but the traffic would go through a third party)
- wmf 13y agoSorry, I didn't take the time to sugar-coat my comment. One lesson I've taken from Web 2.0 over the last decade is that users do not care. So why should I care about them more than they care about themselves? We'll see if PRISM changes that, but I suspect it won't. WebRTC makes P2P a lot easier, especially since it doesn't require installing software. I think getting peer connectivity is 10% of the problem. Video conferencing is pretty much a best case for P2P; general apps are much harder. Things like data sync and handing churn are very complex and not needed in client-server architectures.