• Ruud@lemmy.worldOPM
      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

  • Nato Boram@lemmy.world
    1·
    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.

  • U+1F914 🤔@lemmy.world
    1·
    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
    0·
    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.

      • lenninscjay@lemm.ee
        0·
        1 year ago

        Yup, hence why I’m on lemm.ee. Originally made an instance to cover when .world was being slow but I think this will be my main now. They haven’t finalized the vote but it seems to be going the defed route.

        Still hugely supportive of the .world admins though. They’ve done a ton of work to keep .world running and a ton of digging that will help lemmy overall. I just don’t agree with federating with big social media.

  • comcreator@lemmy.world
    01·
    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
      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.

  • DarthBueller@lemmy.world
    01·
    1 year ago

    Where can I learn about transferring my community to another instance? Lemmy.worlds silence about threads means he has no intent to defederate so I need to move over to lemmy.ml.

    Or is this not possible? Do I just need to walk away from my community because @ruud doesn’t care about the issue?

    If that’s the case, how do I add a mod that doesn’t care about meta expressly stating they are going to add features to ActivityPub protocol (step two of EEE)? I don’t want to keep coming back here if it is federated with threads but I don’t need to leave whoever is staying here high and dry.