3 ms·

A server only needs to support range requests to support seeking to parts of the video that haven't yet downloaded.

6510 5y ago
If something is not available you try to make things work without it. The videos play just fine until the user attempts to seek. At that point playback is terminated. Thus therefore as a result thereof the reason forwhich one can not put a video on the website is that playback may be terminated unexpectedly. It's just too embarrassing, I don't want to see myself explain why it doesn't work to anyone. You can disable controls entirely or javascript the seek event but I don't consider those nice solutions. The video player should work by default. The millions of crappy web devs simply want to use it without investigating the weirdness and hacking up some event listener to allow seeking in already downloaded parts. Or is that seeking backwards only? I don't want to know the answer honestly. Perhaps I should just offer a download? Just like things use to work? But then the browser may play it in a tab and pretend seeking is supported again. Ah! So I have to use the old forced binary file download with application/octet-stream so that the user can watch the video in a different player. One with expected behavior. I just want to drop the file in a folder and send the link to someone. Adding a header to it is already asking to much. I could see myself bother to provide multiple formats in multiple sizes because that is an actual hard problem (I'm lying to be polite here) I find it amazing how well everything in our world works. We humans are very hard working but we tend to do everything wrong most of the time. Look how much effort it took to get embeded video on a web page. It actually works! Well, almost.... This comment is getting so long, I'm probably wrong in more than one way, made a dozen grammatical boo boo's and misspelled a bunch of words. Still, plenty of room left for mis-interpretations and -understandings. I hope no one is watching us.

6510 5y ago

If something is not available you try to make things work without it. The videos play just fine until the user attempts to seek. At that point playback is terminated. Thus therefore as a result thereof the reason forwhich one can not put a video on the website is that playback may be terminated unexpectedly. It's just too embarrassing, I don't want to see myself explain why it doesn't work to anyone. You can disable controls entirely or javascript the seek event but I don't consider those nice solutions. The video player should work by default. The millions of crappy web devs simply want to use it without investigating the weirdness and hacking up some event listener to allow seeking in already downloaded parts. Or is that seeking backwards only? I don't want to know the answer honestly. Perhaps I should just offer a download? Just like things use to work? But then the browser may play it in a tab and pretend seeking is supported again. Ah! So I have to use the old forced binary file download with application/octet-stream so that the user can watch the video in a different player. One with expected behavior. I just want to drop the file in a folder and send the link to someone. Adding a header to it is already asking to much. I could see myself bother to provide multiple formats in multiple sizes because that is an actual hard problem (I'm lying to be polite here) I find it amazing how well everything in our world works. We humans are very hard working but we tend to do everything wrong most of the time. Look how much effort it took to get embeded video on a web page. It actually works! Well, almost.... This comment is getting so long, I'm probably wrong in more than one way, made a dozen grammatical boo boo's and misspelled a bunch of words. Still, plenty of room left for mis-interpretations and -understandings. I hope no one is watching us.