@eloquence@protean@JosephAndriano@evan I think it'd be a sweet idea to explicitly partner with #CoSocialCA sooner rather than later. There may be insights we can share with them, & they'll probably eclipse us in size-complexity real fast once they get launched and learn a TON. I doubt their membership will be as explicitly coop-minded, so we could sort of become the mastodon instance focused on cooperative interests, while many general-purpose cooperatively owned instances like them emerge.
@protean@JosephAndriano I don’t know if splitting up is the way to think of it, how about “budding”. What if we set a cap on our size capacity, both in terms of technical limit & the limit for effective cooperation, & then helped another smaller coop grow out of us, that we maintained close relationships with. Because a 20,000 person coop isn’t really much of a coop. You really see this with the Twin Cities (MN) grocery coops around me as they’ve grown & adopted corporate governance models.
@protean Interesting read. What troubles me about this is that it seems like it’s not something that can be controlled for and needs to be addressed in the codebase. Getting engagement shouldn’t kill your instance. As for social.coop, I don’t like the idea of us splitting up. I do wonder about us scaling up though, and what the costs of that would be.
Lots of smart people saying the same thing - there are dangers ahead for the fediverse that aren't really being addressed right now. What happens when the inevitable consolidation comes knocking?
#SocialCoop has a model that is one way (maybe) out of that trap. But I think we need to seriously consider an upper limit on size, and splitting into multiple coops.