@fla Hi Fla, C4 is the Collective Code Construction Contract. It IS a bit radical but the idea is to prioritize the people and community who are developing a project by making it much easier to get contributions merged and therefore make more constant and satisfying progress. This fork is experimental but my hope is that it demonstrates a viable path forward for really any project.

C4 came out of the work of Pieter Hintjens and the 0MQ project. Links to follow...

@fla

Here are a few links to learn more.

* https://zguide.zeromq.org/docs/chapter6/

* The contract itself: https://rfc.zeromq.org/spec/42/

* https://peertube.co.uk/videos/watch/09b4e6f7-699a-45a7-83f4-16a63f71d57c

@weex so what are you doing right now regarding diaspora?

@fla I've created a fork that will be maintained by the process spelled out in the protocol.

@weex I need to read more to understand how that C4 thing is working, but merging stuff without human review seems a bit dangerous to me.

@fla I agree it's a bit counterintuitive / counterculture even for software and it could be a bit bumpy at the start but I'm hopeful for its evolutionary approach.

@weex diaspora* maintainers always have been very conservative with code merging. But maybe that experiment can change their mind. Just, please, be very explicit on your pod about the fact that you are not running the vanilla diaspora* code, but some untested one.

@fla Understand completely. Created this and will probably update the readme https://github.com/weex/diaspora/issues/20 but will also create one saying the same about the UI.

@fla FYI, I figured it's best to make a post explaining the effort so here's that: https://discourse.diasporafoundation.org/t/experimental-fork-based-on-c4/4095

@lightone Yes, I can confirm that I've created a fork and for the reasoning, I posted this today: https://discourse.diasporafoundation.org/t/experimental-fork-based-on-c4/4095 and a few days ago in the tooling https://github.com/weex/c4-tools/blob/main/README.md

Happy to answer any questions and plus I definitely need help if anyone's out there and wants to work on the process together.

@weex I don't think diaspora has had any long-living forks, or any forks, come to think of it. Will your pod(s) have some indication in their NodeInfo that it's not vanilla *d? Maybe like Glitch-soc Mastodon fork does (if you look at https://the-federation.info/mastodon, you'll find Glitch servers via specific version indicator). I don't know if diaspora can attract new influxes of users, now that ActivityPub is trending, but I still love diaspora interface and will follow any of its forks with interest! 👍

@lightone Yes, will definitely change the Nodeinfo and open to suggestions there about what should be unique. One thing about C4 is releases aren't really necessary so version numbers might turn into a serial number plus hash. Not sure if any trackers might care about that.