• underisk@lemmy.mlEnglish
    52·
    2 年前

    Already noticing some major improvements in both UI and functionality. So nice to see devs that prioritize improving the platform instead of goofing around with dumbass money making schemes.

  • CalcProgrammer1@lemmy.mlEnglish
    30·
    2 年前

    Liking the new functionality so far! The spinner when clicking the upvote button is a huge improvement and lets you know that your upvote was actually received. I have noticed that some posts on my homepage show as expanded by default which is annoying (full size image/video instead of thumbnail) and this wasn’t happening before.

  • UrbenLegend@lemmy.mlEnglish
    20·
    2 年前

    Already seeing a positive difference on lemmy.ml. Better feed content and no more posts being added constantly to the top when you browse All

  • dudeami0@lemmy.dudeami.winEnglish
    19·
    2 年前

    Upgraded my instance, switched the docker images to 0.18.0-rc.6 and it started right up. Appears to have no issues for me thus far, so hopefully a full release will be right around the corner.

    • RoundSparrow@lemmy.mlOPEnglish
      4·
      2 年前

      I’ve been testing for hours, and “Subscribe Pending” went away for the first hour or so after the restart of lemmy.ml - but now I’m getting them again. The underlying issue still seems there.

  • bdonvr@thelemmy.clubEnglish
    9·
    2 年前

    I’m curious why especially lemmy.ml wouldn’t wait for full release - surely after 6 RCs the full release is imminent?

    Or of course, they’re stress testing it. Makes sense enough.

    Wonder if I can finally sub to lemmy.ml communities…

    • monobot@lemmy.mlEnglish
      17·
      2 年前

      I’m curious why especially lemmy.ml wouldn’t wait for full release - surely after 6 RCs the full release is imminent?

      lemmy.ml is official developer instance, makes moste sense to test it out here after dev servers.

    • underisk@lemmy.mlEnglish
      8·
      2 年前

      It’s probably a combination of testing at scale on a server they control and wanting to get these features out so they can be iterated before a bunch of new users show up.

        • RoundSparrow@lemmy.mlOPEnglish
          5·
          2 年前

          I think lemmy.ml has more posts, comments, likes in the database due to historic reasons - and the backend is timing out, PostgreSQL not keeping up to application timeout. I have seen the problem on Beehaw, Lemmy.world when they are busy and throwing nginx 500 errors on their front page.

      • HTTP_404_NotFound@lemmyonline.comEnglish
        21·
        2 年前

        I can confirm that.

        Not long after you upgraded, I upgraded, and was able to successfully subscribe to things here.

        But… not now. /sadface.

  • HTTP_404_NotFound@lemmyonline.comEnglish
    91·
    2 年前

    Also- be aware enabling the new 2FA option… It didn’t work too well for me.

    Knock on wood, I tested it in an incognito window before logging out- and was able to disable it when it didn’t work.

  • edward@lemmy.mlEnglish
    84·
    2 年前

    Can we please not have a default avatar? I specifically want no avatar.

    • SkyNTP@lemmy.mlEnglish
      13·
      2 年前

      Hard disagree, and in fact this was one of my early complaints, and a pretty serious usability issue: because some accounts had an avatar and some didnt, the justification was all over the place, making the scanning of usernames and community names a real chore and tiresome.

      Wether you like the default picture or not, well I guess that’s a matter of personal preference. You could always upload a black box for yourself (or even a transparent PNG?).

      But that aside this is objectively better UX.

      The good news is, there are so many front ends in development, we’ll all quickly find a UX tailored to our needs.

  • purahna@lemmygrad.mlEnglish
    3·
    2 年前

    Can anyone explain why lemmy decided to remove websockets, what they decided to adopt instead of websockets, and to what extent websockets are being removed? I still feel like I don’t understand this move (but I’m sure there’s a good reason)

    • RoundSparrow@lemmy.mlOPEnglish
      3·
      2 年前

      The primary reason I suspect is that it was buggy code. You would be reading a post and the votes and even the title and body of a post would just change in front of you to the wrong post. The server wasn’t keeping the index of clients correct or something. It was a very uncommon way to build a webapp

      • Ananace@lemmy.ananace.devEnglish
        4·
        2 年前

        Websockets really don’t integrate well with the entire rest of the HTTP stack, instead just repurposing the socket as a free-standing two-way communication pipe.

        You can definitely use websockets for requests like regular HTTP, but you have to reimplement things like cookies/session handling, request resumption/retry, duplicated request detection, request timeouts, authentication, etc yourself if you want to use it that way.

        I personally much prefer regular HTTP requests for queries/RPC, and HTTP SSE for notification streams, since those are well developed technologies in the web space - and work much better if there’s a middleware in between.

  • infamousbelgian@lemmy.mlEnglish
    2·
    2 年前

    I’m getting a lot of syntax errors at the bottom of the page since well… recently.

    SyntaxError: JSON Parse error: Unrecognized token ‘<’