13
Curious. Why did someone think it necessary to do sharkey and iceshrimp. What is wrong with Misskey? (feddit.online)
submitted 1 year ago* (last edited 1 year ago) by to c/fediverse@piefed.social
3 comments fedilink hide all child comments
 

I'm curious about people's thoughts around Misskey and its forked projects.

  1. Why is Misskey so popular in Asia, but not used much in the west? Why do you think the preferences are so different between the regions?
  2. What is wrong with Misskey that some people are willing to invest their time and money on separate forks (IceShrimp, Sharkey). What's the difference between the forks and the originals?
  3. Does anyone have experience running any of these? Do they have any downsides like, for example, a database that grows unreasonably fast or that requires too many resources?
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 year ago* (last edited 1 year ago) (1 child)

I don't know about Misskey and haven't the opportunity to test it.

I looked for a french speaking instance that doesn't use mastodon because i disliked mastodon's UI. That french speaking instance was using Firefish.

Then Firefish development stopped and the instance moved to iceshrimp. And then, they started rewritting it into #C because it is the dev main language. (Iceshrimp.net)

If i'm not wrong, as one of its dev know jlai.lu that run lemmy, they will add support of Lemmy and PieFed (because i share lot information about PieFed on jlai.lu and its matrix room)

It is for you @AntoineD@kwak.cab :)

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 3 points 1 year ago* (last edited 1 year ago)

    @Snoopy

    Hello @Jerry.

    Misskey is a Japanese software, whose lead developer does not speak English and does not make an effort to do so, even with translation tools.

    It is therefore very complicated to contribute to the software if one does not speak Japanese.

    At the time of Misskey 12, a soft fork was created, named Calckey, which added functionalities not present in Misskey, such as:

    • API Mastodon
    • Edit post
    • Improved UI/UX (especially on mobile)
    • Improved notifications
    • Fediverse account migration
    • Improved instance security
    • Improved accessibility
    • Recommended Instances timeline
    • OCR image captioning
    • New and improved Groups
    • Better intro tutorial and many more user and admin settings.

    With the update to Misskey 13, which brought significant changes, Calckey became a hard fork and eventually rebranded as Firefish. Various reasons led to the creation of the IceShrimp fork (focusing on bug fixes and performance optimization), while Firefish wanted to continue innovating but ultimately faded away.

    Following this, two new projects emerged:

    Sharkey, a soft fork of Misskey that reimplements the functionalities of Calckey into the updated Misskey (it's the equivalent of Mastodon + Glitch-Social).

    IceShrimp.net, a from-scratch rewrite of IceShrimp in C#, which, once completed, will allow the migration of instances from IceShrimp.js. It will no longer be a fork of Misskey, with the goal of having software that is much easier to maintain, with cleaner and more optimized code, and to implement maximum compatibility with the major platforms of the fediverse.

  • permalink
  • fedilink
  • source
  • parent