Re: SDS/CS WG: Trusted Content Storage (TCS Stack): Decentralized Twitter (Dewitter) App Scenario - completed and posted
Michael Herman (Trusted Digital Web)
What is the most interesting use case in Decentralized Twitter (Dewitter) app scenario so far? …the use case which might have the greatest impact on the architecture of an EDV Server Instance and EDV Data Vault?
Believe it or not, it’s Liking a Tweet…
There have been 2 subsequent revisions to the Dewitter app scenario document. A Change History section is tracking the changes.
Have a great week,
From: Michael Herman (Trusted Digital Web)
Sent: March 6, 2021 7:09 AM
To: dzagidulin@...; firstname.lastname@example.org; Credentials Community Group <public-credentials@...>; Daniel Buchner <daniel.buchner@...>
Subject: SDS/CS WG: Trusted Content Storage (TCS Stack): Decentralized Twitter (Dewitter) App Scenario - completed and posted
As a follow-up to Daniel’s remarks on Thursday’s call: “it’s Decentralized Twitter!”, I’ve documented a fairly complete Decentralized Twitter (Dewitter) App Scenario with 50+ assumptions and use cases. You can find it here:
Trusted Content Storage (TCS Stack): Decentralized Twitter (Dewitter) App Scenario
The ink is still wet so it’s a great time to provide your feedback. If there’s interest, I’ll post a live version on Google Docs. The next step for me is to break the app scenario down into a list of fine-grained requirements to be voted on for the CS specification.
Below is a copy of the Dewitter App Scenario fully decentralized architecture reference model used as the basis for the above whitepaper.
The whitepaper also discusses a Distwitter app scenario that uses a distributed architecture that adds centralized servers and server-hosted EDV Server Instances to the decentralized Dewitter app scenario.
Sovrin Foundation Self-Sovereignist
Self-Sovereign Blockchain Architect
Trusted Digital Web
Hyperonomy Digital Identity Lab
From: Dmitri Zagidulin <dzagidulin@...>
1. IPR Reminder
3. Finish discussing remaining items on the ‘Division of Responsibilities between Hubs and EDVs’.
4. Collection of EDV features and use cases, by priority, from the community -- start discussion.
5. Issue review