They'll have to do that eventually, right?
They'll have to do that eventually, right?
I suspect that’s Google beginning to trim unprofitable channels using a lot of storage: delete them for bullshit reasons.
Especially if the amount of content uploaded keeps going up, so the relative benefit of deleting old stuff is small.
I agree. That's why I've recently made a practice of backing up things to which I'd regret permanently losing access.
https://ourworldindata.org/grapher/historical-cost-of-comput...
I have two accounts from my youth with mostly fansubs and "funny" vids. (A "Everybody Draw Mohammed Day"-Video that, 11 years after its upload, got band in Pakistan.) It includes two very successful (over 1M views combined) uploads of political TV shows. I will not log in to this this accounts. So this stuff will get deleted. So in the long run, stuff will disappear from YT.
[1] https://blog.google/technology/safety-security/updating-our-...
Would be nice if they would write that into the actual policy and don't just add a random sentence to a blog post.
The question is whether YT is serving up the one (redundantly-backed storage) copy they have of your almost-never-watched video, or whether it's serving it up from one of 1,000+ copies it's made across the globe for currently popular videos.
After that, you can plunge into colder storages and warm things up as you stream. Additionally, if you need longer to 'defrost' things, just cache a few more MB at the front. Cheat a bit by assuming 480p to start with if you need to; even less to store.
Maybe Google holds your content in 7 data centers round the world (~1 per continent for planned maintenance + latency + reduced oceanic fiber usage).
But with old rarely streamed content they might cut that down to just 3.
However, implementing this in practice is non-trivial. Knowing what is "everyday content" versus what is "once a month content".
To add more complexity -- you have these semi-predictable hype-waves especially two peaks in case of most YT videos where a "once-a-month" content becomes an "everyday" content before again becoming a "once-a-month" content. It feels you could specifically optimise for this -- reduce storage costs without sacrificing UX.
Caching is hard but this sounds like an ARC would likely catch this, if it occurs on a small number of videos concurrently.
My guess is that the first step will be to re-encode all the non-popular videos with severe lossy compression.
You know that because when they release a new format (eg. HDR or a different resolution), they re-encode from the original. Various people have tested that with moire patterns and various other ways to demonstrate if something was encoded more than once.