| Sure. As @diminoten mentions, legality is questionable here, so I do not recommend. If you do dabble, restrict access, and encrypt everything so that if you lose your keys, they only option is to destroy the stack and start over. Cloud provider of your choice Plex media server running on a high-throughput instance, with cloud storage mounted locally for reading. (Redundantly created in multiple regions depending on where the service is being accessed from) A separate master instance responsible for downloading content from a private torrent site, with cloud storage mounted locally for writing. Multiple on-demand background workers that are spun up when new content is available to be reformatted in various resolutions. They pull the original video from cloud storage, create various versions, and re-upload it to the cloud storage. The largest cost is in data usage, and storage. @diminoten Not sure what I did to "oversell" it. I used off-the-shelf tech components, and some cloud-enginuity from experience, to build a proof-of-concept competitor. I didn't build the entire interface from scratch, or write my own OS, if that's what it sounded like. |
Do you think it would be viable using a pool of 'a few' residential connections (think fiber >500 Mbps upload) in each region, with some x86 server behind each to transcode / store?
The idea being to self-host the whole infra between users themselves, those willing to plug a desktop/server somewhere.
I figure you'd only need a basic load balancer in an actual cloud (always on) which redirects to whichever server is available enough.
Any thought about any of this?