noosphere

ices - Cryptography/Privacy: help us make strong guarantees about public and private information, and bring user legibility to content provenance and authority Some topical links: - Subconscious Blog: https://subconscious.substack.com/ - Noosphere Project: https://github.com/subconsciousnetwork/noosphere If you are interested, please drop us a line to introduce yourself at work@subconscious.network

e strong guarantees about public and private information, and bring user legibility to content provenance and authority Some topical links: - Subconscious Blog: https://subconscious.substack.com/ - Noosphere Project: https://github.com/subconsciousnetwork/noosphere If you are interested, please drop us a line to introduce yourself at work@subconscious.network

ere about our technical progress.

internet of ideas. My personal opinion is that we need more than a story. Our users need tools that empower them to be in control of their data, and that includes being able to keep private data private, fix mistakes and execute countermeasures when they are threatened with abuse. And it's true: immutable data is a double-edged sword. The primary benefit we seek from it is content addressing, which enables us to look up some data in a way that makes data providers fungible. This has an advantage when it comes to censorship: if censored network A can't give you your data, you may be able to find it on uncensored network B as long as your know the content address. It also presents a challenge: sometimes a user may rightly wish for data to be removed from the network; content addressing creates the possibility that an abuser may have access to data in a way that further dis-empowers users who are already vulnerable today. Here is a strong opinion (weakly held) that I have about mutability: the "mutability" of the hypertext web has not spared us from the kinds of danger described above. We have leaned on mutability as a privacy crutch, and in turn we have excused ourselves from providing capabilities and interfaces that enable real privacy and agency for users under threat. For example, a user may think a Snap message is extra private - from their perspective, the message is ephemeral - but others will still find ways to make copies and propagate the data across the network, and Snap the company certainly has access to the data (perhaps in perpetuity). What recourse does that user have once their data escapes the mutable sandbox? It's possible that immutable data will enable us to build better tools for taking pro-active action against abuse. For example: today on the hypertext web, the recourse for most users to head off the propagation of harmful data is to reach out to service providers individually, file abuse claims and hope that the content is eventually removed. Victims are burdened with both identifying that the data is stored with a provider, and also the clerical task of reporting the abuse over and over again. In a world with content addressing, anti-abuse filters full of content addresses may propagate fluidly from provider to provider, which suggests a far less burdensome process for the abuse victim - they don't need to know that the content has surfaced on some provider in the distance, because the provider is already aware of the abuse claim and can pro-actively refuse to propagate the data. In the end, I think the best solutions to the problems of this kind of abuse will be social/legal ones, supported by a technical foundation that can enable pro-active countermeasures. All that said, I'm not an expert on this topic, I just like to spend a lot of time thinking about it. If you or someone else reading this is an expert, and you have some time to spare, please come hang out in our Discord or on Github and teach us what you know!