shacharz

9 ms·

31.
by shacharz 10y ago
Hey, thanks we used three.js for it. We also wrote a blog post about how we built it - https://blog.peer5.com/peer5-live-network/
32.
by shacharz 10y ago
Indeed Red Swoosh was probably one of the first P2P CDN companies, the main difference from them is the underlying technology - WebRTC enabling a seamless experience for the end user. CDN is still a very expensive business to bootstrap and
33.
by shacharz 10y ago
I can't speak to Flickr's use-case specifically, but generally speaking the content delivery market is growing.
34.
by shacharz 10y ago
traffic is as localized as possible. As a general rule you can think of, if the peer is more local to you than the nearest CDN PoP you'll receive data from the peer, otherwise you'll receive data from the CDN. >Cool! Does this
35.
by shacharz 10y ago
https://news.ycombinator.com/item?id=13501923
36.
by shacharz 10y ago
Yup, we support both AES-128 for HLS and any Common Encryption based DRM, that's true because we're basically agnostic to the content it self we just deliver it more efficiently.
37.
by shacharz 10y ago
That's an interesting scenario, we didn't consider it but we can include it as well.
38.
by shacharz 10y ago
Unmetered networks - ISP benefit from more local traffic and less traffic over their peering agreements connections. Metered networks - https://news.ycombinator.com/item?id=13502790 TBH I didn't try to disable webrtc i
39.
by shacharz 10y ago
That's interesting, I know about Octoshape. But didn't know that in enterprise they actually made matters worse. The way our technology works is a bit like an 'onion' architecture. Users from the same corporation should
40.
by shacharz 10y ago
Part of WebRTC's requirements [1] is to be fair on competing TCP connections. This is a very good point, because I agree with you that in general parallel connections cause each connection to have less throughput, but if those connecti
41.
by shacharz 10y ago
No, we're not expecting the consumer to pay for the upload bandwidth. We're working with ISPs to not charge consumer for Peer5's upload traffic.
42.
by shacharz 10y ago
We detect what network you're on, on a cellular network you wouldn't upload and only leech from other users and http.
43.
by shacharz 10y ago
We're definitely looking into that, AFAIK for now, is that as long as the content is legal there's no problem with uploading it.
44.
by shacharz 10y ago
1. WebRTC uses ICE[1] protocol to go over NAT and puncture Firwalls. 2. HTML5 logo is under common license agreement and we give it attribution in the /about page.
45.
by shacharz 10y ago
For PeerCDN checkout [1]. What differentiates our solution from previous P2P services like BTDNA, Pando is the underlying technology stack - WebRTC, that eliminates the number 1 barrier - user needed to download and install a plugin. From t
46.
by shacharz 10y ago
2 valid points 1. We suggest a snippet today for our customers to notify their users. 2. https://www.peer5.com/about towards the end of the page you can see the attribution.
47.
by shacharz 10y ago
The point is that there's no double billing, http traffic is being billed by your existing CDN. P2P traffic is billed by us.
48.
by shacharz 10y ago
Devices connected through another device still have the same external ip - allowing us to detect it's indeed Cellular and not Wifi
49.
by shacharz 10y ago
What's different in the CDN use-case is that the content that reached a 3rd user through the uploading user would've reached the 3rd anyway, just from the original server.
50.
by shacharz 10y ago
No, since the verification is done using signatures received from the server, without any reputation system involved.
51.
by shacharz 10y ago
Yes, we do hash verification of the fragments as they are received from users.
52.
by shacharz 10y ago
That's a very much talked about subject in the standardization groups. They've concluded that WebRTC doesn't add any additional privacy or security exposure than what exists in the browsers previous to it. Can you please exp
53.
by shacharz 10y ago
I just know about the IPFS team, but not familiar enough with their stuff. From my experience usually a synchronization oriented distributed algorithm can be very different from what a use-case like Video On Demand, or Live video requires.
54.
by shacharz 10y ago
Serverless CDN is the term we use to describe a CDN that uses no servers for the content itself. It's actually a Peer-to-Peer Content Delivery Network. Big content providers (like Netflix, Youtube, ESPN) can use that to deliver their c
55.
by shacharz 10y ago
Right, that's a great point. We take into account whether your mobile device is currently using Cellular or Wifi and make decisions based on that. (Today Cellular devices would not be uploading at all, just leeching)
56.
by shacharz 10y ago
Hi HN, I’m Shachar, co-founder and CTO of Peer5 - A P2P CDN for Video We started Peer5 4 years ago, when we heard about WebRTC, and thought this is a ground changing technology that fundamentally change the way the web could work. Yea, and
57.
Launch HN: Peer5 (YC W17) – Serverless CDN(peer5.com)
108 points by shacharz 10y ago|117 comments
58.
A node based server library for multiplayer games(incheon.gg)
3 points by shacharz 10y ago|0 comments
59.
New games in December 2016(trendingfoxnews.com)
1 points by shacharz 10y ago|0 comments
60.
by shacharz 10y ago
The problem with PeerCDN and other WebRTC based solutions is that they can't solve the DNS DDOS problem. Since the WebRTC API needs a server for the handshake to start communicating between 2 peers directly.

More ›