The 0.18 version of Lemmy was announced. This will solve many issues.

But we can’t upgrade yet because the captcha was removed, and captcha relied on Websockets, which are removed in 0.18 so despite the devs agreeing on my request to add captcha back, this will not be until 0.18.1. Without captcha we will be overrun by bots.

Hopefully this 0.18.1 will be released soon, because another issue is that the newest version of the Jerboa app won’t work with servers older than 0.18. So if you’re on Lemmy.world, please (temporarily) use another app or the web version.

  • Richie@lemmy.world
    0·
    2 years ago

    Is this why there’s still a ton of slowness on Lemmy despite the slowness said to be resolved? Because I still can’t efficiently use Lemmy, if I’m being honest.

    Also, has the Top Day sorting become broken? A community will show as blank for me now when I sort by Top Day.

    • Xanthrax@lemmy.world
      0·
      2 years ago

      That was an issue with reddit to. If there’s not enough content/ activity it breaks top post sorting for short periods of time.

      I used to follow a lot of niche communities on reddit and that was always an issue. I’d have to put it at a year, month/ day wouldn’t work.

  • LimitedWard@lemmy.world
    0·
    2 years ago

    I know these are early-adopter pain points, but I think if Lemmy is really gonna take off, the devs need to get serious about backward compatibility and ensuring backend upgrades don’t completely break major instances/clients. IMO switching from websocket to HTTP should have been treated as a breaking change with a new major version release and a more controlled rollout period for this exact reason.

    • barsoap@lemm.ee
      0·
      2 years ago

      Quoth semver 2.0.0:

      Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

      “Semver proper” only starts at version 1.0.0:

      Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.

      • impulse@lemmy.world
        0·
        2 years ago

        This is important. Many people (and news outlets for that matter) consider Lemmy a product, when it really is very much an on-going early stage development effort.

        It’s amazing how well everything works already, but nothing should be considered stable at this point.

  • Wayren@lemmy.world
    0·
    2 years ago

    After installing Jerboa from the Play Store I encountered the crashing issue everyone is mentioning. I was able to seemingly fix the issue by going into the App Info -> Storage and hit Clear Storage. After it cleared it’s been working fine for me. Hopefully this works for you folks unless I’m missing something about the issue.

  • Kabe@lemmy.world
    0·
    2 years ago

    The Dev’s stubbornness about captchas is a little baffling. Yes, they’re not 100% foolproof but they help.

    It’s like arguing that we shouldn’t have locks on or our doors because a skilled lock picker can get past them.

      • Kabe@lemmy.world
        0·
        2 years ago

        That only happened recently, though. For weeks they were replying to instance admins requests to reinstate captchas with things like “bots have beaten captchas, so they’re useless.”

          • Kabe@lemmy.world
            0·
            2 years ago

            My mistake, I understood admins had been asking for the return of captchas as soon as they were removed.

            Still, it took a few days for the devs to agree to reinstate them, which, combined with the general tone seem in that second link, is what gave me the impression that they were reluctant to do so.

            • fubo@lemmy.world
              0·
              2 years ago

              In open-source projects and communities, it’s often a bad idea to go around looking for (or inventing) conflicts among contributors. It can come across as drama-seeking or trolling.

              In software engineering in general, a common reason that a desirable feature has not been written yet is that the people who know & work on the code only have so many hands, and so many hours in the day, and there are other things that also need doing.

              This service is undergoing rapid development. Spam & abuse problems are things that folks who have run Internet services before are well aware of. It’s not like anyone is going to give up and let spam bots ruin the thing they’re building.

              I doubt anyone wants to build a service that becomes 95+% spam & abuse, ya know?

    • OsrsNeedsF2P@lemmy.ml
      0·
      2 years ago

      The devs aren’t pushing back against captchas, but they’re desperately trying to get 0.18 out to resolve a ton of issues. Captchas need to be redone in the code level and no one has done it yet.

    • ilovededyoupiggy@sh.itjust.works
      0·
      2 years ago

      My very first post on Lemmy was a (admittedly out-of-date) rant about the devs stubbornness about the hardcoded bad words filter and their behavior in the relevant GitHub issues. And I had people jumping in the comments defending them, telling me that it was fixed years ago, they’re better now, surely that couldn’t possibly happen again.

      I am Jack’s complete lack of surprise.

      ETA: and yeah, I know about kbin, I’ve tried both, kinda waiting to see all the new Android native apps before completely moving over there. Seeing how all this shakes out.

  • solrize@lemmy.world
    0·
    2 years ago

    Frequently getting “404: FetchError: invalid json response body at http://lemmy:8536/api/v3/site” when trying to visit posts here, maybe due to some backend overload. I guess you know about this but mentioning because I didn’t notice other posts about it.