2. M1S gains traction from hackers who don't want to be part-time sysadmins, but the first widely-used killer app for it is a social media front-end combined with a CDN. Self-hosted files and "publish once, syndicate everywhere" starts to flourish and Facebook begins to lose its position as middle-man to the web's social activity.
3. Bezos buys Keybase with spare change from his couch cushion and integrates it in to M1S; now all server-side apps, and the users thereof, natively have cryptographic identities.
4. Users begin to demand M1S integration from businesses that used to hold (and resell) their data. Widespread adoption from webapps cyclicly drives further adoption by users, making a M1S identity (if not heavy usage) almost ubiquitous.
5. With most client/server use cases sharing a single cryptographic auth network, the last vestiges of anonymity disappear from the web as peoples' username, real name, cryptographic identity, and checking account melt into a blob.
6. With their real identity attached to online activity, online activity becomes "activity", and, while toxicity is not eliminated, it is at least no worse than the real world.
(Crazy? maybe. But I am honestly surprised every day that I wake up and find out that Amazon hasn't made something like step 1 yet...)