Robust to attacks and open for strangers.

Knowledge collaboration with strangers. Offer Software services on an open network.

The problem comes when the bad actors attack the network we need to move to our central services for safety. We want to fight back to keep the network open.

In the early days of the Internet, everyone was naively cooperating because no one was attacking. when bad actors started attacking, we moved to safety, sacrificing cooperation.

How are we doing this with hardware Giving us Address Space boundaries, memory-safe languages, Object encapsulation, and Modern Cryptography giving us crypto primitives for safety.

Impersonation: No one can seem to be you.

Censorship: No one can take your "name" away from you.

A successful example is Bitcoin. Your key pair is your account and holder of the coins. No one can spend your Bitcoin, and no one can prevent you from spending it.

We did the same thing for our knowledge and ability to communicate with each other.

We need to solve two Kinds of Safety. Proactive and Reactive.

Are we storing passkeys or emails on a node?

up to now, everything is p2p content.

Is this right?

We have a Subscritpion Lists.

We have Contact Lists.

How are we going to store Passkeys? Or members? Or Paid Subscriber Or Collaborator.

Collaborators goes with the

Contact are Set of Proofs:

Twitter Proof.

Email Proofs

Who

Conclusion

Add a reputation system that can contain abusive activities.

Object Capabilities to improve the security and performance of the network.

(together with an efficient Pub Sub gossiping and peer exchange protocols should be enough to provide with a Robust and Open Seed Web Network)