> ytdl-sub

> This is the only yt-dlp wrapper that allowed me to properly maintain the Playlist structure to any extent

I have the same requirement and it's possible to do it with the default yt-dlp:

yt-dlp --embed-metadata --parse-metadata "playlist_index:%(track_number)s" "PLAYLIST_URL"

Nice, I'll have to try that. My strategy up until now has been to embed the playlist index in the filename, via `-o "%(playlist_autonumber)02d-%(title)s [%(id)s].%(ext)s"` (or %03d for playlists of 100 videos or more). Works reasonably well for playing the videos in proper order, but the info is only in the filename. Embedding the metadata looks like a better solution if you want a media player to be able to organize the files.

I'm using a GUI called simply "media-downloader". On launch it updates yt-dlp and your chosen JS runtime. It has a separate tab for downloading playlists.

Balatro possibly could have.

Yes, more plausibly. The fact that Balatro is only a 150M download is definitely unusually small by modern game standards - Vampire Survivors is about ten times the size. But 150M is still too big to fit on an N64 game cartridge - those were limited to about 64M.

Balatro is 150MB without trying very hard. I'm sure it could be made to fit.

Just cutting the high resolution textures might get you there.

And only 10MB of that is actual code (LÖVE2D + Lua scripts). The rest is multimedia.

Doesn't have to be social to be enjoyed though.

Yes, but artifacts created in these air-gapped networks are expected to stay there. This is not true for AI lab models, who would get access to the internet once live.

That is not the case, a key purpose for most intelligence functions is dissemination, not holding the secrets in the darkness. For example, satellites take pictures, mobile phones are geolocated, HUMINT sources drop dimes. Then analysis happens high side, and a version of that is automatically and certifiably downgraded to e.g. a report about troop movements, without revealing specific characteristics of the sources used.

The pipeline for model assessments could easily report summary statistics down via a trusted guard product. These are amongst the most highly validated software/hardware devices made, and provide a central point for logging and authorisation out of band.

Sure, derived findings can be published (that's often one of the goals after all), but original artifacts are never expected to leave the premises.

Reasonably sure you'll be able to do the same with DeepSeek in a year if not already.

Awesome. How did you prompt it? In my experience generated long texts quickly turn sloppy.

Also would be great to get an article from other side of the eternal broadcast.

basically, I sent the seed article, the homepage article and the, referring article and I think the whole graph into the prompt, as well as the idea of Fakeipedia and writing guidelines etc. The prompt is in the repo but I’m on my phone so can’t link atm!

Do higher ups actually read contribution policy on a public repo?

I'd rather have extra content in separate files so it's playable by anything.

What's to pad there? Their one nine?

It can only go up from there.

More like the year of the Whopper imo.