Let's rephrase that, if you have easy access to hosting and [sufficient] bandwidth, can anyone recommend creator-friendly tooling such that you can just host your content yourself?
I'm so done with relying on third parties to do a poor job hosting stuff I created :(
Most of your garden variety blog/CMS engines have plugins that can even automatically take media uploads and stash them on Amazon or a similar CDN. For something that's not even that big, that might even be overkill. If the amount of data transferred monthly is low enough, you could probably just serve it off a VPS.
If I had to actually recommend a service it'd be Cloudflare Stream[0], which allows you to upload videos, CF transcodes them, and you get a link to a page with just the video player[1], and they offer options like only allowing embeds on certain origins and disabling/enabling MP4 downloads. The pricing is fairly reasonable as well at $1 per 1,000 watch minutes and $5 per 1,000 minutes of stored video.
0: https://www.cloudflare.com/products/cloudflare-stream/
1: https://watch.videodelivery.net/b9d528d5eece459b80113823cefd...
but why does it need to have all these different formats and bitrates?
varying devices/platforms support varying formats
>bitrates
so some guy on watching on a 3G connection doesn't need to watch your 4K stream.
You can probably implement a part of these features imperfectly in a regular CMS and with the video tag, but you may as well use readily-available software that do this job for you well.
If you host, occasionally, one or two videos, that's probably the best thing to do, but if you are to create a channel, you are probably better of using dedicated software.
* I think it’s dubious that S3 & CloudFront is really DIY anyway but hey, if you already broke the seal.
You know how much cloudfront bandwidth costs? $0.085/GB. Vimeo has a 2TB/month limit before they "may reach out to discuss a more suitable plan for your needs". If you consume that much bandwidth, it would already be costing you $170/month on AWS for the bandwidth alone. I suspect viemo's plans are still going to be cheaper.
For example you seem to know your way with the solutions you propose, but I already see an issue, as in reality WebM is a format limited to VP8 and VP9, and cannot contain H.264 video.
But Chrome ignored this limitation and wrote a muxer that is actually able to store H.264 inside WebM files, thus going out of spec... which means different tools might have different degrees of support for those files.
https://bugs.chromium.org/p/chromium/issues/detail?id=980822
Arguably, a former user of YouTube or Vimeo shouldn't have to learn about all this, and shouldn't have to end up reading bug reports such as that one (and this is just scratching the can of worms that is all the topic of codecs, encodings, containers, etc.)
https://github.com/Chocobozzz/PeerTube/blob/develop/support/...
PeerTube is a piece of open source software meant to build a YouTube-like platform, with optional federation (and P2P to allow servers to offload some bandwidth to viewers, but I don't know how well this works in practice with the widespread asymmetrical or mobile internet connections). It is not for the viewer to install.
I host a PeerTube instance for my choir and I don't quite care about the existence of PeerTube instances hosting questionable content. I didn't enable federation though. Still hesitant to do this.
Maybe the current system works after all? Just don't visit those instances you dislike, this is what I do. Give people the option to choose for themselves whether they want to partake of material which you or I or my neighbour or his dog finds offending.
Imagine using WordPress to construct your website. If some page existed that listed all the sites that use WordPress, and that listed some disagreeable ones (as it surely would), that has very little impact on your usage of the software.
So, no. Either everyone is censored or no-one is. I vote for the latter, let the law decide what is allowed and keep it at that. If it isn't forbidden, it is allowed.
[1] this is not a joke, see https://www.vox.com/the-goods/2019/2/25/18234950/knitting-ra... where they seriously talk about 'Fiber artists of color' (?) pointing out the 'racism' (?) in the knitting 'community'.
The killer problem is specifically the bandwidth. There is not enough capacity to scale video over IP transit[0]; individual creators will get hosed by bandwidth costs. The way that every video platform gets around this is peering[1], but that requires lots of capital expenditure; and last-mile ISPs will play shenanigans with peering negotiations[2]. This is also why video is a monopoly market: large companies can negotiate way better bandwidth deals than you can.
Someone else mentioned PeerTube; I personally do not consider it a solution because P2P is a privacy nightmare. It's still fairly common still for vexatious litigants[3] to sue members of BitTorrent swarms to try and extort settlements out of people. Not to mention, how the heck do you handle GDPR in an environment where every one of your customers gets every other customer's IP address?
[0] What most people think of when they talk about "buying an Internet connection" - you pay someone else to route your packets.
[1] How ISPs connect to one another. You set up a link between your network and theirs, either in the form of physically wiring up extra cabling or connecting up different switches in a colocation center. That link then carries all the traffic between you and them (and either side's transit customers).
This saves money over transit, if you have lots of traffic between you and that ISP.
[2] Notably, Comcast refused to upgrade their link with Level-3 because Netflix was one of their customers
[3] Also regular copyright holders too, but usually they give up once they get a DMCA takedown processed.
A typical content creator is unlikely to have enough demand for their videos to congest IP transit links.
IP transit is also very,very cheap. At scale IP transit is only about 5 cents per Mbps.
Source: built and operated a global CDN in-house
Looks like someone built a solution awfully quickly!