@vintprox@reiver@weex Regarding migration steps, we will see. It's just based on kbin, so migration would a very easy switch, with the same requirements.
Yeah, all that sounds sweet and tidy at the first glance. Upon another glance, there are missing URLs and files. Hope the switch won't cause any such hiccups. 🙌
@melroy It's a hypothetical scenario in which you replace Kbin with C4, but previously working links are no more (404 Not Found). It damages SEO and UX for external guests.
But I suppose you're planning to open a completely separate instance and still maintain kbin.melroy.org?
@vintprox c4 is not the name of the project. C4 is a wow. Anyhow, the fork will be backwards compatible. We shouldn't break links or activitypub in any way.
@vintprox kbin.melroy.org will be running this version of the fork eventually. But you won't even notice it, unless we have more features than the slow development of kbin.
@weex@laravista Ps. I will also upgrade to Ecko on my mastodon.melroy.org instance! I'm sick of Mastodon not supporting markdown and longer posts, let's go Ecko! It will have no down-sides for the users, we just have more features.
@reiver@weex follow up. The fork is in place and it's seem like a success already. This model based on trust is basically an experiment, let's see how it evolves. See: https://github.com/MbinOrg/mbin
@melroy@reiver@weex Is it compatible with any mobile clients? On iOS I haven't been able to find a single one that works with fedia.io (kbin). Will happily switch server if that now works :(
Add comment