Edit 1: After I made this post I looked for the app everywhere, turns out the developer removed it from Fdroid and Google Play Store and even deleted the community.

I guess the client is done.

  • Dessalines@lemmy.ml
    link
    fedilink
    arrow-up
    30
    ·
    6 months ago

    That’s very unfortunate. Open source development can seem like a thankless job sometimes… you start out building something because it’s fun, or you want to challenge yourself, or learn something new… and then other ppl start making demands, those start to pile on, and it quickly becomes a stressful job.

    Sorry to see that app go, it had a lot of potential.

    • Einar@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      6 months ago

      It definitely had potential. Was my main driver for Lemmy. It had the best layout of posts, modern and sleek handling, etc. Markdown worked just fine for me. The minor bugs I noticed didn’t bother me much. Am sad to see it implode like this… hope the dev will change his mind or someone will pick up the pieces.

  • Einar@lemm.ee
    link
    fedilink
    arrow-up
    12
    ·
    edit-2
    6 months ago

    That’s concerning. I’m typing this through Raccoon right now. Awesome client.

    • ModerateImprovement@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      10
      arrow-down
      2
      ·
      6 months ago

      After I made this post I looked for the app everywhere, turns out the developer removed it from Fdroid and Google Play Store and even deleted the community.

      I guess the client is done.

      • kinkles@sh.itjust.works
        link
        fedilink
        arrow-up
        15
        ·
        edit-2
        6 months ago

        Someone on Lemmy did a markdown test of all existing Lemmy apps and posted the results. Raccoon was one of the worst performers, and after seeing the results the dev went nuclear.

        Here’s a comment on the original post talking about it. I think the thread’s OP ended up removing Raccoon from their results but the damage was already done.

        • Spunky Monkey@lemm.ee
          link
          fedilink
          arrow-up
          10
          ·
          6 months ago

          Just to add that it was the worst performer because the tester made some mistake when doing said markdown test. When he corrected the test it was nowhere near the worst, but it was already to late.

          Some people (tester included) tried to reason with the dev, but to no avail. I think he was scared because he was using his real name in github, and didn’t want to have bad code in his résumé or something like that.

          IMHO, the dev overreacted. But it’s his project so it’s is decision.

          Some people forked the project before it went down, so maybe we can see a comeback in the future.

  • Akesi Seli@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    6 months ago

    update: we have decided to continue the project starting from the latest active fork and re-create a new community here.