How It Works:
- One user opens a room and receives a unique code.
- Participants join by simply entering the code to view the shared screen.
After that initial build, I moved the project to Cursor to continue iterating and enhancing its features.
One issue: when I stopped sharing, my audience (my another computer) can still see my shared screen (I assume the last frame), what I think it shouldn't. And there is no indication or whatsoever that I have stopped sharing.
While we're on the subject of WebRTC, if anyone would need MIDI over WebRTC, here is my take on it:
The afore mentioned webapp is based on WebRTC so, not totally unrelated.
I have nothing to advertise as I have nothing to gain from this. I just wanted to offer additional solution for people that might find it useful.
Also, judging by the other comments, it seems that someone did find it useful.
Furthermore, reading through other comments on this thread, there are a lot of other WebRTC projects mentions anyway, and many of them have nothing to do with screen sharing.
No custom UI bloat when shadcn will do; no feature creep when the outline is fulfilled.
Simple apps < 30,000 LOC means cursor can keep the code base in the context window, so its generations stay high quality.
Has anyone stumbled upon something similar? I hate having to register and login to every chat platform, especially bloated ones like Discord and Slack. The closest one to what I want is gitter but it requires a GitHub signin.
It’s decentralized, serverless, anonymous, private, ephemeral, and open source.
Jitsi Meet is also a classic example of this, though these days it requires at least one logged-in "moderator" user to work.
click create space -> choose proceed as anonymous -> In your space, use chat or other apps. It's end to end encrypted (using the hash-frag in url as key, AES-128 bit GCM)
Similar to https://pin.gl/
You state it uses PeerJS. And indeed, the code calls from PeerJS,
const peer = new Peer();
I.e., it constructs a PeerJS Peer without manually specifying PeerOptions. That class, in turn, states,
/**
* Configuration hash passed to RTCPeerConnection.
* This hash contains any custom ICE/TURN server configuration.
*
* Defaults to {@apilink util.defaultConfig}
*/
config?: any;
… so it sure looks to me like it is using a TURN server…
> Application error: a client-side exception has occurred (see the browser console for more information).