I made my own app at Slemmy!
Thanks to the CORS PR that I made to upstream Lemmy, all web clients should now be a lot easier to maintain, so I’m resuming work on mine as well!
I made my own app at Slemmy!
Thanks to the CORS PR that I made to upstream Lemmy, all web clients should now be a lot easier to maintain, so I’m resuming work on mine as well!
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.
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.
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.