I personally find the development to be more "sensible". firefish bungled up their flagship with a (imo) failed transition to scylladb and hasn't been doing much of importance since then (they changed the boost icon to a rocket though!)

compared to that, iceshrimp rewrote their mastodon api compatibility layer to the point where it may be the most compliant one among misskey forks, uncovered several perf bottlenecks (one really big one related to word mutes since fedia migrated over), fixed the http signature security vuln ahead of firefish (and provided the patch to them, which they didn't put in a stable release for something like two days even after merging)

quite a lot of firefish instances seem to be migrating over to sharkey for similar performance and stability reasons, but if you like the firefish UI/UX compared to the "classic" misskey one (or want a smoother migration path from firefish that doesn't involve a major version bump) then iceshrimp is the one to check out imo

[–] nix@merv.news 3 points 9 months ago* (last edited 9 months ago) (1 children)

Ah, thanks for the writeup. Definitely sounds like the better option.

Them not having a flagship instance or a website that lists iceshrimp instances makes it difficult to try though.

[–] ShittyKopper@lemmy.blahaj.zone 4 points 9 months ago

https://fedidb.org/software/iceshrimp is a thing, and there are several general purpose instances such as fedia.social and iceshrimp.social (which isn't anything official despite the name)

not having an (open) flagship is, to the best of my knowledge, an intentional choice as moderating it would take time away from development