Earlier quoted context omitted.
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?
CacheP2P – Distributed caching platform
41–50 of 63 posts
Re: CacheP2P – Distributed caching platform
#42Can I use qbittorrent/deluge to seed webpages?
Re: CacheP2P – Distributed caching platform
#43I'm getting this error on your API page: cachep2p.min.js:9 Uncaught Error: Cannot add duplicate torrent 3cd9bdf4916f422aa77cdd1b952c14202e0eafca I'm also getting these on FF: ICE failed, see about:webrtc for more details(unknown) TypeError: asm.js type error: expecting argument type declaration for 'e' of the form 'arg = arg|0' or 'arg = +arg' or 'arg = fround(arg)'
Re: CacheP2P – Distributed caching platform
#44Re: CacheP2P – Distributed caching platform
#45Would it be possible to make a completely serverless webpage? Or a website that has a server to bootstrap, but all assets are 100% distributed?
Re: CacheP2P – Distributed caching platform
#46Sounds cool, but what are the use-cases? What problems is this tech trying to solve?
Re: CacheP2P – Distributed caching platform
#47This project, and lots of others, would really benefit from a standardized crypto Javascript API in browsers so there is an opportunity for using better hashing algorithms than are realistic to implement in Javascript. Im not saying its realistic to engineer sha1 collisions to serve up malicious content on a platform like this, but its getting closer every year.
Re: CacheP2P – Distributed caching platform
#48This project, and lots of others, would really benefit from a standardized crypto Javascript API in browsers so there is an opportunity for using better hashing algorithms than are realistic to implement in Javascript. Im not saying its realistic to engineer sha1 collisions to serve up malicious content on a platform like this, but its getting closer every year.
It was cool seeing how hashing works under the hood. I used UInt32Array for speed. It is still nowhere near native speed, but fast enough for many applications.