misskey be like:
*adds feature that doesn't federate*
*adds feature that doesn't federate*
*adds feature that doesn't federate*
*adds feature that doesn't fed-
@julia @natty out of curiosity, how do stuff like firefish/iceshrimp and sharkey compare to that? do they implement those? do they implement them federated? im trying to decide what to run for own instance πŸ‘€
@hazel @julia firefish had some plans to make some of those federate, but development fizzled out

iceshrimp removed some broken parts and generally tries to catch up the tech debt first

catodon removed almost everything that doesn't federate

sharkey is the closest to vanilla misskey in that way
@natty @julia as someone way to deep into fedi software; which one would you recommend for: β€œthings just work and i can talk to my friends instances but i also get cat ears”
@hazel @julia probably (unfortunately) sharkey

iceshrimp is great but the dev is rewriting from scratch
@hazel @julia the issue with sharkey is that it moves fast and relies on upstream misskey, so it suffers from similar issues as misskey
@natty @julia what would those issues be? also what about like akkoma?
@hazel @julia Well, getting used to the feature creep of Misskey

Akkoma is well-established, but has its own jank

All the choices are valid, it's just about considering what kind of jank is acceptable. Whether the JavaScript-heavy frontend and terrible user API or a more lightweight but clunky experience

Akkoma has the advantage of a fully-working Mastodon-compatible API, IceShrimp has an "ok" compatibility layer for it, and the rest is spotty
@natty @hazel @julia Akkoma's Mastodon API really isn't that great actually

When I moved to Akkoma I expected to just use Megalodon like before but then ended up contributing like ~2.5k lines of code to get it to work properly
@natty @hazel @julia and it's not even possible to log into Mozilla's Android client without modifying the code a little bit
@natty @julia hehe yeah ive seen that its C# (?) now