Open mwherman2000 opened 3 years ago
Here's what an EDV-based, fully decentralized Twitter (code named Dewitter) platform might look like...
Here is the full description of the 50+ assumptions and use cases that comprise the current version of the Dewitter app scenario: Click Trusted Content Storage (TCS Stack): Decentralized Twitter (Dewitter) App Scenario
NOTE: In a subsequent variation of the baseline fully decentralized use case, the addition of centralized servers and server-hosted EDV Server Instances will be considered. This variation is called “Distributed Twitter (Distwitter)” because it runs across multiple centralized servers in addition to local, personal EDV server instances; that is, Distwitter is not fully decentralized.
I think of decentralized use-cases in terms of Separation of Concerns. Twitter, like other platform business models, combines a bunch of concerns into a platform to get platform lock-in. For example:
Decentralization of twitter could mean making any and all of these seven activities separable and substitutable.
Using Twitter: https://help.twitter.com/en/using-twitter
Types of Tweets: https://help.twitter.com/en/using-twitter/types-of-tweets
Authz use cases: https://help.twitter.com/en/using-twitter/twitter-conversations
Liking Tweets: https://help.twitter.com/en/using-twitter/liking-tweets-and-moments
Notifications: https://help.twitter.com/en/managing-your-account/notifications-on-mobile-devices
Policies: https://help.twitter.com/en/rules-and-policies/twitter-limits, https://help.twitter.com/en/using-twitter/mentions-and-replies
Glossary: https://help.twitter.com/en/glossary
Scrolling through a Twitter feed
[LARGE APP SCENARIO] Decentralized Twitter (Dewitter): what does an EDV-based, fully decentralized "Twitter" platform look like?