this post was submitted on 07 Jul 2023
3 points (100.0% liked)

Lemmy.World Announcements

29332 readers
11 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world/

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

Donations 💗

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
 

We've updated Lemmy.world to Lemmy 0.18.1.

For the release notes, see https://lemmy.world/post/1139237

all 9 comments
sorted by: hot top controversial new old
[–] NatoBoram@lemmy.world 1 points 2 years 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.

[–] WiildFiire@lemmy.world 0 points 2 years ago

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

[–] DarthBueller@lemmy.world 0 points 2 years 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.

[–] trouser_mouse@lemmy.world 0 points 2 years ago (1 children)

My favourite thing except the emoji is the new theme

[–] wit@lemmy.world 0 points 2 years ago

That is the ugliest thing I have ever seen. What the fuck.

[–] owatnext@lemmy.world 0 points 2 years ago (1 children)

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.