We do not intend to enforce any sort of identity verification or unique identities in distributed[C]. We do not think encouraging people to doxx themselves is a good idea.
This goes beyond concerns about privacy, though. We believe that having multiple personas, which you can use depending on the context you are in, is healthy.
This raises concerns regarding disinformation. If the platform is uncensorable, and we do not plan to enforce identity, how will this not become a cesspool of fake news?
(This post is about distributed[C], an experimental decentralized publishing platform Haad and myself were running through 2021-2022. It’s currently inactive.)
distributed[C] came about originally as a design experiment, thinking that a completely peer-to-peer Tumblr would be a great testbed for swarm-based design (more on that later).
A talk on conceptual accessibility being fundamental for adoption, while discussing mistakes I’ve made.
I delivered this talk at SAP Inside Track Berlin in September 2018. The audience was mostly enterprise developers, almost all of them specifically working with SAP as a platform.
Given how many companies I’ve seen flirting with the idea of distributed ledgers, I thought it would be useful to give people an idea of which cases I see as being a good fit for them, to give them a leg up the next time it enters the discussion.
I delivered Remember The Rubber Hose, a talk on privacy and distributed applications, at DappCon Berlin 2018. Skipping the introduction and going straight to the beef…
Last week I had the privilege to speak at infiniTIFF Summit, a part of the Transylvanian Film Festival dealing with technology, storytelling and experimental narratives.
I wrote Stories We Tell Ourselves for the summit. Below is a slightly longer version of the talk I gave.