While I think the concept of BitTorrent to handle distributed storage is a good line of thinking, I have a feeling keeping seeders alive.

I kind of wish for Pied Piper from Silicon Valley. Distributed sharding with p2p distribution. I can only speak for myself, but my phone has more storage than I would ever need, and T-Mobile 5G is unlimited, just cache the video content as and my phone can serve chunks as a temp seeder until I need that space for new content. With enough people contributing the space needed per person could be negligible. Extending to a federated backend protocol, selfhosters to large organization could contribute block storage as things scale. BBC just started exploring Mastodon. If there was a viable video platform for BBC, their resources would help establish large collective pools of data.

Just keep it a completely open source standard, very strong encryption/compression and wide duplicated sharding across devices. I absolutely hate blockchain hype, but an actual use case would be a blockchain index of where each chunk of information resides.

All of that totally hypothetical, that’s just my “throw shit at the wall” idea for a federated solution. Initial adoption would probably never succeed. Just like in the show, things are getting to incredibly complex solutions once federated networks come into play, explaining it to not computer oriented people would be neigh impossible.

Took a few steps to get there. First prompt was just to create some data.

Perfect! Please generate 10 users to be used for seed data. I would like the users to be based on Dragonball Z characters

Followed with:

Okay, that is pretty cool. Lets reference something I am more passionate about. Can you generate the data again, but this time use Neon Genesis Evangelion as a reference for the data. Also please include an 11th entry at the very beginning that contains all fields as 'test' and is_admin = true

And finally:

hahaha I love that. Just for shits and gigs can you redo that but use washed up 80s rockstars as a reference?

I figured I could use data my boss could relate to.

Pushing traffic to https isn’t the worst thing. My ask would be to have a toggle to disable due to local development or server deployments where http/port 80 is the only choice.

The channel was much better when they were in the house and the backups were stored on a toilet.

Because that one GitHub project that solves your needs but has sparse documentation and only works if it’s as close to what I assumed it was created on.