overview for diamond

trans and nonbinary people (and cis if you apply!), how did you pick your name? in c/lgbtq_plus@beehaw.org

[-] diamond@beehaw.org 3 points 1 year ago

My name (Diamond) mostly came from my username. I used to be more active talking on Discord, so a lot of my friends would call me based on my username. It was weird at first, but I got used to it! Some people found it surprising, but the reactions aren't too bad.

UPDATED: There are now multiple iOS / Android apps in development for kbin & lemmy! in c/foss@beehaw.org

[-] diamond@beehaw.org 1 points 1 year ago

Shameless plug (sorry) but I'm working on one too! It's a web app that works on both desktop and mobile: https://slemmy.libdb.so.

It is a free-time kind of project (I work on it after my actual working hours), so it might not grow at the same pace as other newer apps, but I'm trying!

Source code is at https://libdb.so/slemmy, AGPLv3 license.

Missing CORS prevents third-party web clients in c/support@beehaw.org

[-] diamond@beehaw.org 0 points 1 year ago

Huh, interesting. It seems that a WS connection to wss://beehaw.org/api/v3/ws works, but not wss://beehaw.org. I remember reading somewhere that the WS API will eventually be removed, though.

I'll continue development w/ the REST API until I feel like it's in a mostly-working state, and then I'll probably subject myself to the WS API after. Working with the REST API does feel a lot easier.

Missing CORS prevents third-party web clients in c/support@beehaw.org

[-] diamond@beehaw.org 0 points 1 year ago

Websocket handshakes are done over HTTP. The endpoint for Beehaw's WS API would be wss://beehaw.org/, so it's still going to use the same CORS policies as accessing the / (root) path.

0

Missing CORS prevents third-party web clients (beehaw.org)

submitted 1 year ago by diamond@beehaw.org to c/support@beehaw.org

4 comments fedilink

Hey Beehaw mods!

I'm currently working on a Lemmy web client, but the lack of proper CORS headers is preventing anything from working :(

I just wanted to ask if the appropriate CORS headers could be added to the front-facing proxy layer. If you're using Caddy, I believe something like this should do the trick:

reverse_proxy ... {
  header_down Access-Control-Allow-Origin *
  header_down Access-Control-Allow-Methods *
  header_down Access-Control-Allow-Headers *
}

Relevant issue: https://github.com/LemmyNet/lemmy/issues/3109