Earlier quoted context omitted.
Your mistake is thinking that the relevant centralization is in the client-server architecture. The real reason that people have centralized social is because it's hard to let people authenticate and find their friends across domains. And even further, there are no good tools comparable to Facebook when it comes to subscriptions, notifications, updates, realtime collaboration, and all those other multi-user things th…
The discussion point of the article is how we can build such technologies for the kinds of things you just listed as needing a centralized domain. You claimed that they were describing your platform. But in the 'macro' sense, your platform is nothing like that -- it's a different flavour of Web app server, and fits in with the existing paradigm. Yes it may be part of a decentralised system (the Web), but any large We…
Really? It seems that many of the actual quotes from the Fathers of the Internet in the article apply to existing web client-server architecture:
“We hoped everyone would be making their own web sites—turns out people are afraid to.” - Tim Berners-Lee
“People have their friends on Facebook and some photos on Flickr and their colleagues on LinkedIn. All they want to do is share the photos with the colleagues and the friends—and they can’t. Which is really stupid. You either have to tell Flickr about your Facebook friends, or move your photos to Facebook and LinkedIn separately, or build and run a third application to build a bridge between the two.” - Tim Berners-Lee
(by the way, we address this explicitly in our platform)
"Don’t discount Wordpress, it has been embraced by large numbers of people, perhaps the new web should have a decentralized Wordpress type of service." - Brewster Kahle
That doesn't sound like a necessarily serverless architecture to me.