Ciro Santilli @cirosantilli 35

As a JSON: github.com/cirosantilli/media/blob/master/cia-2010-covert-communication-websites/hits.json. OurBigBook Markup to JSON conversion helper cia-2010-covert-communication-websites/bigb-to-json:

Hit criteria: has Wayback Machine archive, and clear indication of a known communication mechanism. The mechanism itself doesn't need to be archived however, a link to it is enough given other supporting elements: IP range, site style, date, web archive date pattern. JS commons are always quickly visually inspected, other mechanisms we look only at filename patterns. Commented edge cases that didn't make the cut can be found mostly under Section "IP range search" and Section "2013 DNS Census virtual host cleanup heuristic keyword searches".

Some less-trivial breakthroughs:

Initial announcements by self on 2023-06-10:

Shared by others soo after:

2023-10-26 twitter.com/cirosantilli/status/1717445686214504830: announcement by self after finding 75 more sites

Second wave:

Some more:/ny

The third one from Cambridge after:

Some good mentions at: Video "Where is Anatomy Encoded in Living Systems? by Michael Levin (2022)".

As of 2023, working with DNS data is just going through a mish-mash of closed datasets/expensive APIs.

We really need some open data in that area.

This is going to be the most important application of generative AI. Especially if we ever achieve good text-to-video.

Image generators plus human ranking:

www.pornhub.com/view_video.php?viewkey=ph63c71351edece: Heavenly Bodies Part 1: Sister's Mary First Act. Pornhub title: "AI generated Hentai Story: Sexy Nun alternative World(Isekai) Stable Diffusion" Interesting concept, slide-narrated over visual novel. The question is how they managed to keep face consistency across images.

The fundamental insight of Git design is: a SHA represents not only current state, but also the full history due to the Merkle tree implementation, see notably:

This makes it so that you will always notice if you are overwriting history on the remote, even if you are developing from two separate local computers (or more commonly, two people in two different local computers) and therefore will never lose any work accidentally.

It is very hard to achieve that without the Merkle tree.

Consider for example the most naive approach possible of marking versions with consecutive numbers:

If Local 1 were to push to Remote first, how could Local 2 notice that when it tries to push itself? The navie method of just checking: "does Remote have commit "2"" does not work, because Local 2 has a different version of commit 2 than local 1.