Can Big Social just swoop in and take over the Fediverse on a whim?
Realistically, that can't happen.
1. Pivoting a big business is like captaining an aircraft carrier: it is slow and takes deliberation
2. Most businesses don't like to kill their cash cow, and the network effect that they own is their cash cow
3. Big Social itself is in disarray and doesn't have the wherewithal to make good strategic decisions
And there's other reasons too! 🧵
Big Social are no longer the innovators they were.
In actuality, for the past 10 years, most innovations in social media have been created by small, nimble players—which Big Social then attempts to either acquire or copy.
In essence, they've replaced R&D with M&A.
Thus, they probably have nothing new to add to the Fediverse.
Big Social is obsessed with metrics, and proving value through metrics.
What metrics prove the Fediverse's value?
No one knows. Every metric regarding the Fediverse is at best conjecture. Nobody even knows its true size.
Hard to convince a CEO to buy into an idea when nothing is probable through metrics.
Nobody has validated the Fediverse as a place to make money.
Sure, tiny web-hosts might charge for services, but the average Big Social executive isn't looking to make tiny increases in a new venture. They want to 100x or 1,000 their ROI.
Somebody might eventually try this, but Big Social isn't going to be first.
Believe it or not, most people who work at Big Social are *not* social media nerds, and have zero interest in how the technology works.
When they look at Mastodon, their response is pretty much the same as everyone else's: they throw up their hands and say, "This is too complicated!"
And then they close their browser tab.
The only way Big Social challenges the Fediverse is through small competing skunkworks projects.
Which has actually happened with Jack Dorsey's Blue Sky project.
And to be honest, I'm skeptical about Blue Sky for many reasons—which I may talk about in a separate thread.
But more to the point, Blue Sky has been around for 4 years—and why aren't we using Blue Sky?
@atomicpoet They do not know how to extract money if they Federate too. That is what is holding up the Blue Sky development in my honest opinion.
@darnell @atomicpoet
They were stalled arguing about blockchain for almost all that time.
Dorsey took over, and they have since basically all but abandoned any blockchaininess, released a couple of papers, and got some test code running.
Their plans are ambitions and unproven, and seem to amount to still having algorithms written by advertisers deciding what you see. Just you get to pay to pick which advertisers wrote the algorithm.
I think they wasted 3 years and are now doing work but I don't think their incentives and aims are for the communal good.
@darnell @atomicpoet @pre I'm just disappointed that BlueSky decided to make their own protocol instead of just using a pre-existing protocol *cough*ActivityPub*cough*
@strypey @JoshuaACasey @darnell @pre Have you looked into the nomad protocol? It aims to combine Zot6 with ActivityPub.
@atomicpoet @strypey @JoshuaACasey @pre That sounds very interesting! I think what would be cool if the protocols could be merged (yes, even relevant remnants of Blue Sky) into one super protocol.
It would be easier if they were written on top of ActivityPub though since the latter is much larger than the others.
@darnell
AP is just a name. It doesn't really matter what the unifying protocol is called, as long as it takes the best from all the existing protocols, and overcomes the limitations in each of them.
@atomicpoet
> Have you looked into the nomad protocol
Not in any detail. But the author's refusal to work with anyone else (because we're all so "toxic") makes me sceptical that it will get any more attention or addition than any previous Zot-based experiments. Which is frustrating, because it's probably just as technically brilliant as they were.
@JoshuaACasey
TBF they have some legitimate criticisms of the limitations of AP. Eg full account and data portability is hard to do in the 'verse because AP ties both to the domain name of the hosting instance. What I'm hoping it's that that they can work constructively with AP implementers - in a way the Zot folks couldn't - to come up with a successor protocol (or a new version of AP) that can overcome these limitations.
@darnell @atomicpoet @pre