What's SamOS?

[sacha-l]

Just a brain dump based on questions I have about SamOS.

---

What's the simplest story around SamOS?

1. You've created your DID
2. You can move to any website or web apps, e.g. Youtube
3. Whatever data the website requires, you'll provide or request access for it to allow you to access it
4. You can revoke access to your data after some time

But..

• Why do I need access to a webpage? Is it just for webpages that required authentication?
• If SamOS uses a blockchain, then all my details are public. Is there a work-around to give some privacy guarantees?
• What else can I do with SamOS as an end user? And as a developer?

[thewoodfish]

Web pages are actually unnecessary, as per what is to be done now. There's Samaritan(what is it) and Samaritan to the world(how it can be used). I think focusing on what it is, is what should be dealt with. Second question which is a fantastic question: A Samaritan is a digital personality. And in my head who we are is defined by our credentials and what we own. So digitally for now, a S should contain self-sovereign credentials and data(e.g report card). These are stored on dStorages of users choice, (would try to implement for crust, storj and filecoin) and can be marked as private/public. Public credentials/data are stored onchain and can be searched through and (maybe) indexed.

[thewoodfish]

The third major thing would be adding your credentials issued by another chain to your S (attributes) which can also be marked as public or private

[thewoodfish]

Your third question, hmm.... I can't tell yet, what i know is your S would be your digital persona with your credentials and data. The actions to perform would show itself e.g sending credentials, searching for S's with specific attributes (maybe using origintrail), etc. Can't say, but i know that junction, people would have many lots to say and say

[sacha-l]

Thanks! let's keep this thread open so that we can keep adding here for when we're ready to create some documentation (which I can help with of course:)).

A Samaritan is a digital personality. And in my head who we are is defined by our credentials and what we own.

This hits well. SamOS is therefore an OS for helping a Samaritan manage their identities and access to dStorage layers or other services they might be using.

[thewoodfish]

. Creating a command line to add credentials to ones S root. ac [link] the link would contain a JSON that looks like https://buylink.app/cred.json

If link is not given, what appears is an explicit modal to upload a JSON doc.

The attributes required are attr, personal and mode.

attr stands for the credentials and relationship. personal says whether the credential Is personal, e.g the email of the S. mode indicates whether the credential is public or private. The default is public.

Then the S protocol creates a great JSON-ld doc/credential with what was given.

[thewoodfish]

The credential is always self asserted, which cannot be trusted. Then the user can allow other S or protocol assert them. More on this soon...

[thewoodfish]

Thanks! let's keep this thread open so that we can keep adding here for when we're ready to create some documentation (which I can help with of course:)).

A Samaritan is a digital personality. And in my head who we are is defined by our credentials and what we own.

This hits well. SamOS is therefore an OS for helping a Samaritan manage their identities and access to dStorage layers or other services they might be using.

Yes, thank you 😊😊

[thewoodfish]

Something i'm thinking.... To aid search, indexing, grouping etc, really, the type of credential would help. So i'm thinking of standardizing a list of credentials, and more could be added (maybe by voting, maybe). Types of credential e.g EducationalDegree, MaritalStatus, HealthStatus, WorkExperience, PersonalInformation etc. But they should be quite general, then the user is free to add attributes, but at least, has narrowed down the domain