Discussion about this post

User's avatar
Johnathon Lang's avatar

Hello Jordan,

I've been following your work for awhile. For me, this article (call to action) points to a practical application/expression of the concepts you've been sharing for many years now. Thank you.

Expand full comment
Luka Kovačič's avatar

This is how I see it currently...

The hyperstructure should be able to push all self-interested parties (the state, big tech, ...) to the edge, where they are all on the client side of any such identity system.

The decision to collaborate or transact with a certain person or organization (as proven by the digital identity) should be done dynamically on the edge (the client side).

You are free to disclose a certain part of your digital identity to a certain party (person or organization), when you decide to.

You can make parts of your identity visible to anyone, when you decide to.

Most services (those who are not government regulated like finance) should not require any institutionally provided proof of identity, as people should self-regulate (on the client side) their "valid identity filters".

If you wish to delete one of the proofs associated with your identity, do it, but you might not be able to access some service, which is dependent on this specific proof.

The government is just another trusted identity (categorically an organization) - if the government proves your identity, fine, that is just one more proof of your identity. That could also be done by a company - KYC (also categorically an organization) or some person.

How you personally value these proofs, that is up to you.

What I would not like to happen is that *any* one organization (the government, some company) statically embeds their permission checks or their own "special status" into this hyperstructure.

These should be done at the edge by persons and organizations (companies and institutions).

These digital identities also should not get in the way of P2P communication.

Expand full comment
9 more comments...

No posts