Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CacheP2P – Distributed caching platform

cachep2p.com

Post reply on HN
Print view View original

31–40 of 63 posts

Re: CacheP2P – Distributed caching platform

#31

Post by striking »

Paul-ish wrote: post #21

Couldn't someone create a large number of sybils in this network to see what pages people are loading? Browser sessions could be inferred from this. Also, how much latency does this add due to P2P connection set up time?

Hot-cache reloading the page, the P2P set up time is less than three seconds.

And yes, you could see what resources which people are downloading. It isn't a replacement for a server, just a great way to avoid the Slashdot effect. Definitely not privacy-focused, but I could see some smaller websites using it.

Re: CacheP2P – Distributed caching platform

#32

Post by sprky »

randall wrote: post #23

This has made me rethink a lot of things. I think video on the web should probably use the webtorrent approach primarily. Thanks for posting... gonna go work on some interesting approaches now.

I dont think bittorrent is particularly suited for small file caching and thats how a lot of video is served these days (think about how adaptive rate streaming works, a video is split into thousands of small files containing a few seconds of video at certain bitrates).

Re: CacheP2P – Distributed caching platform

#35

Post by guerrerocarlos »

ravenstine wrote: post #10

I wonder how this could be set up to work on error pages; could this keep pages working even if the server returned a a 503? Such a concept would be pretty useful for a media company, like the one I work for, which mostly serves static content.

Certainly, could be set up in error pages, so that the content get's retrieved from users who already received it instead.

Would recommend embedding everything (all the HTML and JS) in the error page, so that the it works 'standalone'.

Re: CacheP2P – Distributed caching platform

#37

Post by johnhenry »

sprky wrote: post #32
randall wrote: post #23

This has made me rethink a lot of things. I think video on the web should probably use the webtorrent approach primarily. Thanks for posting... gonna go work on some interesting approaches now.

I dont think bittorrent is particularly suited for small file caching and thats how a lot of video is served these days (think about how adaptive rate streaming works, a video is split into thousands of small files containing a few seconds of video at certain bitrates).

I believe that bittorrent works by splitting a single file into thousands of small files, so this may, in fact, be ideal?

Re: CacheP2P – Distributed caching platform

#38

Post by johnhenry »

Great work. Looking through the documentation, I realized that this uses a modified version of webtorrent in order to associate torrents with urls rather than a page's content. I wonder would be necessary if BEP46 were implemented (https://github.com/feross/webtorrent/issues/886) in web torrent?

Re: CacheP2P – Distributed caching platform

#40

Post by thatcat »

theon144 wrote: post #39

I like it, but doesn't this inherently expose all currently connected users' IP addresses to all other users? In other words, if I connect to the webpage and just monitor the swarm, can I log all IP addresses that accessed that page?

Theoretically though it would depend on the size of the swarm and how many peers you had. Tor doesn't support webrtc either.
Post reply on HN