pusher-js VS renraku

Now let's push the notification to pusher. First you have to go to https://pusher.com/ login create an app an get API keys. Then fill them in your .env file

another tool is pusher but have a high cost https://pusher.com/

Pusher specializes in realtime WebSockets and offers a straightforward way to integrate realtime features into your React app. It's a reliable choice for apps that need to send notifications based on realtime events.

why are you considering building your own websocket service instead of using something like https://pusher.com/ ?

IVS offers chat rooms, but Kick doesn't seem to use them. All chat messages are sent over a websocket connection to Pusher. Pusher seems pretty cheap for the purpose.

Serveless Websocket service

Is it possible to use Supabase as a Pusher alternative?

if you are on time, since it is a coursework, and it is allowed to use some libraries, you can check how to use pusher it should be fairly easy for you too integrate to your application.

I've built a flutter web chat using flutter_chat_ui and dart_pusher_channels, for the backend I used soketi which is an open source node.js pusher replacement but you could just use pusher.com if you can squeeze into their free tier.

What? No. Takes 5-10 minutes to set up a websocket server manually or is just requires a few configuration variables to be set if using a hosted service like Pusher.

for example, i'm using simple requests in my experimental typescript json-rpc api library, renraku. you can find the specific code where i issue simple requests here in browser-client.ts

i think of tokens much like any other data that a server might accept to perform a function call. it's just another parameter. that said, my experimental renraku api library abstracts out the mundane auth stuff from function calls, merely as a developer experience ergonomic enhancement.

we're using websockets via our experimental renraku api library, which internally uses ws on the serverside (we found ws preferable to socket.io)

i've also just recently started working on multiplayer web game tech, so i've implemented websocket communication (using ws) in my experimental library renraku, which is the basis of the signalling server in sparrow-rtc, which is a peer-to-peer realtime communications library for our forthcoming project benevolent.games. if you're interested in the open source libraries, you could join our discord and i'd be happy to help you get setup, since they aren't quite yet documented :)

if you coded up a standard node http server directly (probably not) you could allow cors manually by setting the right headers and responding to options requests. i've done that before, here in renraku's allow-cors