3 ms·

This seems very interesting already! I now have some more technical questions: - Where is the downloaded data being stored? With a traditional bittorrent clien

This seems very interesting already! I now have some more technical questions: - Where is the downloaded data being stored? With a traditional bittorrent client I the data is written to disk. Since JS doesn't make raw disk access available, I'm assuming it's being kept track of in through some js api that tells the browser to store this data. What API is it using? - Even when I finish downloading the video, the player doesn't allow me to seek to random positions in the video. It displays a "this is how much is buffered"[0] bar that is way smaller than the green bar at the top of the page indicating download progress. Why is this the case? - As you can see in the screenshot[0], there's lots of nodes that are labeled with ip addresses that are not visible to my computer at all. Is this because the displayed ip addresses are self reported? [0] - http://nacr.us/media/pics/screenshots/screenshot--17-46-37-2016.png http://nacr.us/media/pics/screenshots/screenshot--17-46-37-2...

vonklaus 11y ago
idk, works perfectly for me. It pauses for ~1-2 seconds then begins the video at the new position. Mac os x el capitan, google chrome latest. Not sure what the deal on your end is but I can seek immediately on page load, and the video begins there after buffer.
jsprogrammer 11y ago
Presumably the data is stored in RAM (or potentially on a swap disk) by the browser. Most likely they are feeding the data into the Media Source Extensions [0] APIs. I'm not sure why you can't seek to random positions. It seemed to work for me, after a few second delay (presumably to issue commands to start downloading different blocks). Those IP addresses are private network addresses. The machine you are connected to is probably behind a NAT and is connected to you through a different address. The UI is probably just showing the local address that that node reports. [0] https://w3c.github.io/media-source/ https://w3c.github.io/media-source/

vonklaus 11y ago

idk, works perfectly for me. It pauses for ~1-2 seconds then begins the video at the new position. Mac os x el capitan, google chrome latest. Not sure what the deal on your end is but I can seek immediately on page load, and the video begins there after buffer.

jsprogrammer 11y ago

Presumably the data is stored in RAM (or potentially on a swap disk) by the browser. Most likely they are feeding the data into the Media Source Extensions [0] APIs. I'm not sure why you can't seek to random positions. It seemed to work for me, after a few second delay (presumably to issue commands to start downloading different blocks). Those IP addresses are private network addresses. The machine you are connected to is probably behind a NAT and is connected to you through a different address. The UI is probably just showing the local address that that node reports. [0] https://w3c.github.io/media-source/ https://w3c.github.io/media-source/