3 ms·

The claim you make (that the speed of light) is the main limiting factor is incredibly undersubstantiated. Firstly, it is incredibly likely that the same query

The claim you make (that the speed of light) is the main limiting factor is incredibly undersubstantiated. Firstly, it is incredibly likely that the same query within you tube is handled by as many computers as it would have been in your DHT. The difference between youtube and your DHT is that youtube doesn't need to do constant connection re-establishment. In a DHT -- especially one used for short-lived queries such as these -- the establishing of short connections can add a lot of overhead. This is a challenge mainly because of the protocol stocks in common usage on the network, not really a property of distributed systems in and of themselves.

jasode 8y ago
>same query within you tube is handled by as many computers as it would have been in your DHT. For the poster I responded to, and the topic of this thread (Peertube), decentralized means WAN (wide area network) and not LAN (local area network). (I noticed you substituted "decentralized" with "distributed" which muddies up the discussion. The poster asking the question and my response used "decentralized".) >because of the protocol stocks[sic] in common usage on the network, not really a property of distributed systems in and of themselves. The overhead of network latency and multiple round trips is absolutely a property of decentralized systems. It's technically impossible to invent a protocol that can query thousands of home-based nodes to return a result that's as fast as a centralized system such as Youtube. For the purposes of this particular thread, the "distributed network" means something like PeerTube with home nodes over ISP networks. We're not talking about the "distributed network" of 10,000 computers within Google and Facebook datacenters. [To downvoters, please point out the technical flaw or show a protocol stack that removes ISP latency and round trips that makes it equivalent network performance to Youtube as tathougies suggests.]
- posting2fast 8y ago
  > It's technically impossible to invent a protocol that can query thousands of home-based nodes to return a result that's as fast as a centralized system such as Youtube. Yeah, but it's possible to crawl and cache all metadata, everything except the actual video and audio, centrally, and search it from there. Sure, that means you can't find a video 5 seconds after it was uploaded, but for practical purposes, it's not hard to imagine a bunch of solutions that would be good enough, especially considering search isn't that great on YT to begin with. Why can't I search among subscribed channels and filter and order by 20 criteria? Because search on YouTube isn't that good, it's not even trying to be, just like on Facebook for example. Being quick at doing something crummy is still kinda crummy.

jasode 8y ago

>same query within you tube is handled by as many computers as it would have been in your DHT. For the poster I responded to, and the topic of this thread (Peertube), decentralized means WAN (wide area network) and not LAN (local area network). (I noticed you substituted "decentralized" with "distributed" which muddies up the discussion. The poster asking the question and my response used "decentralized".) >because of the protocol stocks[sic] in common usage on the network, not really a property of distributed systems in and of themselves. The overhead of network latency and multiple round trips is absolutely a property of decentralized systems. It's technically impossible to invent a protocol that can query thousands of home-based nodes to return a result that's as fast as a centralized system such as Youtube. For the purposes of this particular thread, the "distributed network" means something like PeerTube with home nodes over ISP networks. We're not talking about the "distributed network" of 10,000 computers within Google and Facebook datacenters. [To downvoters, please point out the technical flaw or show a protocol stack that removes ISP latency and round trips that makes it equivalent network performance to Youtube as tathougies suggests.]

posting2fast 8y ago
> It's technically impossible to invent a protocol that can query thousands of home-based nodes to return a result that's as fast as a centralized system such as Youtube. Yeah, but it's possible to crawl and cache all metadata, everything except the actual video and audio, centrally, and search it from there. Sure, that means you can't find a video 5 seconds after it was uploaded, but for practical purposes, it's not hard to imagine a bunch of solutions that would be good enough, especially considering search isn't that great on YT to begin with. Why can't I search among subscribed channels and filter and order by 20 criteria? Because search on YouTube isn't that good, it's not even trying to be, just like on Facebook for example. Being quick at doing something crummy is still kinda crummy.