[this is very-very-very-draft]
serverless web-conferences with unimaginable client agility
not a lot of details yet, open mind is the source of 'em!
- node12
npm run dev
will start development server on all available interfaces:
https://0.0.0.0:8082
- node12
- gcloud
deploys into flex app engine container
pre-requisites:
gcloud
toolkit installed
npm run deploy
pre-requisites:
-
supported browser
should work on:
- Firefox@Linux
- Chrome@MacOS,
- Chrome@Android
- Safari@IOS
-
a bag of hemp to keep away all frustration
after deployment it'll tell u URL to go
hell yeah... but how? dig in the shit... erh.... code :) fork, dumb, create!!!
MVP is what's planned to initial official release. MVP-next is futurology.
list of features for the first release
- volatile meetings + self-organization (all-with-all)
- peer who joins get to know everybody else connected
- single-link join to meeting
- controls:
- mute a person
- mute myself
- hide myself
- disconnect
- known issues:
- disconnect handling 1. firefox does not generate event
- chat-feature!
- cross-platform
- android webview app
- ios webview app
- poop-feature!
- send poop, display poop
- poop reactions: 1. auto-mute a person who floods you with poop 2. ???
- video processing
- face detection use square tiles focused on face
- detect emotions and color tiles accordingly (e.g. green border -- smile, red border -- angry)
- attach things (mustache?:)) to face landmarks 1. share attached things with others
this section is btw the main one at current state of being. previous were just introduction.
-
run
npm run dev
-
after successful compilation it'll say that peer and beacon are updated there will be url:
http://localhost:8082/
-
open browser, look at what's there is, try it, define what you don't like, improve it!
-
code is in
src/peer
directory, less likely you would want to changesrc/beacon.js
upon any file update corresponding module will be rebuilt-
all files which relate to peer must start with
src/peer
-
all files related to beacon must start with
src/beacon
-
in order of priority:
-
increase stability
-
increase accessibility
-
simplicity
-
portability
-
add features, e.g.:
-
mute
-
chat