4 ms·
I agree with you, and I also mentioned it in another comment. We don't have to chose P2P or hosted service, when we can have both. See https://news.ycombinator.
by diggan 9y ago
I agree with you, and I also mentioned it in another comment. We don't have to chose P2P or hosted service, when we can have both. See https://news.ycombinator.com/item?id=16109202 https://news.ycombinator.com/item?id=16109202
As my full-time work is working on P2P systems, I would love to hear more about what you think gets even worse with P2P systems compare to hosted services.
Lack of client support, features and so on is more a sign of lack of adoption, rather than something fundamentally worse with P2P than hosted services.
- cortesoft 9y agoBiggest issue is connectivity issues. Corporate firewalls don't allow incoming connections, and limit outgoing connections to specific ports (in most cases). Maintaining history is also tricky in a P2P system. Can I search and view all chat history from when I am not there? A hybrid system could, but then you would still be limited by the host being online and accessible. Also just the amount of moving parts. With P2P, you can get strange issues where some people can talk to some people and not others. It can be hard to track down where those connectivity issues are. My company moved from self-hosted IRC to slack a few years ago. No one had time to maintain the system (backups, updates, troubleshooting, etc), and it was cheaper and easier to pay slack than to hire someone to maintain an IRC server, or to pull someone from their actual job to maintain it.
- Johnny555 9y agoPlus one on this -- it would be nearly impossible to make a P2P chat system work on our corporate network since we have layers of isolation between users (not to mention about a dozen small branch offices, each with their own independent office, so even if I can Slack the coworker next to me with P2P, I couldn't reach the coworker in Germany that I really need Slack for). So we either need a central chat server on our network, or we use a cloud service like Slack. We used to run Microsoft Communicator (OCS) and availability of that service was far worse than what we've seen with Slack.
- arbie 9y agoMicrosoft finally threw in the towel last year (2017) and cut off enterprise support for Office Communicator 2007 (!)
- littlestymaar 9y ago> Biggest issue is connectivity issues. Corporate firewalls don't allow incoming connections, and limit outgoing connections to specific ports (in most cases). The STUN protocol solve most of this issue[2], webRTC is working fine in the majority of enterprise network. > Maintaining history is also tricky in a P2P system. It's perfectly possible to build a distributed database, actually that's exactly what blockchains are (OK, I know , we said no blockchain but I merely use it as an example ;)). > My company moved from self-hosted IRC a few years ago. No one had time to maintain the system (backups, updates, troubleshooting, etc), and it was cheaper and easier to pay slack than to hire someone to maintain an IRC server, or to pull someone from their actual job to maintain it. This isn't p2p, p2p shouldn't be confused with self hosted. Nobody has time to set up and maintain a server of any kind, but everybody was seeding torrents in the late 2000 and nobody complained about it being too much work. [2] while the TURN protocol gives you the “hybrid system” for free (development-wise, you still need a hosting plan in that case, but it can be mutualized between all your applicative needs).
- maltalex 9y agoI'm all for P2P solutions and a more distributed Internet, but I'd like to add a few items to that list. - Security in a P2P system is harder to get right. The system is distributed and each member has to trust more parties. This significantly increases the attack surface compared with a client that just needs to trust a single server. - Not everyone is connected all the time, so network partitions happen constantly. It's hard to maintain a consistent state such as a chat log, not to mention anything more real-timey like the state of some real-time game. - STUN and other NAT traversal techniques don't always work. NAT is horrible, creating connectivity between NATed clients is always a dice roll. - Bandwidth - A dedicated server can have a lot of upstream bandwidth (to the clients). In homes, it typical to find (in some countries at least) connections that are heavily biased towards the downstream. So a 100Mbps connection (downstream) might have a 2Mbps connection upstream. Now say you want to have an 8 people video conference call, and all of your users have a 2Mbit uplink and need to send 7 copies of their video stream... What if it's a 20 person video call? What if half of them are on mobile? - Bootstrapping - every P2P system still needs to have dedicated servers for bootstrapping. There are no pure P2P systems AFAIK. - Client versioning and patching - a lot harder in a P2P system. With a central server - you just update the server and everything works. With a network of clients, things are trickier and you run the risk of partitioning the P2P network between different client versions. - Monetization in P2P is hard(er).
- jjrh 9y ago> Biggest issue is connectivity issues. Corporate firewalls don't allow incoming connections, and limit outgoing connections to specific ports (in most cases). NAT's are the real pain for this sorta stuff and why people use stuff like skype, slack, discord, etc. When the majority of folks have IPv6 connectivity a lot of things should become much easier (at least for home users and people not behind a frustrating firewall they don't control) I'm surprised maintaining a small IRC server was that much of a time sink. User problems is understandably another story.
- sitkack 9y agoYou would have to run some servers on the inside and have a specific tunnel to a small set of servers running on the outside. Clients could see either. I don't see how this is an issue.