> Only the current audio/video frame is being sent to the viewers, there is no way they can download/cache the videos either for future usage.
This seems misleading, though. I think I get what was meant: clients can't send a request to download from the start or a specific offset and thus "download" the original file, the server is in charge of what's being sent. However, clients can still capture the frames, save them, and replay them, obviously. And I see a button to "Seek", so...
Cool. What are the hardware requirements? I use https://github.com/calzoneman/sync with mp4 files served by nginx and it works great for 15-20 people watching on a cheap 0.5GB ram 1 vcpu vps.
Cool project.
> Only the current audio/video frame is being sent to the viewers, there is no way they can download/cache the videos either for future usage.
This seems misleading, though. I think I get what was meant: clients can't send a request to download from the start or a specific offset and thus "download" the original file, the server is in charge of what's being sent. However, clients can still capture the frames, save them, and replay them, obviously. And I see a button to "Seek", so...
Cool. What are the hardware requirements? I use https://github.com/calzoneman/sync with mp4 files served by nginx and it works great for 15-20 people watching on a cheap 0.5GB ram 1 vcpu vps.