4/9/2023 0 Comments Vuze webtorrent protocol popupI'm not aware of any video formats that are arranged this way though. The blocks wouldn't have to be sequential: as torrent transfers are essentially random access you could have the content required for lowest quality display at the start of the file and the extra data further on, similar to how FLIF supports almost immediate low quality with progressive improvement as the rest of the file arrives ( - see the video demo part way down that page, or for a more interactive look at how it copes with truncated files). it has a block structure that lines up with the torrent block structure such that block X is enough to play a given set of frames at the lowest quality, block X+1 for better quality, and so forth. Well, it would be possible but only if the video format in the torrent allowed for this is a way compatible with the way torrent transfers are split into blocks - i.e. Also see "podfuk", though it looks pretty ancient. Update: AVFS seems to be an all-in-one solution that handles HTTP, FTP, WebDAV, Zip/RAR/Bzip, SSH, and others. I'd appreciate a link if anyone finds one. Incidentally, I can't find any archives with audio hosted on a server that supports Accept-Ranges on the open web. GNU Hurd took this approach, with the native ability to mount tarballs and FTP servers as filesystems, and POP3 as an mbox file. The job of an archive reader, disk reader, or "server reader" should be to translate these things into the filesystem so that all programs benefit. Not sure about the reliability, but I think the approach is more general - you could even stream from within a remote archive this way, using whatever program you wanted. I believe this can be achieved via a combination of httpfs and archivemount. Projects like the Internet Archive can make huge files available for immediate streaming on their website, without paying for bandwidth. If enough people end up running it, BitTorrent in the browser will really happen. I'm really excited about the way WebTorrent Desktop bridges the WebTorrent and BitTorrent networks. Tons of cool new uses of the web are just at the edge of becoming possible. Safari is almost certainly gonna get WebRTC support as well - it's already in WebKit, just not enabled in Safari yet. Edge is getting Data Channel support soon. Even today, Chrome has a few big bugs left ( eg ) and WebRTC is not yet supported in Web Workers ( ). WebRTC support in browsers was flaky and buggy until very recently. Every single page of Electron docs or code I've looked at on Github, the latest commit on it is zcbenz. He's incredibly prolific and seems to be nearly single-handedly developing the Electron project. Many of the little things that an app needs to feel native and professional have clean cross-platform APIs. System tray integrations, desktop notifications, launcher progress bar in OSX, installers for all three platforms, seamless auto updaters for Mac and Windows, a crash reporter, and so on - all built in. * Electron is surprisingly nice to work with. This is what Feross and I have been working on the past few weeks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |