[submission] Creative Privacy

[bumbleblue]

The Design Problem

Creative pursuits often involve multiple people. Cloud-based collaboration typically takes place in shared digital spaces. However, the feeling of being observed while working can be uncomfortable, as many of us value privacy when developing new ideas.

The Design Solution

Creating a space for users to exercise their creative privacy, for example by giving users the options to make a private, editable copy of a shared document. This issue is orthogonal to decentralized technologies, but of course decentralized technologies are uniquely positioned to solve it as there is nothing more private than "local" (on my computer only).

Examples

We haven't seen a real-world implementation of this pattern just yet.

Why Choose Creative Privacy?

Creative Privacy is not only a design goal, it can also be used to frame the value proposition of a decentralized technology.

Best Practice: How to Implement Creative Privacy

• Give clear UI indicators between the private and shared version of the document
• Do not automatically upload to a shared cloud

Potential Problems with Creative Privacy

The Take Away

References & Where to Learn More

• [Upwelling discusses the problem at length](https://www.inkandswitch.com/upwelling/)

[bumbleblue]

Notion's scratchpad is an example of this.