Protocols != Businesses
A business that has lots of demand can buy its way out by raising money and directing lots of resources towards solving the problem. It also has the benefit of typically controlling all the infrastructure, so is able to replace the entire underlying stack.
A protocol cannot do that, it's dependent on volunteers, grants or companies that, often against their commercial interest, keep improving it in a mostly backwards compatible way. The amount of resource that can be mobilized is smaller and the upgrade process harder (a whole ecosystem has to move).
The most likely outcome imo is that companies will build very sophisticated scaling technology, that will likely not be open source so they can have a moat, and then dominate the end user market. Us nerds can still use the core protocol, but might not even be able to communicate with the majority of users.
E-mail is a cautionary tale, try hosting your own and still reaching gmail users reliably. Or try getting ICS files for flight bookings, airlines just set the google calendar metadata since ~everyone uses GMail+GCal. It's a bit different since the centralizing force for e-mail was spam and not scaling, but I think it's a close enough analogy.
Or look at the web stack, it historically evolved to become such a bloated monstrosity (because the inventors designed a document standard and we shoehorned it into becoming an application framework) that these days only companies with millions to burn can keep up with maintaining browser engines (and Google pretty much defines the direction of travel because Chrome is number one).
So when I worry about scalability it is out of a deep care for decentralization and not seeing all that energy invested go to waste by ultimately ending up in the same place we started at. If we don't consider decentralized scaling from the beginning, the non-ideological VCs pouring money in once it gets traction certainly won't.
elsirion /
npub1nc…rz5pa
2024-08-29 12:21:06
in reply to nevent1q…yrsg
Author Public Key
npub1nc0ynppqh37rtulr57xjqpzmfjp58xrd4ey8896ehn9j5flg33fszrz5paPublished at
2024-08-29 12:21:06Event JSON
{
"id": "ba838836d67fcacbdd49b41208e660eaa2d8217203c70a059848d15e97b51c6e",
"pubkey": "9e1e498420bc7c35f3e3a78d20045b4c8343986dae48739759bccb2a27e88c53",
"created_at": 1724926866,
"kind": 1,
"tags": [
[
"e",
"0f3685b65b3689bdd68f90998ecf6445df20f325b27b79f529278aa98bc6cc86",
"wss://nostr.mom",
"root"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
]
],
"content": "Protocols != Businesses\n\nA business that has lots of demand can buy its way out by raising money and directing lots of resources towards solving the problem. It also has the benefit of typically controlling all the infrastructure, so is able to replace the entire underlying stack.\n\nA protocol cannot do that, it's dependent on volunteers, grants or companies that, often against their commercial interest, keep improving it in a mostly backwards compatible way. The amount of resource that can be mobilized is smaller and the upgrade process harder (a whole ecosystem has to move).\n\nThe most likely outcome imo is that companies will build very sophisticated scaling technology, that will likely not be open source so they can have a moat, and then dominate the end user market. Us nerds can still use the core protocol, but might not even be able to communicate with the majority of users.\n\nE-mail is a cautionary tale, try hosting your own and still reaching gmail users reliably. Or try getting ICS files for flight bookings, airlines just set the google calendar metadata since ~everyone uses GMail+GCal. It's a bit different since the centralizing force for e-mail was spam and not scaling, but I think it's a close enough analogy.\n\nOr look at the web stack, it historically evolved to become such a bloated monstrosity (because the inventors designed a document standard and we shoehorned it into becoming an application framework) that these days only companies with millions to burn can keep up with maintaining browser engines (and Google pretty much defines the direction of travel because Chrome is number one).\n\nSo when I worry about scalability it is out of a deep care for decentralization and not seeing all that energy invested go to waste by ultimately ending up in the same place we started at. If we don't consider decentralized scaling from the beginning, the non-ideological VCs pouring money in once it gets traction certainly won't.",
"sig": "66f82bdc2728e2b06b819789dc5851346118f80038148814f17596decfbef8136eb8525b1f7ae7b1400b133e682e7eeb7b0117cf7621cdbfac931e4647ff2545"
}