W3C home > Mailing lists > Public > public-credentials@w3.org > March 2021

Re: SDS/CS WG: Trusted Content Storage (TCS Stack): Decentralized Twitter (Dewitter) App Scenario - completed and posted

From: Gabe Cohen <gabe.cohen@hey.com>
Date: Mon, 08 Mar 2021 18:44:41 +0000
To: Dmitri Zagidulin <dzagidulin@gmail.com>, "sds-wg@dif.groups.io" <sds-wg@dif.groups.io>, W3C Credentials CG <public-credentials@w3.org>, Daniel Buchner <daniel.buchner@microsoft.com>, "Michael Herman (Parallelspace)" <mwherman@parallelspace.net>
Message-ID: <573e5fe5306c4bfbe15be84616d325d19ae6e531@hey.com>
Cool idea. I had it too, which is why I registered the did:twit method
and created a minimal cli to sign and verify tweets. Mines much less
thought through. <https://didtwit.io/>

If there’s an open source work that needs a hand I’m happy to help - or
expand my project.

Gabe

On March 8, 2021, "Michael Herman (Parallelspace)"
<mwherman@parallelspace.net> wrote:
> 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…
>
>  
>
> 1. Like a Tweet
>
> There have been 2 subsequent revisions to the Dewitter app scenario
> document.  A Change History section is tracking the changes. 
>
>  
>
> Check out https://hyperonomy.com/2021/03/05/trusted-content-storage-

> tcs-stack-decentralized-twitter-the-dewitter-use-case/
> <https://hyperonomy.com/2021/03/05/trusted-content-storage-tcs-stack-

> decentralized-twitter-the-dewitter-use-case/>
>
>  
>
> Have a great week,
>
> Michael
>
>  
>
>
>
>  
>
>  
>
> From: Michael Herman (Trusted Digital Web)
> Sent: March 6, 2021 7:09 AM
> To: dzagidulin@gmail.com; sds-wg@dif.groups.io; Credentials Community
> Group <public-credentials@w3.org>; Daniel Buchner
> <daniel.buchner@microsoft.com>
> 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
>
> <https://hyperonomy.com/2021/03/05/trusted-content-storage-tcs-stack-

> decentralized-twitter-the-dewitter-use-case/>
>
>  
>
> 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.
>
>  
>
>
>
>  
>
> Best regards,
>
> Michael Herman
>
> Sovrin Foundation Self-Sovereignist
>
>  
>
> Self-Sovereign Blockchain Architect
>
> Trusted Digital Web
>
> Hyperonomy Digital Identity Lab
>
> Parallelspace Corporation
>
>  
>
>
>
>  
>
>  
>
>  
>
> From: Dmitri Zagidulin <dzagidulin@gmail.com
> <mailto:dzagidulin@gmail.com>>
> Sent: March 4, 2021 12:49 PM
> To:
> sds-wg@dif.groups.io <mailto:sds-wg@dif.groups.io>; Credentials
> Community Group <public-credentials@w3.org <mailto:public-
> credentials@w3.org>>
> Subject: Reminder and Agenda for Confidential Storage Spec Call - Mar
> 4 2021
>
>  
>
> Dear all,
>
Received on Monday, 8 March 2021 18:44:58 UTC

This archive was generated by hypermail 2.4.0 : Monday, 8 March 2021 18:44:59 UTC