Sync'd up another #C4 project. This time: #Diaspora*
Took a couple hours merging 11 of 26 open PRs on upstream.
Code: https://github.com/weex/diaspora
Next step is to deploy this to a production pod.
@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.
@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.
@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! 👍