Update The upgrade was done, DB migrations took around 5 minutes. We’ll keep an eye out for (new) issues but for now it seems to be OK.

Original message We will upgrade lemmy.world to 0.18.3 today at 20:00 UTC+2 (Check what this isn in your timezone). Expect the site to be down for a few minutes. ““Edit”” I was warned it could be more than a few minutes. The database update might even take 30 minutes or longer.

Release notes for 0.18.3 can be found here: https://github.com/LemmyNet/lemmy/blob/main/RELEASES.md

(This is unrelated to the downtimes we experienced lately, those are caused by attacks that we’re still looking into mitigating. Sorry for those)

    • astral_avocado@programming.dev
      31·
      1 year ago

      Haters. Groups paid by Steve Huffman. Script kiddies. Any rich trust fund pissant with a couple hundo to spend on the dark web.

        • astral_avocado@programming.dev
          2·
          1 year ago

          Not too much, just that it would be incredibly tempting of an option for a millionaire. Anonymously destroy your competition by paying some dark web site in Monero? Sure why not?

          • sab@lemmy.world
            2·
            1 year ago

            If that were the case, I think he would have paid a bit more and make sure it would have stayed down. No competition was destroyed here.

            I think it’s Far more likely that it’s just a bunch of scriptkiddies saying “when I press button, error page goes brrrrrrr”.

    • Corvid@lemmy.worldEnglish
      1·
      1 year ago

      It’s a bit confusing. The backend added support for infinite scrolling, but lemmy-ui(the front end) hasn’t landed that change yet.

      • Dr. Dabbles@lemmy.worldEnglish
        0·
        1 year ago

        Infinite scroll and word filtering. If I see one more post about “AI”, Musk, Twitter, or fake superconductors, I might have to get off the computer for 10 whole minutes.

            • Contravariant@lemmy.world
              2·
              1 year ago

              Fair. It’s not too hard, but most lemmy UIs make it a bit harder than it needs to be because they want to be a fancy JavaScript-ridden mess of html tags.

              On old.lemmy.world it is supremely easy, you just use the element picker tool of uBlock to select all posts, add the ‘magic’ command :contains(reddit) to filter out the word you don’t want (in this case reddit), and you’ve got your filter. This would result in old.lemmy.world##.post:contains(reddit).

              On lemmy.world it is trickier because it is the kind of HTML no sane person would write. Doing the above you end up with lemmy.world##div.mt-2.post-listing:contains(reddit) which is messy, and misses a line that is used to divide the posts. With some manual tuning you can first simplify the first part to ##.post-listing:contains(reddit) and then add :xpath(.|following::hr[1]) to get rid of the annoying line. This results in ##.post-listing:contains(reddit):xpath(.|following::hr[1]).

              • Blamemeta@lemmy.worldEnglish
                12·
                1 year ago

                Oh is it literally just css selectors, but with a slightly different syntax? Fuck me, I never looked into it and assumed it was nonsense.

                • Contravariant@lemmy.world
                  2·
                  1 year ago

                  The extra syntax is just to add some features that aren’t in CSS. Not quite sure where this came from, I think it’s from the Adblock Plus era, but Gorhill perfected it for uBlock origin, which makes it a very powerful tool.

                  It’s not limited to just hiding the elements either, if you want you can simply restyle them (I’ve used this to redact sports results until I hovered over them).

        • kazerniel@lemmy.worldEnglish
          0·
          1 year ago

          I want to be able to ban/hide entire servers. Regularly seeing lemmynsfw celebrity communities pop up in All/Hot :| (I have nsfw disabled, so it’s just generic photos of random women.)

          Also an option would be nice to hide downvoted posts, I had that on in RES.

  • randint@feddit.nlEnglish
    0·
    1 year ago

    Minor suggestion: write time zones like UTC+2 and not CEST. I’m pretty sure most people outside Europe don’t know what the time zone CEST is. Yes, you provided a link that helpfully converts the time to the users’ local time zone, but sometimes it’s nicer to be able to know something without having to click into a link.

      • randint@feddit.nlEnglish
        0·
        1 year ago

        Wow, you actually changed it! I was kind of shocked when I came back to my feed seeing UTC+2 in the title. Thanks! :D

          • ydieb@lemmy.worldEnglish
            01·
            1 year ago

            Super nitpick. Can we just use 1800 utc? Then everyone can convert to their zone directly. *signed me in a CEST zone.

  • AlmightySnoo 🐢🇮🇱🇺🇦@lemmy.worldEnglish
    0·
    1 year ago

    This version brings major optimizations to the database queries, which significantly reduces CPU usage. There is also a change to the way federation activities are stored, which reduces database size by around 80%.

    Is it me or is the 80% figure just insane? Are there any benchmarks to see how fast this has become versus say Lemmy 0.18.2 on a very large instance?

    • miket@lemmy.worldEnglish
      1·
      1 year ago

      Is it me or is the 80% figure just insane?

      Not really, you’d be surprised how often systems are bloated all because of a single option, character, etc. Most developers don’t start optimizing until much later in the software’s lifecycle. Often enough, it is easily overlooked. That’s why code reviews are needed often with fresh pair of eyes.

      Just to set the expectations, reducing database size or CPU usage does not necessarily mean it is faster but it does mean there’s more free capacity on the servers to handle more users at the same performance.

      More importantly; they may help reduce costs on the smaller indie instances that doesn’t need to buy larger server instances.

      Hopefully, we’ll continue to see more of these optimizations.