• U+1F914 🤔@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    “This release includes major improvements to performance, specifically optimizations of database queries. Special thanks to @phiresky, @ruud, @sunaurus and many others for investigating these.”

    Hehe, lemmy.world doing some stress testing for the entire lemmy project.

  • owatnext@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    3
    ·
    1 year ago

    Thanks for the update! But I noticed an issue: it seems you haven’t commented on defederating from Threads? Please let us know if you are so we can respond accordingly.

  • Nato Boram@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Hi! I noticed an issue with the headers sent by Lemmy.world.

    Headers sent from and to this website’s official UI look like this:

    HTTP/1.1 200 OK
    server: nginx/1.18.0 (Ubuntu)
    date: Fri, 07 Jul 2023 23:35:17 GMT
    content-type: application/json
    vary: accept-encoding, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
    content-encoding: gzip
    access-control-allow-origin: *
    access-control-allow-methods: GET, POST, PUT, OPTIONS
    access-control-allow-headers: DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range
    access-control-expose-headers: content-encoding, content-type, vary, Content-Length,Content-Range
    X-Firefox-Spdy: h2
    

    Which is fine. However, headers received by custom clients look like this:

    HTTP/2 200 OK
    server: nginx/1.18.0 (Ubuntu)
    date: Fri, 07 Jul 2023 23:33:50 GMT
    content-type: application/json
    vary: accept-encoding, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
    content-encoding: gzip
    access-control-allow-origin: https://natoboram.github.io
    access-control-expose-headers: content-encoding, access-control-allow-origin, content-type, vary
    access-control-allow-origin: *
    access-control-allow-methods: GET, POST, PUT, OPTIONS
    access-control-allow-headers: DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range
    access-control-expose-headers: Content-Length,Content-Range
    X-Firefox-Spdy: h2
    

    There’s two access-control-allow-origin! This still breaks web clients.

    • Ruud@lemmy.worldOPM
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Yeah, but we run a special build with the retry-queue disabled, if we don’t we need to restart every 30 mins because of memory leaks. So I’ve requested another built of 0.18.2 without the retry

  • TheForvalaka@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Definitely notice the improved speed and fewer errors lately. Thanks so much for hosting a great instance, and for keeping up with its needs.

  • RCMaehl [Any]@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Hi Ruud, was wondering if you could check if lemmy.world/.well-known/security.txt actually exists on the server. It was added in 0.18.1 but either isn’t being created or isn’t public.

  • vera@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Nice to see speedups. I always thought it was ironic that kbin was faster than Lemmy when kbin is php and lemmy is rust. Makes sense it was database stuff. You can’t solve that with language choice.

  • WhoRoger@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    I find it hilarious how the most random shit always changes with updates. Like I just noticed how the badges for mod and OP changed on posts, and so I knew there’s an update. Who keeps constantly fidgeting with these things?

    Ed: to be clear, I’m not dissing anyone. Keep it up folks

    • Molecular0079@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Yeah I wonder what the reasoning behind that was. Personally I preferred the old way, where it was completedly filled in. Made it easier to notice the tag by color. It also aligned more with the rest of the Lemmy UI and it’s filled-in green buttons.

    • Matt@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Haha, this is how fast-moving open source projects work, things change constantly as they believe it’s better to just get (perceived) improvements out of the door when they’re cooked up, instead of waiting in any capacity.

  • GONADS125@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Mobile browser is ultra fast and stable, and Jerboa is running like a charm! Appreciate all you and your team’s hard work.

  • comcreator@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    Any plans to allow cryptocurrency donations to help fund the costs of the servers? If you post a Bitcoin, Bitcoin Cash and Litecoin address in the sidebar under Donations, I will send some crypto now and them to help with the costs.

    • Ruud@lemmy.worldOPM
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Have been looking into this, haven’t yet found an easy way to accept donations via crypto. It needs to be transparent so people can see what’s donated, without having to dig through the blockchain :-) When I find an option I’ll add it.