Lemmy.world updated to 0.18.1
Lemmy.world updated to 0.18.1
“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.
Congrats!
I just donated to celebrate this!
The Rodent is bitchin’ fast now.
Have any comments on the overall load on the server now and how it might look with any further growth?
How does lemmy compare to say mastodon or calckey in terms of server load for example?
My favourite thing except the emoji is the new theme
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: h2Which 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: h2There’s two access-control-allow-origin! This still breaks web clients.
It has been working great. Smooth like butter.
Thank you!
Threads is the new Facebook-owned twitter come. It uses the activity pub protocol and is therefore part of the fediverse.
People are concerned that Facebook with embrace the fediverse, enhance it with me features (as they will be the largest developers on the platform) and then either deliberately or because no-one can keep up with their development extinguish it.
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.