I have no idea what to call the Eepy.moe Misskey fork, but I’m really frustrated that I’m in a position of having to make it in the first place.

@julia new misskey fork incoming

@julia please stop forking this shit codebase

@itzzen I literally have no fucking choice, all the other forks implode on themselves, I need something that’ll just fucking hold out till I’m done with Aurora.

@julia fork9

@julia SpiteKey

I'm dead serious, call it that.

@SymTrkl Bet.

@julia eepkey

@julia I'm a millennial, is "bet" the one that means yes, or no? /hj

@SymTrkl kinda? it’s like “just you watch, I’ll make it happen” or something.

@SymTrkl @julia It means yes!
Source: Zillennial who was raised speaking AAVE

@julia firefish is still maintained it seems, or iceshrimp

@itzzen its not that simple, making and maintaining my own fork is an informed and pained decision.

@julia cutekey

@julia why fork?

@itzzen I don’t have the mental capacity to write down all the reasons that lead me to this decision at the current moment.

@julia but serious answer, misskey is originally a Japanese project right, since you're an English speaker maybe go the other way. so eepy dot moe, maybe "nemui"? (眠い meaning sleepy)

@julia also because, tbh, naming yet another misskey fork "XXXkey" is more than a little tired

@julia I feel that if you are wanting to use something as a temporary thing before you work aurora to stable, I don't see how using something like iceshrimp or whatever for the meantime would be bad

@itzzen I disagree with the direction iceshrimp is going.

@julia then firefish? that's still maintained

@itzzen not really.

@julia I mean, you want something for until aurora, not a permanent thing?

@itzzen I’m already on sharkey and disagree with a lot of design decisions, so I want control over the code I’m deploying. Furthermore, I don’t want to be in a situation like firefish again while I’m trying to work on aurora.

@julia fair, ig