Protip: if you requested the 26 beta and are regretting that rash decision... Reboot, then hop back into update settings and change it back to off. Thankfully, it resets and now you can wait out the far more sensible 0.2 beta, where they've ironed out the crazy kinks.
Second the pickling idea. Read a similar story that a food bank had a lot of excess fresh material. Thry had set up production through a commercial food processing site, had put labels on them, and were selling them online and at farmer's markets. The proceeds were going back to the food bank. Zero wastage. They were also making things like sauerkraut, kimchee, and kombucha. Watermelon can also be juiced and the rinds pickled.
I imagine for food safety and liability reasons, you wouldn't want to do it in someone's kitchen. Plus, licensing fees. But you have a great story to tell (good health, zero waste, help food bank).
3rd grade. Teacher sent me and my best friend to the office with a note for being too disruptive (we were snickering a lot). I was used to getting into trouble, but he was petrified and shaking. I felt bad for him, so I told him I would take care of it.
I tossed the note over the wall, then we went off and played in the yard for the rest of the morning.
In the afternoon, there was school assembly. The two of us were called out by name and were told our parents would be called to come collect us. My mother showed up and couldn't stop laughing at the silliness of it all.
My kids had a lot of fun with stuffed bears and dogs from Ikea. On several occasions, I had to re-stuff them (to comedic swole effect) with fill from craft stores. Pretty easy.
A couple years ago, I would have agreed. Most of our email is junk. But nowadays, you can have an LLM digest and summarize it for you. That could also be a service the legacy system offers.
Grandkids can just ask for a free-form search term without having to wade through everything.
A long time ago, I had the idea for a startup to keep digital material, including accounts, passwords, old documents, etc. in a digital vault that would be released to the next-of-kin when someone dies. It would also convert documents to newer formats so your old unpublished WordPerfect novel could be opened and read by the grandkids (should they choose).
Problem is, nobody would (or should) trust a startup with that material. This is stuff that should be around for many decades and most startups go out of business.
Cloudflare does use AI to generate tarpit content, but it's too expensive to run for every request. IIRC, they periodically change and cache the output to throw off the tarpit detectors.
One thing most DON'T do is change up the format for the page, so the placement and number of links randomize.
Same question applies to all the other websites out there being mined to train LLMs. Google search Overviews removes the need for people to visit linked sites. Traffic plummets. Ads dry up, and the sites go out of business. No new content to train on 🤷🏻♂️
The exact format depends on the source file format, the platform of the player, the duration of the clip, encryption, and whether it's copyrighted material or not. Also, if it's older software or fairly recent (the current schemes stand on the carcasses of a lot of old formats).
If the source is a single file, it's likely MP4 or WebM (or MOV on Apple and AVI on Windows). The video player can start downloading the whole thing in a background thread. When it has enough material buffered, it can start decoding and playback. However, if there is a network glitch, the video may start pausing and stuttering. This is typically how unprocessed video is served from a cloud file storage site.
Many sites use HLS or MPEG-DASH (or their superset CMAF) to send the video in adaptive chunks. The user-experience is much better and has better server utilization. The manifest files describe which chunks to get depending on current bandwidth. Players can then up or downscale their next request based on network conditions to avoid stuttering. Overloaded servers can also downthrottle the chunk formats on-the-fly.
Apple device native video players only support HLS/CMAF, and inside native appstore apps, files over 10 minutes must be HLS formatted. Non-Apple devices may use either format.
Then there's encryption. If a decryption key (often AES-128) is provided, the player can download it over https, then decrypt the stream on the fly. This is so anyone sniffing the stream only sees encrypted content.
If the material is copyrighted, it may have DRM. On Apple devices this is likely FairPlay. On Windows it could be PlayReady, and on Android and for some browsers, it could be Widevine. Then there's CENC, which use a common encryption format so the same stream can have PlayReady or Widevine.
Most browsers support HLS, since it's delivered over HTTP, it's adaptive, and tools like ffmpeg or handbrake can generate all the files and chunks one time, once a video file is uploaded. The chunks can be hosted anywhere HTTP is served.
This is all for one-way, one file, one viewer mode. If the video stream is meant to be two-way or multicast to lots of viewers, you'll want to head into the world of WebRTC, RTMP, and RTSP.
This also means anyone wanting to mess around and subvert society can create a whole corpus of disinformation and put it out for the LLM spiders to pick up.
They're just sucking up and ingesting whatever's out there unquestioningly, with little regard to its veracity. For the record, I think this is a BAD idea. Then again...
Protip: if you requested the 26 beta and are regretting that rash decision... Reboot, then hop back into update settings and change it back to off. Thankfully, it resets and now you can wait out the far more sensible 0.2 beta, where they've ironed out the crazy kinks.