Sync'd up another project. This time: *

Took a couple hours merging 11 of 26 open PRs on upstream.

Code: github.com/weex/diaspora

Next step is to deploy this to a production pod.

@weex Just curious. Are you forking diaspora? 😲 For further independent development? Or do you just want to install the version with those PRs present?

Follow

@lightone Yes, I can confirm that I've created a fork and for the reasoning, I posted this today: discourse.diasporafoundation.o and a few days ago in the tooling github.com/weex/c4-tools/blob/

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

· · Web · 1 · 0 · 2

@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 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.

Sign in to participate in the conversation
Ecko / c4.social

Creating magic through evolution of the Fediverse. Running Ecko, a community-driven fork of Mastodon managed using the Collective Code Construction Contract (C4) by the Magic Stone Community. C4 is a protocol for asynchronous, non-blocking, distributed, problem-focused software development.