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

Edit: Removed the photos due to lemmy crawler displaying the toot.

  • edric@lemm.eeEnglish
    0·
    2 months ago

    Glad I held back from suggesting Firefish for my wife. I’ve been slowly trying to convince her to jump to the fediverse for microblogging and figured to have her try Firefish simply because it’s prettier than Mastodon. Guess it’s back to ol’ Mastodon.

    • 101@reddthat.comOPEnglish
      0·
      2 months ago

      You can suggest Akkoma to her if you want a Mastodon alternative.

      • noodlejetski@lemm.eeEnglish
        0·
        2 months ago

        there’s Phanpy, Ełk, Tangerine, Pinafore, and Mangan when it comes to web apps. and apart from that there’s a huge offering of mobile and desktop clients.

      • schizo@forum.uncomfortable.businessEnglish
        0·
        2 months ago

        There are some. Mastodon has a lot of garbagey nonsense, but they do at least have a proper API which will let you make a non-shit front end if you wanted.

          • schizo@forum.uncomfortable.businessEnglish
            0·
            2 months ago

            Well, Lemmy’s front end talks to it’s back end via an API, which is pretty much how every web app of any scale works these days.

            There’s really not any particular difference between a monolithic app vs a seperate front end in terms of “all those API calls” since everything is basically calling APIs at this point, if they’re not made by complete incompetents. (In the case of Mastodon, though, I suppose complete incompetent is possible.)

          • Xylight@lemdro.idEnglish
            0·
            2 months ago

            photon doesn’t directly communicate with the backend, it’s not intended for that. but even then, lemmy-ui is almost entirely client side (for some reason) and it makes its calls to the API