Right now the fediverse is nipping at the heels of the silos.
They know we are here, and they perceive us as a threat. We know this from leaked emails from facebook.
That said, they could attack us in an oblique manner with any number of poisoned waterhole attacks.
Earlier today someone predicted one or more of those platforms just integrate activitypub and crush us by incorporating us.
Another pointed at the potential for procedurally generated instances that just harvest data, or overwhelm our ability to suspend all of the instances they throw up.
When these attacks are adapted to... they'll get concerned, and will try to frame us as part of "the dark web(tm)"...
That's how we'll know we're winning.
For corporate applications (which, arguably, most projects on Github are), its interaction model is nearly ideal. It mimics closely enough the centralized VCS organization that it's easy for companies to adopt, but has just enough DVCS features that enables collaboration. I suspect that is why it took off so well.
text too long-mandatory cw Show more
This is how Linux is developed, although though use a mailing list. Git over Email is effective because it is decentralized and does not require developers to create accounts or accept other system's policies to submit patches and bug reports.
Another, extremely simple model of using email for git is creating your own public repo at say, git.example.com/somerepo and sending an email to the maintainer of some software, "Hey, can you please merge my branch 'master-somenewfeature' located at https://git.example.com/somerepo ?"
There is a reason there's an email field to setup when running git config.