Lemmy.world updated to 0.18.1
Lemmy.world updated to 0.18.1
We've updated Lemmy.world to Lemmy 0.18.1.
For the release notes, see https://lemmy.world/post/1139237
Lemmy.world updated to 0.18.1
We've updated Lemmy.world to Lemmy 0.18.1.
For the release notes, see https://lemmy.world/post/1139237
"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.
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:
yaml
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:
yaml
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.
At first I thought it was a Lemmy problem, but lemmy.ml doesn't have this problem. @ruud@lemmy.world It's a lemmy.world problem indeed.
I'll check that. It's to do with the CORS settings that changed in recent Lemmy update
The Rodent is bitchin' fast now. Thank you, operators!
Lemmy World! Party Time! Excellent!
Whoops replied to the wrong place
0.18.2 is out, btw
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
Mobile browser is ultra fast and stable, and Jerboa is running like a charm! Appreciate all you and your team's hard work.
Just donated. Thank you for giving us Lemmy.
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.
Definitely notice the improved speed and fewer errors lately. Thanks so much for hosting a great instance, and for keeping up with its needs.
Glad to see the admins keeping the instance up to date
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.
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
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.
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.
It seems that they need a UI expert.
It’s working great, but we would appreciate an update in regards to letting meta in our instance or not
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.
@owatnext @ruud I think he already has: https://mastodon.world/@mwadmin/110654590632768079
Thanks for sharing. Odd that Rudd hasn't posted here, not all of us are on Mastodon.
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.
My favourite thing except the emoji is the new theme
Hahah hadn’t seen that one, looks nice! Reminds me of the good old days..
That is the ugliest thing I have ever seen. What the fuck.
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.
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.
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.
I'm not familiar with this blocking threads controversy. Can you EIL5?
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.
Threads big and scary. Smol bois in the Fediverse have been discussing preemptively defederating from Threads due to how big and scary it is in an attempt to protect themselves and the Fediverse as a whole.
wew nice!!
Awesome, now block threads.net from this instance. Lemmy.ml already did it.
I'm just gonna leave Lemmy.world while I'm ahead. The quietness says all we need to know.
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.
If you move, don't move to Lemmy.ml, move to smaller instances
It really seems like having my own personal instance is the way to go. The only users I’d need to have are mods of any community I create on it. Then I can defederate with tech co instances. damn. I was really starting to like “local” here, but the fact that @ruud@lemmy.world is totally silent about threads is just absolute BS.
Ooh I need to check the size of the custom emoji 😄