provability

Striving toward, not retroactive detection of deepfakes & other fake evidence, but prospective, pro-active measures (instrumenting data) to increase PROVABILITY -- that is, to

approach asymptotically

the ability eventually to prove

that content (especially time-series data like video, audio, or scientific data)

was created at the time & place claimed,

helping multiple witnesses to corroborate one another's accounts if they so choose,

while maintaining their privacy.

I'm committed to nonprofit, open-source, grassroots, and decentralized solution design, because, in general, one cannot expect to maximize more than one parameter at a time, and truth is the parameter I am trying to maximize. It would be nice to be paid to work on something I care this deeply about, but I am not sure how to fund a properly decentralized design effort. Donations, perhaps? Maybe if I could enforce that all donations are anonymous. I don't want a "tail wags the dog" situation.

The big tech companies might be pressured to adopt the open-source-designed (community-designed) solution after it's complete and has proven its superiority.

In the early 1990s I was on the Cypherpunks email list, which discussed the trusted timestamp service by Haber & Stornetta (1990) at Bellcore, based on inserting hashes of content into a Merkle tree. My interest in algorithmic information theory led me to join a company that commercialized code division multiple access (CDMA) for wireless telecom.

I have a computer engineering degree (1995) from CMU and experience in mobile wireless, real-time systems, assembly language & DMA on several processor families, device drivers, TCP/IP, computer vision, high-power LED board design, web back-end & a little front-end. I'm very much "beyond full-stack," learning & doing new things every year.

[this username} (AT] rise up dott nett (please use your human imagination to make sense of this)