The rtc-chat from d-side

rtc-chat's Introduction

A simple (almost) serverless WebRTC chat

Uses re-frame (meaning, ClojureScript, React.js and Reagent as well) under the hood.

Uses Bower dependencies via lein-bower and wiredep (I have it globally).

This is a toy and will likely always be a work-in-progress. I'll be really glad if anyone finds the code here even remotely useful, but it hasn't been cleaned up in any way before being published.

Once I found SkyBlue I pretty much stopped using garden
Events are a bit of a mess, I haven't found a way to scope them down yet
Wraps rtc for interaction over WebRTC with a dead-simple wrapper and a couple of event handlers; almost the entire code for that is shoved into initializer and should be extracted into a namespace

Development Mode

Run application:

lein clean
lein figwheel dev

Figwheel will automatically push cljs changes to the browser.

Wait a bit, then browse to http://localhost:3449.

Production Build

lein clean
lein cljsbuild once min

Contributions

I'm not expecting any. You'll really surprise me in a good way if you pay this project this much attention. GitHub issue all the things, I'll take it from there.

rtc-chat's People

Contributors

Stargazers

Watchers

rtc-chat's Issues

RTC: "Google-Closure" it down and package to CLJSJS

All JS dependencies should be handled properly. Of these Bower currently only fetches rtc. I don't mind leaving SkyBlue as-is, with Bower, but properly packaging JS deps should drastically reduce build sizes and therefore download times. Currently builds are about a megabyte each.

Prepare externs for rtc, as primitive as they currently are
Get the project to compile with :optimizations :advanced
Contribute the package to CLJSJS (why not? the hard part would be done by then)

Add nickname support

The simple way

Announce the names of each other when the connection is established
Provide a nickname input field (possibly within a popup)
Broadcast nickname changes
Display names in the participants' list

Pitfall: easy to impersonate

The less convenient way

Display names in the participant list alongside their channel ids
(?) Hash channel ids into colors and use them for displaying names

The bleeding-edge way

Generate a pub-pri key pair using the new Crypto API
Establish a localstorage-persisted address book of publickey-name pairs
- ...and a way to add users there, of course
Show an icon near those whose identity has been proven

Consider removal of Garden

I'm not using it anyway, so there's no point to keep it in the project.

A possibility is style sharing between Reagent views and Garden stylesheets, but I'm not sure it's feasible.

Add support for multiple message content types

There's an idea about adding multiple content types for a message. Namely, sending pictures.

Add message types (see if MIME can be used for that, I don't want to invent another "standard")
Decide on whether pics will be displayed as Blobs or data:-URLs (or both?)
- Blobs sound more practical right now, since they're guaranteed not to be insanely long
Implement picture uploads

Recommend Projects

d-side / rtc-chat Goto Github PK