[FEATURE] WebRTC P2P Video delivery

[ghost]

Why:

• To keep bandwidth cost extremely low
• Allow many people to watch hosted video content at the same time with fast loading speeds (even if the site is hosted on a home server)
• Negate the need for a CDN (even when hosting lots of large videos)
• More users means even better performance (not the other way around)
• No reliance on third party video delivery services
• Works natively on all modern browsers
• Supports VOD and LIVE video (depending on implementation)

Method 1: Using a HLS.js player such as Clappr with P2P Media Loader or CNDBye. Demo example Simple implementation tutorial

Method 2: Using IPFS-JS implementation of IPFS protocol. Demo example

Method 3: Using WebTorrentPlayer which is built on WebTorrent which a lot of projects use. How WebTorrent works. Demo example

[khusika]

Why:

• To keep bandwidth cost extremely low
• Allow many people to watch hosted video content at the same time with fast loading speeds (even if the site is hosted on a home server)
• Negate the need for a CDN (even when hosting lots of large videos)
• More users means even better performance (not the other way around)
• No reliance on third party video delivery services
• Works natively on all modern browsers
• Supports VOD and LIVE video (depending on implementation)

Why do we need P2P video delivery in static website especially in Hugo? FeelIt already has Youtube & Vimeo for embedding video. Even you can attach live video stream with both of those apps.

[ghost]

Why do we need P2P video delivery in static website especially in Hugo? FeelIt already has Youtube & Vimeo for embedding video. Even you can attach live video stream with both of those apps.

• People would gain complete control over the compression and quality of their videos, so if artists want to use Hugo as their portfolio site where they share their work, they can then easily share their own videos, at whatever resolution and compression quality they need. Sometimes they do not want their work on third party services such at YouTube or Vimeo. Already on YouTube, if age verification is required for a video, a person needs to sign in to YouTube to watch a video, making embeds non-functional. Recently YouTube also changed unlisted videos to private, making them unavailable, so who knows what they'll do next. Having the option to not be reliant on other services is also very future proof. You can just take your entire Hugo site and host all content completely elsewhere no matter what happens to Youtube policy.

• Hugo is getting a lot of traction right now because more and more people want to have their own site, and have complete control (and ownership) of their own content, away from dominating services (like YouTube). Having the option to use WebRTC P2P video in Hugo means a lot more people (and content creators) can choose to make and host their own websites (even from their home). Imagine if people who make their own animation movies, nature exploring videos or video podcasts can all switch to Hugo completely and build their own communities. YouTube community is not always desirable either, so people may want to split that base of users from their content.

• There are some countries that are cut off from YouTube / Vimeo, so they can not upload to, or watch videos from those services. Unfortunately this list is not static either, at the worst time (like during protests) a lot more countries block access to popular sites like that. So if independent journalists or activists want to share content with their country, reliance on popular video hosting services is a no-go. It also allows for easy mirroring of sites including their video content, so if one source goes down, the others would still be up.

I know I'm asking a lot, but I hope you can see the benefit of having the option to be completely self-reliant.

[khusika]

WebRTC on Hugo is an out of the box idea because Hugo it self doesn't have a WebRTC API (no documentation found).

Based on your request, all the mentioned resources are still using 3rd party libraries because static websites cannot process a dynamic data. And yes, the cycle will be the same as the 3rd party video players we have (Bilibili, Youtube & Vimeo) even simpler

This is a Static Blog Theme not a video streamer app.