We partly moved to ice shrimp, but it was quite divergent from Hajkey, and after being burnt by our Calckey experience, we lost a lot of momentum and energy, so it’s sort of sat there in a mostly working state, not ice shrimp and not Hajkey for a while now.
Once we’re both back from South America though, we’ll do a migration to Sharkey (a direct soft fork of Misskey). After that, Kaity will look at gradually adding our Hajkey specific features directly in to Sharkey where possibly.
Was on it for a few months but jumped ship after bugs went unfixed. Can’t fault the owner personally. It’s a stressful, thankless job. Hope he finds happiness in 2024
I’d rather go back to the 90s! The good old times, when devs can lose all that commercial software source code they are developing when the hard drive crashes! And there were no backups! Sorry people who bought licenses! 😂
Not to downplay all the blood, sweat, and tears that have been shed while making the fediverse work, but if I may offer some unsolicited advice to the author of the linked post: Publicly airing out a team’s dirty laundry tends to be… counter-productive. Usually it’s best to “keep it in the family.”
In this case, we don’t know what’s going on in the original project owner’s life right now. The author of this post could have just said “hey all, we apologize for the inconvenience, but the original project appears to be abandoned, so we’ve forked the project with the intention of patching some of the known issues and adding some new features.” (insert GH link here)
Although the original project dies, this new project is born, and who knows—the original project’s owner might even show up again someday and start making meaningful contributions to the new project (or not).
I say all this without knowing the full history of this project, and I don’t mean to downplay the author’s frustration, just my two cents.
All of that said, in my mind this situation makes for an interesting case study on the pros and cons of different ownership structures for public/open projects.
Damn, that repository and its forks really know how to crash and burn. I’m glad to see it’s being given more life with another fork. That said, with a name like Catodon, I can pretty much guarantee it won’t be a resounding success 🥺
i hope instances can come up with a more standardized methods of control that dont leave all the keys in a single humans hands. we know how unstable humans are.
i hope instances can come up with a more standardized methods of control that dont leave all the keys in a single humans hands
Yeah like we could have a shared legal entity, say a corporation, controlling the servers 🤔 And they could instead of a single decisionmaker have a board. 🤔
Jokes aside, wouldn’t this go against the federated idea? anyone can go and roll their own instance. Or take it down. Control is in the user’s (of the software, that is, the instance owners) hands!
Another example of this is what happened with KeePass, then KeePassX, which gave us KeePassXC. Went from single Dev to single Dev to group of devs that were serious about the ecosystem.
Even at its smallest form, a federated instance hosting a community likely needs more than one person acting as admin and mod. It may not be a for profit corporation, but there needs to be some kind of collective organization.
catodon.social
Newest