Ambitious Misskey fork that rebranded from Calckey, added many features, then collapsed when the solo maintainer burned out — a cautionary tale of fediverse forks.
Firefish was a fediverse server implementing the ActivityPub protocol, written in TypeScript with a Vue.js frontend and PostgreSQL backend. It supported emoji reactions, quote posts, rich media embeds, antennas (saved searches), and Mastodon API compatibility.
Misskey is a Japanese-origin fediverse server known for its rich feature set: emoji reactions, drive-based file management, antennas, and a distinctive UI. A Misskey contributor decided to fork the project in 2022 under the name Calckey, adding features the community had requested but Misskey's developer hadn't prioritized — better quote posts, improved accessibility, and a more polished onboarding experience.
What started as a side project grew rapidly. Calckey attracted users who wanted Misskey's features without the rough edges, and the project garnered significant attention in the English-speaking fediverse. In July 2023, the project rebranded to Firefish with its 1.0 release. The new name was controversial — some found it generic and too similar to Firefox — but the project pushed forward.
The problems were structural. Firefish was essentially a one-person project with enormous scope. The lone maintainer had to track Misskey's rapid upstream development, maintain their own feature additions, handle community management, and deal with the inevitable bugs of a complex web application. The burnout was predictable.
By early 2024, development slowed dramatically. The main project website went offline. Only security fixes were being released. By mid-2024, Firefish was officially discontinued. Instance administrators scrambled to migrate to alternatives — primarily Sharkey (another Misskey fork) or back to Misskey itself.
Firefish's rise and fall happened in barely two years and became a cautionary tale in the fediverse community about the sustainability of forks maintained by single developers. The project's features and ideas didn't die entirely — Sharkey and other Misskey forks incorporated many of them — but the project itself couldn't sustain itself.
Calckey created as a Misskey fork with community-requested features
Calckey rebrands to Firefish with 1.0 release
Main website domains go offline; only security fixes being released
Firefish officially discontinued; users migrate to Sharkey or Misskey
Firefish demonstrated both the potential and the fragility of fediverse forks. It showed there was strong demand for a more polished Misskey experience, but also that a single maintainer cannot sustain a complex social media server. Its features and ideas influenced Sharkey and other Misskey derivatives that continue today.