#ShowerThoughts pure #P2P networks don't really make much sense for public #SocialMedia. It would be a ridiculous waste of storage for every single member of a subReddit to have a complete copy of its history on their own hard drive, let alone every subscriber to a YT channel. They make a lot more sense for private #SocialNetworks, among family and friends, or colleagues, in which the total data is smaller and you ideally want it stored locally anyway.
@kravietz > You only see public key ids for people who are too far from you, but their id was references in responses
You kind of answered your own question ;) Also, the Jami namechain allows users to claim a unique human-readable username, without a centralized ID server. AFAIK in SSB as it works now, you'd have to check the public key of a post to be sure it was sent by this "strypey", not another user calling themself "strypey".
@kravietz ... OR, any SSB app that comes across a post with my public key could check that key against the ID namechain (like a decentralized keyserver) and assert with certainty that it was posted by 'strypey'. Just saying ...
@kravietz > if a SSB client sees a signed message "this is my new account" to somehow link them or auto-follow
... doesn't do anything to allow users to claim a unique username across the network.
> because the existing model works well nobody really cared
This kind of thinking is how #IRC got overtaken by #Slack. IRC "works well" for the existing userbase, so the #UX doesn't get improved, so new users go somewhere else.
@kravietz with Jami, the account isn't stored on the blockchain, only a record that associates a certain account ID with a certain username. If you delete your account (or lose access to it), that username effectively points to nothing.
@kravietz the blockchain is the means of ensuring uniqueness of usernames without a centralized nameserver. I don't understand why this wouldn't also be useful on SSB or any social network, especially if it had 1000 times its current user numbers.
@kravietz the blockchain is the means of ensuring uniqueness of usernames without a centralized nameserver. I don't understand why this wouldn't also be useful on SSB (or any social network), especially if it had 1000 times its current user numbers.
@kravietz it would require SSB apps to include a node of the namechain (if they want to implement the feature) and check any unfamiliar public keys against it whenever they download new posts. Like the way web browsers include code to reference the #DNS system, so they can map the domain name of a website to the IP address of the webserver that hosts it.