4 ms·
This solution might make a lot of sense as a build-up process. However, until DTube release a client so that the network can build, it's just a centralized vid
by arghwhat 9y ago
This solution might make a lot of sense as a build-up process.
However, until DTube release a client so that the network can build, it's just a centralized video platform using IPFS and STEEM as storage backends. Unless clients are made available, it might as well use S3 and Postgres.
- TekMol 9y agoIf it uses IPFS as a storage backend, then why is it faster to watch the video on the website then via IPFS as hobofan did? This seems to be an indication they store that data on a server all the time.
- diggan 9y agoBy default, when making requests to the HTTP gateway, it'll cache the content requested until a GC runs. So it's possible that the local node you're using, have not seen the content before so it needs to go out and fetch it while the gateway d.tube uses, already has the content fetched and only needs to serve it. Of course, the second time you load the content (or if another node on your local network already loaded it) via a local node, it'll be much faster than the public gateway d.tube is running. Disclaimer: I work for Protocol Labs specifically on IPFS.
- arghwhat 9y agoFurthermore, being behind a CDN, the CDN might be caching some resources at their edges for additional performance improvement. (I believe someone stated DTube was running behind a CDN.)
- btczeus 9y agoThe content is hosted on the STEEM blockchain. d.tube is just a front-end. You can access it thru different front-ends i.e.: steemit.com, busy.org Just like blockchain.info is a frontend to the bitcoin blockchain