“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.

Ooh I need to check the size of the custom emoji 😄

The Rodent is bitchin’ fast now. Thank you, operators!

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

Awesome, now block threads.net from this instance. Lemmy.ml already did it.

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.

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

My favourite thing except the emoji is the new theme

Congrats!

I just donated to celebrate this!

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

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.

Can you please give us a straight answer regarding blocking threads.net? If you don’t intend to do so, there are those of us who want to know so that we can leave.

It’s working great, but we would appreciate an update in regards to letting meta in our instance or not

Nice work @ruud. Things are feeling MUCH better now.

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.