I’ve been talking about self-sovereignty since I introduced self-sovereign identity back in 2016. That was about controlling your digital identity, this is about controlling your digital existence. [2/8] http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html
You deserve to be the captain of your own vessel on the digital seas. That’s the simple premise of my new article on Self-Sovereign Computing. [1/8] https://www.blockchaincommons.com/articles/self-sovereign-computing/
Self-sovereign identity was a great first step, but we need to be the owners of our whole experience online, especially as it becomes more important to our everyday life. [6/8]
But you still have responsibilities. In my paradigm of self-sovereign computing, we need to support other community members, either through collective bargaining or sharing resources. It’s the only way we can actually become peers with the corporate behemoths. [5/8]
The crucial difference is that you’re not a serf to corporate entities, or in this metaphor a passenger on a vessel. Instead you’re captain working and negotiating at parity with others. [4/8]
But I hope it also clarifies a crucial fact that I think has gotten muddled over the last several: self-sovereignty isn’t about going it alone. It’s about becoming a peer in a community. [3/8]
You can also join me at @BlockchainComns, which is working on the tools that will make self-sovereign computing a reality. [8/8] https://github.com/sponsors/BlockchainCommons
I hope you’ll joing me to advocate for privacy-preserving tools, to demand transparency from platforms, and to assert control over personal data. [7/8]
@oliverbeige your url http://econpatterns.com isn’t working. A bad TLS cert maybe?
RT @FOUNDATIONdvcs: As always, if a highly motivated and well-resourced adversary gets extended physical access to your device, you should…
RT @DonjonLedger: Coinkite presented the results on their blog https://blog.coinkite.com/donjon-faults-2023/
To give a precision, the seed can be practically ext…
RT @RWOTEvents: Dear Identity Experts,
Rebooting the Web of Trust 12 has begun in Hürth, Germany (just outside of Köln). We’re working on…
RT @RWOTEvents: We’ve got seven papers in process for RWOT12. Here’s the abstracts that we’re working on to continue exploring the frontier…
RT @RWOTEvents: Here’s some of our principles of collaboration in collaborative form!
RT @RWOTEvents: We also immersed ourselves in the space by putting together a timeline of events that have affected the decentralized ident…
RT @ankurb: Thoughts from Day 1 & 2 of @WebOfTrustInfo Rebooting Web of Trust #RWOT…
- I was surprised by how little generative AI was…
RT @RWOTEvents: Here’s the final of the timeline we collaboratively created at #RWOT12 showing influential events for decentralized identit…
The Principle of Least Privilege (or Least Authority) is a cornerstone principle for computer security. But how does it apply to data? That’s what my newest Musings of Trust Architect discusses. 🧵[1/9]. https://www.blockchaincommons.com/musings/Least-Necessary/
I consider this a design pattern like those famously created by Christopher Alexander for architecture. They’re building blocks that can be used to create secure, trusted computing (and now data) systems [4/9]. https://www.designsystems.com/christopher-alexander-the-father-of-pattern-language/
I extend that to data such as SSI and VCs with the Principle of Least Access: “In order to protect privacy, respect individual entitlements, and maintain human dignity, only the minimum amount of data access necessary to achieve a specific goal should be granted.” [3/9]
The Principle of Least Privilege says: give someone the least permissions they need to do their job. @marksammiller extended that to include transitive permissions, creating the Principle of Least Authority [2/9].
If you’re interested in individual consulting on these trust architecture, DIDs/VCs, human rights digital privacy, and related topics, drop me a personal line [8/9].
I’d love to hear your thoughts on this and other design patterns for secure computing and secure usage of data such as that found in self-sovereign identities and verifiable credentials [7/9].
What can you do to ensure that each person has what they need to do their job, and is it a better pattern than the converse? Take a look at the article for the whole discussion [6/9]. https://www.blockchaincommons.com/musings/Least-Necessary/
When contemplating design patterns, I find it useful to twist them on their head, so the article also talks about the flipside: Principles of Necessary Privilege, Authority, and Access [5/9].
If you’re interested in supporting the continued development of trust architectures, become a patron for Blockchain Commons [9/9]. https://github.com/sponsors/BlockchainCommons
RT @matthew_d_green: If anyone thought that the EU legislation on content scanning would be limited, you can forget about that. Europol has…
RT @mer__edith: 🙏thank you @giacomo_zando @Balkanizator & @LudekStavinoha for revealing the EU law enforcement & AI company mass surveillan…