Firefish (@firefish)
info.firefish.dev
**Announcement: Firefish will enter maintenance mode** For those who have been supporting Firefish and me, I can’t thank you enough. But today, I have to make an announcement of my very difficult decision: As of today’s release, Firefish will enter maintenance mode and reach end-of-support at the end of the year. The main reasons for this are as follows. In February, Kainoa suddenly transferred the ownership of Firefish to me. This transition came without prior notice, which took me aback. I still wish Kainoa had consulted with me in advance. At that time, some people were already saying that “Firefish is coming back”, making it challenging to address the situation. Also, since there were several hundred active Firefish servers at that point, I could not suddenly discontinue the project, so I took over the project unwillingly. Over the past seven months, I have been maintaining Firefish alone. All other former maintainers have left, leaving me solely responsible for managing issues, reviewing merge requests, testing, and releasing new versions. This situation has had a significant impact on my personal life. Frankly speaking, there are numerous bugs and questionable logic in the current Firefish codebase. While I attempted to fix them, balancing this work with my personal life made it clear that it would take ages, and I’ve started thinking that I can’t manage this project in the long run. Additionally, vulnerabilities have been reported approximately once a month. Addressing vulnerabilities, communicating privately with reporters, and testing fixes have proven overwhelming and unsustainable. Moreover, a certain percentage of users have made insulting comments, which have severely affected my mental well-being and made me fearful of opening social media apps. I will do my best to refund the donations made to Firefish via OpenCollective, but that’s not guaranteed. `firefish.dev` and `info.firefish.dev` will remain operational until the end of February 2025, after which they will return a 410 Gone status. Server admins may downgrade Firefish to version `20240206`/`1.0.5-rc` and migrate to another *key variant, or may fork Firefish to maintain. Downgrade instructions: https://firefish.dev/firefish/firefish/-/blob/downgrade/docs/downgrade.md Thanks, naskya

Announcement: Firefish will enter maintenance mode

For those who have been supporting Firefish and me, I can’t thank you enough. But today, I have to make an announcement of my very difficult decision: As of today’s release, Firefish will enter maintenance mode and reach end-of-support at the end of the year. The main reasons for this are as follows.

In February, Kainoa suddenly transferred the ownership of Firefish to me. This transition came without prior notice, which took me aback. I still wish Kainoa had consulted with me in advance. At that time, some people were already saying that “Firefish is coming back”, making it challenging to address the situation. Also, since there were several hundred active Firefish servers at that point, I could not suddenly discontinue the project, so I took over the project unwillingly.

Over the past seven months, I have been maintaining Firefish alone. All other former maintainers have left, leaving me solely responsible for managing issues, reviewing merge requests, testing, and releasing new versions. This situation has had a significant impact on my personal life.

Frankly speaking, there are numerous bugs and questionable logic in the current Firefish codebase. While I attempted to fix them, balancing this work with my personal life made it clear that it would take ages, and I’ve started thinking that I can’t manage this project in the long run. Additionally, vulnerabilities have been reported approximately once a month. Addressing vulnerabilities, communicating privately with reporters, and testing fixes have proven overwhelming and unsustainable. Moreover, a certain percentage of users have made insulting comments, which have severely affected my mental well-being and made me fearful of opening social media apps.

I will do my best to refund the donations made to Firefish via OpenCollective, but that’s not guaranteed.

firefish.dev and info.firefish.dev will remain operational until the end of February 2025, after which they will return a 410 Gone status.

Server admins may downgrade Firefish to version 20240206/1.0.5-rc and migrate to another *key variant, or may fork Firefish to maintain.

Downgrade instructions: https://firefish.dev/firefish/firefish/-/blob/downgrade/docs/downgrade.md

Thanks,
naskya

  • Blaze@feddit.orgEnglish
    55·
    14 days ago

    I thought it was gone last February as mentioned in the post.

    Again, sad to see, but good luck to IceShrimp, Sharkey and all the others!

    • Coelacanth@feddit.nuEnglish
      32·
      14 days ago

      Iceshrimp is also in a weird place right now, as it’s currently also in maintenance mode while the ongoing iceshrimp.NET full rewrite is happening. Seeing the OP’s comments about the Firefish codebase, that rewrite might be just what’s needed - provided it’s actually completed.

  • MoogleMaestro@lemmy.zipEnglish
    23·
    14 days ago

    I was on firefish’s previous instance, known as calckey, before I migrated back to Mastodon.

    There were definitely warning signs that the project was facing maintenance issues in those days as well, and it felt that the Firefish rebrand was an attempt to “start a new”.

    But just like my post on KBin’s demise, it should be a warning to those who want to make the software and host a “big” instance: Don’t do it. I think it’s smart to host your own mini instance for testing, but you should probably solely focus on the code development side of things to make sure that you aren’t over burdening yourself with managerial tasks. If your software is good, people will make spins inevitably. If people use it, then you will probably have enough people contributing that you can scale up your mini-instance if needed. But don’t jump in without the finances in place, because you’re essentially taking on two jobs.

    • db0@lemmy.dbzer0.comEnglish
      3·
      12 days ago

      counterpoint: If developers aren’t forced to “eat their own dogfood” it becomes difficult to see some issues and know what to prioritize.

      • MoogleMaestro@lemmy.zipEnglish
        1·
        11 days ago

        I do agree that developers should use their own software, but doing so on a smaller instance with strict active user limits is probably the right call – at least until you are certain the software has a “stable” version, but even then you probably will want to run a master branch instance that is much less stable and prone to errors. Until you can afford it, it’s probably not a good idea for developers to be spending a huge amount of time debugging in-progress features (which IIRC, firefish had a lot of those.)

  • sabreW4K3@lazysoci.alEnglish
    22·
    14 days ago

    Loved the branding and was so hopeful, but like everyone else, I long thought the project was dead.

  • aasatru@kbin.earth
    20·
    14 days ago

    Sad, but mostly awful that the project has gone down in such a messy way. That sounds like a tremendous personal load that was completely uncalled for.

  • schizo@forum.uncomfortable.businessEnglish
    11·
    14 days ago

    As with all things in life, as soon as I touch it, it explodes, lmao.

    I think this means I’m done with trying to host fedi-Twitter. Discoverability on a small instance sucks, maintenance on a small instance sucks, and the software available designed to do a reasonable small instance doesn’t exist.

    That, and since relays are almost entirely required if you expect ANY useful content discoverability, you’re just wasting a huge amount of resources on crap you don’t want, don’t care about, and can’t really delete because all of these pieces of software expect you to keep everything from everywhere forever.

    Think I’ll just do a rm -rf and get that ~25gb of disk space back and stick with Lemmy (which is my preferred interaction format anyways).

    • aasatru@kbin.earth
      11·
      14 days ago

      Sounds like… uncomfortable business? :)

      More seriously though, couldn’t a.gup.pe help with discoverability? Tag a larger group, and the post is automatically forwarded to a lot of servers and shown to a fair share of users.

      But yeah, bring on a smaller fedi server for microblogging has obvious drawbacks that people tend to brush over. It does require more effort to become discovered.

      • schizo@forum.uncomfortable.businessEnglish
        15·
        14 days ago

        I’m going to get shit on, but outside of Lemmy, there are just… no active groups on the various fediverse group site aggregators that I’m remotely interested in.

        It’s all news, politics, political news, and political peacocking. Which fine, if that’s what you’re after, but I’m here for nerd shit, and Lemmy is utterly completely awash in nerd shit.

        The other problem is an ActivitPub problem. Even if you follow someone, if you’re not following every single human on fucking earth, you’re not going to see all the replies to their posts on your server. So your clever post was already made 8 hours ago, and unless you click on another link that takes you to their instance you can’t actually browse what replies actually exist before posting.

        Which is just stupid: if I have to visit someone else’s shit in order to see if I should reply, I might as well just you know, use that server and save myself the trouble.

        IDK, I liked the UX and it was interesting while it lasted, but it was really just a massive resource drain and had far less interesting nuggets than other options did.

        • aasatru@kbin.earth
          41·
          14 days ago

          Yeah, very fair. I’m lucky enough that the things I use Mastodon for has more or less established communities there.

          The federation of comments is a huge headache. Intuitively it makes no sense the way it’s solved - if I go to the comment section, I don’t want a bunch of it to be randomly hidden from me. It’s something that just needs to be solved better, even though we’ll always see slightly different things as not all content is equally welcome everywhere.

          I’m happy Lemmy works better for you though! I think it might just be a better format for nerd stuff. I like Mastodon for many things, but this is where I go to embrace nerd stuff. Politics here are more insufferable than at the Mastodon instance I’m on though. ;)

          • schizo@forum.uncomfortable.businessEnglish
            51·
            14 days ago

            I’m not one to tell developers what to do, but from a user perspective, comments (which is like, most of the damn point, no?) are effectively broken and that makes the whole platform kinda… defective.

            I’ve discovered I follow topics but very very rarely care about who is posting/commenting, which makes microblog feeds doubly not my thing. Forums and Lemmy match far more what I’m after than Twitter-style feeds ever will, because the amount of curation to find a single interesting person (who then doesn’t turn out to be an utter monster) is just… too much involvement for some idle time-wasting.

            Also I don’t know what you mean about the politics being insufferable on Lemmy, comrade. Perhaps you need to take a nice long vacation to the People’s Re-education Retreat and hot spring?

  • themadcodger@kbin.earth
    10·
    14 days ago

    Popular take, but I also thought it was dead. I was on Firefish and noticed it was seriously degraded in day to day use. I started with Mastodon, but the *isskey platforms just have a better ux/ui (IMO) and I really didn’t want to go back to Mastodon. So now I’m on Sharkey, and hoping this one sticks around!