Sufficient Decentralization for Social Networks
varunsrinivasan.com
varunsrinivasan.com
I think, the Torus/web3auth people do it.
our recovery system for Farcaster has a few more bells and whistles, and you can read about it here: https://github.com/farcasterxyz/protocol#33-recovery
This isn't true though?
If I go out camping for a week and the recovery address transfers my identity, I won't be asked to approve; it'll simply go through after waiting 3 days.
The fundamental problem with keys is that they are files. You can't exactly memorize one, not without torturing yourself. You have to store them somewhere extremely reliably but at the same time completely secretly.
Self-hosting is possible with ActivityPub as well, but without sacrificing the user-friendliness. I can already see someone saying "what do you mean I have to start a new account after my private key leaked".
the key insight is that smart contracts can be used to transmute keys from single points of ownership into a distributed set of permissions.
you can compose a whole set of recovery systems with this primitive - key B could be your ledger or it could be a friend or it could be a third party service that offers "recovery as a service" where you have to call them and prove your identity before they will recover it back to you.
Well 12-word mnemonics help here right? It's imperfect, but certainly is as good as most 2FA implementations use for account recovery.
There are alternative approaches people are trying too. For example Coinbase[1] is trying a MPC approach where you delegate two (or more?) people known to you and if they agree it can recover your account.
But this is done using secure multi-party computation so the unencrypted key is never stored - it is only decrypted by the person doing the recovery when all the other parties agree to provide their tokens.
[1] https://blog.coinbase.com/threshold-digital-signatures-1d467...
A phenomenon sometimes referred to as the Lindy effect:
https://en.wikipedia.org/wiki/Lindy_effect
I'd be picking this time-tested tech as a foundation over anything else being pitched these days (who knows what their longevity will be).
Can you give some examples of acceptable account recovery systems?
Do they involve either giving up privacy (with government-issued IDs, for example), or delegating the problem to another system like email?
If email is an acceptable system to base account recovery on, then couldn't users just store their recovery private key in an email sent to themselves (or saved as a draft)?
Sometimes, yes. But then presenting a government-issued ID is kinda inescapable — this is also a requirement for participation in crypto. You can't buy cryptocurrency without KYC. And you sure as hecc need some sort of tokens for these "fully decentralized" identity schemes because they inevitably are a cryptocurrency with extra functionality duct taped to the side.
> or delegating the problem to another system like email?
That's also an option.
> If email is an acceptable system to base account recovery on, then couldn't users just store their recovery private key in an email sent to themselves (or saved as a draft)?
And if their email account is broken into and the private key gets into someone else's hands, how exactly do they prevent potential impersonation without starting a whole new online life, ideally without their followers even noticing?
I've not actually used BrightID[0], but my understanding is that you can use it without needing to buy any of their tokens. So it's more like a web-of-trust identity scheme with a cryptocurrency duct taped to the side. (Also I think that buying cryptocurrency without relying on a government-regulated business is probably more common than you're suggesting).
> if their email account is broken into and the private key gets into someone else's hands
This is the same problem that all existing social networks (and probably some government services in some countries) are already vulnerable to. I think a decentralised social network can offer meaningful improvements in user freedom and privacy without also solving every other online/computer security problem in the world.
> starting a whole new online life
In the case of BrightID, you can set up "social recovery"[1] which uses the social graph to allow you to regain access to your account.
[1] https://brightid.gitbook.io/brightid/setting-up-social-recov...
You can walk back on the security preventing account recovery by giving your keys to a third party. This is essentially the same as not having the security guarantees in the first place - and it's optional and you can choose who to give the keys to!
I am working on a project where this is a very definite possibility: https://stamp-protocol.github.io/#arch-recovery
I think anyone believing otherwise should spend a few months as front-line tech support dealing with forgotten passwords and then (perhaps) reconsider.
There are a lot of issues with DNS - fights over limited names/squatting, per-country rules depending on TLD, unreliability of registrars (see the thread every 6mo "what registrar should I use" with horror stories about every single one), and the fact that once you've chosen a name it's hard to change. I'm not going to claim that cryptographic keys don't leak into UX because I don't know, but I'm not sure what experience you have to guarantee they do. The only system I know of that heavily relies on keys is cryptocurrencies, which aren't social networks and are only one example (and TBH seem to be doing alright in the UX department).
Account recovery essentially means you have a backup method to gain access if you lose your key or it's stolen. There are many ways to accomplish this, many of which work fine with public key crypto systems: 1. If you're just worried about losing it, backing up your primary key, 2. A backup master key/subkey system with revocation, 3. An opt-in service that manages network access for you (including your keys) and provides human recovery mechanisms. The latter is essentially what you get with non-crypto methods but allows decentralization.
Better UX and better security.
''' Successful social networks are usually built around a new communication primitive. Facebook had the wall, Twitter had the 140-character tweet and Snapchat had the ephemeral message. The idea maze of things you can do with decentralized identities, blockchains and zk-proofs is large, weird and interesting enough that there are probably many primitives waiting to be discovered. Decentralized social networks should explore this as a way to attract users. Offering a product experience that doesn’t yet exist is far more compelling than a clone of an existing network. '''
This is the quote.
For the decentralized social network, it needs to be 10x better than existing social networks. I have a few ideas, currently playing around in this space.
I think a decentralized social network can at minimum bring 10x the value to users/creators that existing social networks do.
As a quick example, look up how much Tiktok/youtube make per view. Tiktok is something like 2 cents per thousand views. Per thousand views.
I also think a decentralized social network can be much more profitable than a centralized network.
Maybe what will evolve the space is automatic translation from any possible format to any other format using AI.
You don't need to manage a server or store anything in any particular way in any particular place.
Instead, you expose whatever you want in any way you want, whether that's uploading a video to some big tech host, or exposing a bunch of XML over FTP, or a RESTful endpoint that serves binary encoding pictures of cats.
My user agent scoops up everything and presents it to me in a way that I like.
There would need to be some creative ideas involved for, say, "replying" (hashes? webmentions?)
In other words, maybe innovation on the demand side is where the fun is.
</bad-idea>
'''My user agent scoops up everything and presents it to me in a way that I like.'''
I think this is close to what the future looks like.
For example, it rattles me that no matter what app I am watching 'videos' on I have different options. Some I can watch 2x speed. Some I can tap the sides to go quicker through. Some if I tap it mutes. Some if I tap it stops the video.
All of this for the same type of content.
Insanity.
Not to mention even within certain apps like Instagram is just brutal. For the same content type - videos - they have like 3 (?) different ways to view it.
I get that they can display suggestions for what you should watch next and keep data on how much you watch or how often you pause it or whatever. But if we're going to create a decentralized social network, then maybe we could junk all the metrics that a centralized social network keeps on their users. Let it evolve organically, rather than in a way that best suits one particular small group of people, and give people back their privacy as well as their autonomy.
Edit: rewrote an awkward sentence.
one way I am thinking about it right now is do away with the idea of "apps" entirely. Think about it more in the sense of "intents".
If anyone is interested in building in this space, my email is in my profile! Looking for cofounders :)
Easier said than done. Facebook, Google, Twitter and Co. like to gatekeep their data and don't allow third party clients access. So you don't just need an AI smart enough to capture the data and reshape it, but also one smart enough to pass whatever CAPTCHA they throw at you, which will likely get progressively more difficult the more popular your tool gets. And of course they'll lock your account when you try, so this is at best a read-only participation in the social network.
The problem has shifted over the last decade, it's no longer about fixing a broken Web, but about a large part of the content no longer even being a part of the Web. Everything is either moving to Apps or getting gated behind login screens and ToS.
That said, CAPTCHA can be defeated by changing the landscape of incentives in favor of giving the consumers what they want.
The consumers will use these user agents when they get so good that they're better than the alternative and/or it's easy enough to "dual boot".
Once one of the above happens, then there is a greater incentive for everyone to make their content available e.g. by uploading to public Google Drive folders.
What I'm trying to get at is that the dream of decentralization can happen perhaps sooner if we focus on building the client side of it as a layer over the existing structure, instead of trying to supplant the current server side structure.
> can be much more profitable than a centralized network.
The money comes from advertisers, not from users or views. Advertisers perennially spend the same amount (~1% of GDP, barring periods of war) to advertising companies. The pie is not expandable and is eaten by google and FB.
If the words "decentralized" are anywhere in your marketing of a decentralized social network, you have already lost ;p
I didn't intend to mean that by making a social network decentralized it would be 10x better. What I mean is, that by making a decentralized social network it opens up possibilities that are just not possible in a centralized network (or at least very hard).
And those possibilities are real tangible benefits to users/creators that don't directly have anything to do with 'decentralization'.
If we now stop and look back over the last 15 years we see
1. Art has degraded as Artists are optimizing their work for share-ability and a quick consuming audience.[1]
2. Social networks are pulling us further apart than bringing us together.[2]
3. Don't get me started on influencer culture[3]
[1]https://www.youtube.com/watch?v=BPWkHtFPHH8&t=645s
[2] https://www.nature.com/articles/d41586-022-00805-0
[3] https://techcrunch.com/2022/01/10/hype-house-creator-economy...
His lead developer Dmitri Zagidulin agreed to work with us for a while but ultimately went on to help create the DID standard at the W3C. And Daniel Buchner at Microsoft pushed for years to make ION (sidetree protocol) which Jack Dorsey’s Web5 is based on.
If you want to see truly decentralized and working social networking, here are some examples:
All built on our framework: https://qbix.com/platform
The eventual decentralized Web2 ecosystem can look like this, and there is no blockchain: https://qbix.com/ecosystem
Why we need it: https://qbix.com/blog/2021/01/15/open-source-communities/
Questions, comments and threats welcome :)
Taking a look now, will drop some questions if they come up!
I am following TBL's SOLID work as well!
Edit: I thought I had reached the bottom of all the decentralized tech out there after a few months of research. qbix hadn't come up, looks really neat!
> two users can find each other and communicate, even if the rest of the network wants to prevent it
and use centralized methods where it does not compromise on this constraint (e.g. efficiently storing/retrieving data about posts).
We are building standards for open distributed social media systems, with identity and security built in, and absolutely no centralized management. Everyone can run their own communities, while still having managed identity, and without a single click sending content to everyone in the world.
Before DevOps was fully a thing, a coworker and I sketched out a (too-complicated) service-discovery/bootstrapping program using DNS + PGP, and what we thought was a super-clever signing scheme for trusting automatically-spawned processes from our central platform tool. (Turns out, there are better ways)
The ability to build trust a la PGP Key Signing Parties, but at scale - and use them in a polycentric way could change a lot of things for the better.
For example, instead of ever giving out my IlluminatiFreedomCoin address that's tied to my SSN, I could produce a Venn diagram of users who have signed my keys for FB, Twitter, HN, etc. to suggest that I am who I say I am. Not foolproof, but probably sufficient to add a user account or keep a Craigslist deal moving forward, until I can authenticate IRL.
We won't notice it really until it hits a certain tipping point, which will look a lot when interoperable email started to take off (mid-1990s or so)
an aside but does anyone else remember when everyone was telling you their AOL Keyword?
BitTorrent's DHT never had this problem. BitTorrent existing and working IS the value.
"We have a working social network" is likely sufficient value to motivate users to host things.
I am skeptical of the need for filecoin-like systems in the first place. If all you have is a hammer, then every problem looks like a nail.
Here is a comment I made yesterday on the matter:
>Instead of "liking" or "upvoting" a post on a centralized forum, why not "rehost" or "forward" a post on a decentralized forum: essentially seeding it like in BitTorrent or "pinning" it in IPFS. "Followers" of a user donate their storage and bandwidth to them, combating bureaucratic attacks like delisting and DDoS against popular users.
That's where Filecoin comes in.
But yes, I think the Filecoin model is to heavy weight right now.
My friend uses private trackers and his download speeds are unbelievable. But even on public trackers the download speeds are quite good. It does not take that many seeders to serve even a giant video file like an HD film, because even if upload speeds are a fraction of download speeds, the total upload bandwidth will be multiplied by the number of seeders. In fact, even an adequately-seeded torrent is orders of magnitudes faster to download than a youtube video or HTTP file for example.
People like to keep backups of their favorite creator's works. On youtube, when a popular youtube video is taken down, it will usually be reuploaded by fans. From this, we can probably surmise that maybe 1/100000 viewers will archive a given video. That's basically enough to keep a video alive forever on bittorrent, even throughout times of peak viewership as downloaders will also seed the chunks that they have.
No, people do not have crazy upload bandwidth. A private BitTorrent tracker group is immaterial. They're maintaining ad hoc infrastructure just by leaving a machine on 24/7 and maintaining favorable U/D ratios. Many groups also maintain seed boxes.
This doesn't apply to the population at large. Most people are on phones or laptops on WiFi. They're not running 24/7 and in the case of phones a background service isn't even viable. Many people are on CGNAT and can't "serve" data without some intermediary infrastructure.
As for retention, that's a pipe dream. A torrent more than a few years old may as well not exist unless it is extremely popular and maintains its popularity. There's innumerable dead torrents with no seeders.
They don't need to serve 24/7, they just need to be available 24/7. Do people not have their phones on and connected to the internet 24/7 in case they receive a message? For social media, most people just share text posts, pictures or a few small videos. BitTorrent is a worst-case scenario where it would be only used for large files like movies.
>Many people are on CGNAT and can't "serve" data without some intermediary infrastructure.
There are ways to get around CGNAT without STUN/TURN.
>As for retention, that's a pipe dream. A torrent more than a few years old may as well not exist unless it is extremely popular and maintains its popularity. There's innumerable dead torrents with no seeders.
This is desirable behavior in social media. Popular content will have longer retention, unpopular content will have shorter retention. Web forums like this one emulate a "fake" version of this with the weighted voting/time system that favors upvoted posts and disfavors old posts.
A device able to receive a notification is not the same as listening on a socket 24/7. Push notifications on mobile go through the platform's push notification system lest they kill the device's battery. A push notification doesn't wake up a device and power up all the radios to stream masses of data.
Apps on mobile devices can be killed at any time, they're extremely unreliable as servers of content. Laptops are little better as servers of content.
I don't understand why you'd want social media content to only favor popular and recent content. Why would you want a built-in memory hole in the system?
Bitcoin is worth a trillion dollar. Meanwhile 20+ years of effort into creating P2P networks has resulted in pretty much nothing. No Linux distributions are hosted on P2P. No source control is on P2P. No messaging. Nothing of significance. Just a few tech demos here and there.
Proper incentives can make all the difference and given the utter failure of getting any non-incentivised P2P off the ground in the last two decades, I think it's safe to say, it will be necessary. I don't see much point in repeating what hasn't worked in the past.
> and they may host others' data for free like in BitTorrent
BitTorrent isn't free. All the fancy piracy sites have share ratios. The public stuff more often than not has 0 seeders, lots of leechers and is just a lot of dead torrents in general. You are better off just using a centralized share hoster. Even your average Linux distribution agrees. BitTorrent might still be offered for ISO downloads, but it's hardly ever the default anymore, it's all back to plain old HTTPS.
Bitcoin is """"worth"""" a trillion dollars. It's not a free money machine, It's is a shitty payment system, not a P2P network unless you are sharing your blog over OP_RETURN.
>Meanwhile 20+ years of effort into creating P2P networks has resulted in pretty much nothing
IDK bittorrrent and IPFS just work without inventing a free money machine.
You can download linux install disks over BitTorrent.
>No source control is on P2P
With a system like Git there is no need for such a centralized system. Each user has their own copy of the tree.
>BitTorrent isn't free
Bullshit. It is free. Go on TPB, it's still up. I use it every day and it is leagues faster than any alternative.
Or to put it another way: No one, at any point, put that much money into the system.
Also, it costs our environment a lot. Soon I would join the ranks of luddites, if science and anything digital was not that much more interesting to me than plainly surviving.
And then you inadvertently host 'terrorist' materials and get 25 years in jail.
People are trying to redesign 'social networks' with no fundamental understanding of what they are, how to run them or the very real risks involved.
Necro-posting (bringing up old discussions) becomes a viable option, as does scouring through old information.
What is more interesting to me, is utilizing this functionality for something beyond a social network, something more productive like an ERP system, yet allowing the social aspect of collaboration improve such a platform.
Server offering person Alice: If I want to use the service, I want to use the service, not get cryptocoin shares. And I usually want stuff on the internet for free.
Server or service using person Bob: If I want to make money by hosting, I need someone to pay for my hosting-mined coins.
I don't understand as to who in this overview is willing to pay for a place on the blockchain with fiat currency? Someone needs to pay Alice for the efforts she has put into hosting, but who transfers something worth real money to here?
Even the author stated that he wants to use a blockchain for user identification, not monetary incentive. But perhaps he means identification is what is granted to you, no money involved. But that can't be it either: So you can host a server, to gain the right to use the server? No, that is the status quo.
Lets take a look what happens if you do not run your own server: So you host a more or less public server for others as the scenario proposed here. A client connects, and sends that that shall be stored in a blockchain (i.e. append only, publicly distributed database) to upload [1] and later confirm their identity. When not running the server, who says that the server is not malicious and uses a different identity for the federated network than it displays to the client that connected to it?
[1] Something like the the Web of Trust exists between existing servers, or the server will have to spend a resource like having coins or a history of already signed up users to gain the right to add user identities to the blockchain? The Proof of Stake/Work paragraph above probably now again applies for true "trustless" systems, that require full client (i.e. technically server node) equals user identity.
People might not care about the technical implementation details. But they do care about what the implication of those details would be.
what distributed database would let you own your identity without any third party party being able to take it away from you?
that's a necessary condition for sufficient decentralization, and the only distributed databases capable of achieving such guarantees are L1 blockchains.
Owning a private key file when signing transactions allows to prove your identity to other parties. That is, what a blockchain uses to map identities to accounts/wallets, too.
Having a consensus protocol does not provide identity proving, but the eponymous censensus is based on a share of either state or computational power.
And state is just a database. State that decides what goes into the database is a recursion, voila an example would be Proof of Stake. Or as censensus protocols go, other names exist for the concept of proof of previously-done-arbitrary-things, which allowed you to mention a share with you cryptographic signature (i.e. hash derived from your private key) in the append-only database. Cases like a "plant a tree" eco-coins.
Also, to see the bigger picture on
> What distributed database would let you own your identity:
from a technically more complex angle: Tim Berners-Lee proposes a DRM system for users to own their content, instead of using this technology against user liberties. That would include owning your identity and enforcing your will on you intellectual property. I found these plans not feasible, yet, but at least people who know about cryptography still research the topics of user rights and P2P networking.
The article does indicate a blockchain is undesirable
For another decentralized social network (that runs entirely without a blockchain) check out Scuttlebutt (not affiliated)
To move to a free market, there just has to be something like Wordpress for Web2. Forget Web3 and blockchains (which don’t scale) but we need at least federated software (Matrix, Mastodon) but with a lot more features that we have come to expect from Facebook, Telegram et al
we've also been building a sufficiently decentralized protocol called Farcaster, and you can check it out here: https://github.com/farcasterxyz/protocol
we've also built the first clients for this protocol, which are still in beta. if you have an ENS name and are interested in trying them out, DM me on twitter https://twitter.com/varunsrin
Look at nostr https://github.com/nostr-protocol/nostr
There's also Revolver https://blog.freespeechextremist.com/blog/revolver-kickoff.h... it is in development and very interesting, will be available to the public for testing Soon™ from what I gather.
It seems to me sometimes that a lot of these posts come from people that don't really interact with the average social media user very much. People are willingly giving all their data to Facebook, Tiktok, etc. They do that because in reality... they don't care all that much!
How do you expect these kind of people to care about decentralisation? I think the closest we are to a good middle point is stuff like mastodon, but federation is not perfect. Will it not be reasonable for people in the future (if mastodon becomes really popular) to simply default to the biggest server out there?
I think the best we can do is come up with standards for data-transfer between sites as well as basic communication tools... pretty much what activitypub has tried to do. This would go a long way to ensure people are actually capable of moving, not being locked in is I think the key to ensuring decentralisation.
In a few words: people don't care as much as we'd like them to and that's not really a technical problem. Because of this, it is not possible to solve this problem by adding any extra inch of complexity that doesn't come with substantial benefits to users. And I don't think adding blockchain-based market mechanics to it is really going to solve the problem as blockchains add a huge amount of overhead to the problem.
but if you've figured out a new social network, building it in a decentralized manner today might give you very strong second order benefits. and its now possible to do this in a way that doesn't compromise the user experience.
If it's the ability to publish and subscribe to content, why not just do some fancy version of RSS?
IMO, a better question (two questions) is where is RSS now and how did RSS get there?
If you look into the specs for decentralized identifiers (DIDs), they don't define how a "method" needs to implement its interface.
There are solutions that use blockchains (Ethereum), others use DAGs (IPFS, IOTA) and some are even static without any server required.
The bad side is the barrier to entry (a hobbyist-level knowledge of internet protocols, and the ability to either self-host or seek out a managed server). It would be nice for people to be able to just install a program and be able to both write and read things. This is something that will require some protocol and application design to keep decentralized, but there's no reason to believe that a blockchain is needed, or even helpful.
if you squint, the protocol i've described is really a fancy version of RSS. In fact, the original brainstorm doc for this idea was titled RSS+ :)
I just subscribed - by RSS - to your blog. I'm looking forward to read more about RSS.
You need to be connected to the Avalanche Fuji Testnet in Metamask (there are some instructions on the site for how to set that up). Feel free to leave us some comments, feedback and suggestions here or on the app :)
No one owned all the servers for either of these. The problem came with moderation versus spammers and trolls.
The problem still exists with the centralized social networks, although theoretically it should be easier for them to deal with due to centralized identity management. It isn't.
>ActivityPub doesn’t provide a way to use a managed host without compromising decentralization.
what does this mean?
i don't get this. if i am hosted on mastodon.social and i want to talk to cawfee.club or a pleroma instance, don't i just message them and the services resolve themselves using activitypub?
what does managed hosts mean? you mean mastodon.social as an example?
what is this
The compromise of decentralization is that if you have an account on mastodon.social, they can censor you (for good or bad reasons), or the people you'd like to follow. You can move to another instance, but your identity has to change (though at least now you have a decent likelihood of being able to transfer your social graph along with you). And because discovery of instances is not perfectly frictionless, people tend to just sign up for the big instances (like mastodon.social).
All that said, any solution is also going to introduce new problems. And there's absolutely no reason to think that adding blockchains to the mix is going to do anything but harm.
i am assuming if i want to block a bad actor on the chain, i note that and later whenever someone queries their address, my note is shown so what is it solving?
>And because discovery of instances is not perfectly frictionless, people tend to just sign up for the big instances
the solution exists, sure it might not be frictionless as of now but its not like it is a fundamental problem?
yeah, blockchain is not the solution.
>The compromise of decentralization is that if you have an account on mastodon.social, they can censor you
admins of mastodon.social can but so can any other instance so how is that a bad thing? how do we equally fight spammers/bad actors and at the same time prevent good people who have been banned to say their words?
isnt good/bad inherently a subjective issue that is to be decided by a person? activitypub gives users and admins the power to decide so what is the problem there?
i am not questioning you specifically, just asking
Not only don't you need blockchains you can phrase it more strongly, it renders the entire thing impossible. A social network needs a messaging protocol, data ownership should be private and state local or else it doesn't even scale.
Pushing the entire history of a what is p2p, private communication through a global state machine is entirely antithetical to the use case. Imagine every time you talk to your neighbor you inform the entire country first, there's no point.
Start with the use case, not the tech. I joked that facebook was invented as a way to let people know you went to harvard without having to say you went to harvard. It started by solving the h-bomb problem whereby having a thefacebook account they created an online way to say you went to school "in Boston," which they then extended to "in Newhaven," "New Jersey" and then to any college affiliation at all (.edu domain requirement). That signalling was the use case. It expanded to include people without that status but wanted access to it, and the only way to "win" at facebook was either an Ivy school education or becoming a celebrity. Once it opened up to everyone else, it finally became the cruel spectacle it is today, and the source of our cultural discord.
A decentralized social network isn't a protocol problem. The hardest thing to face is that nobody wants to join decentralized social networks because they confer no signalling benefits or meaningful status to users the way central ones did. It wasn't an artifact of the technology that made the handful of social networks successful, it was their use case.
Clubhouse almost replicated it, but like any elite organization, 80% of the game became not-being the person who recommends someone off brand or un-cool, and so it became contrived and over gatekept, and its growth atrophied from the anxiety.
Git is probably the closest thing to a decentralized social network that confers tenuously analogous status to what FB originally did, where instead of your school tribe and pictures of your butt, it's a competence graph with localized hierarchies.
It's like we can solve every problem except how to become attractive to users, probably because we're indexed not on being attractive, but on emmulating what we percieve as smart and powerful and solving a problem, which is the very thing repelling users from decentralized social networks: The products are self-defined as inferior to the problems they oppose, and not as sharing access to a desirable resource - like powerful tribes and butt pictures. Nobody wants to become like decentralized social users.
Twitter's blue checks are similar, where you can affilliate with people close to the source of official power narrative by "following" them. If they follow you back, it's an endorsement of your identity and status. If I join a decentralized social network, what do I get? A bunch of anonymous fugitives pushing newsletters explaining why it's someone else's fault they're unhappy.
This is a message of mercy to decentralized social projects. Focus on the use cases and build things for specific people you sincerely like and who sincerely like you back, and not anti-solutions to anti-problems for aspirational audiences using obfuscated proxies to simple experiences.
> A decentralized social network isn't a protocol problem.
When the author talked about "the ability to claim a unique username" I was waiting in joy for him to start talking about domain names. But he didn't...
Then the author talked about "scaling networks" and I was hoping he would mention the internet... and he sort of did.
How do you stop spammers and bad actors in general.
> the ability to claim a unique username
Which would require a centralisation, presumably. We have things like OpenID, but that hasn't really caught on.
What we want is internally inconsistent. We want both unique identifiers (this is the "real" "blippage" making this post), the possibility of multiple identities, and the possibility of anonymity.
We also want openness, but are likely to desire censorship for legitimate reasons, too.
Just how are we going to square the circle?
Li'l update: I see NFTs being mentioned, which sounds a bit band-wagony to me. In the Gemini protocol one creates TLS certificates. The Lagrange browser can generate a cert quite simply. So in at least some sense, isn't the identity issue "solved".
Another update: there's also the issue of discoverability. Centralised networks make discoverability easy. It's not insurmountable with decentralised ones (people are willing to host aggregators), but it is harder.
https://slashdot.org/faq/karma.shtml https://slashdot.org/moderation.shtml
The same goes for democracy and politics, how to prevent bad actors from gaming the system and acquire illegitimate power.
When moderating a 5000 person topic focused community I used a ruleset which was easy to understand. Along the way I tweaked the ruleset to defend against bad actors using the rules against me.
That idea won't get traction because people don't want to pay for a social network. But damn do people love "reality internet" - outrageous content, reaction videos and otherwise fabricated "content" I equate to Reality TV like "The Real Housewives of ..."
In my opinion, it should also be closed in the sense of no viral/global messaging. With zero need for advertising money, you don't need eyeball time or to be promoting controversial content above people posting pics of their dinner. Let people be social about stuff they are interested in and connect with people they know. That's the other bit - you can't randomly connect/view content by people not in X degrees of separation from you.
Maybe there is some middle ground where its free for users and advertisers can pay to advertise but there won’t be the viral content that advertisers want. One approach could be the local groups that naturally form - book clubs, mom’s groups, gamers, etc. could be tagged as such so an advertising model can happen.
Perhaps social interaction could be thought of as sort of like food, and social media could be thought of as sort of like junk food -- maybe this paid social media site could be thought of as a less-damaging form of junk food. The metric for success could be something like <user satiation>/<wasted time>.
> Which would require a centralisation, presumably. We have things like OpenID, but that hasn't really caught on.
The article addresses this. We already have a decentralized, credibly neutral identity layer with unique names in production (and pretty wide use, at least in the web3 space): Ethereum Name Service.