/queetings

Primary LanguageTypeScript

queetings

[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!

usage

local

requirements:

  • node12

development:

npm run dev will start development server on all available interfaces:

  • https://0.0.0.0:8082

GCP

requirements:

  • node12
  • gcloud

deploy

deploys into flex app engine container

pre-requisites:

  • gcloud toolkit installed

npm run deploy

operate

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

improve!

hell yeah... but how? dig in the shit... erh.... code :) fork, dumb, create!!!

features

MVP is what's planned to initial official release. MVP-next is futurology.

MVP

list of features for the first release

  1. volatile meetings + self-organization (all-with-all)
  2. peer who joins get to know everybody else connected
  3. single-link join to meeting
  4. controls:
  5. mute a person
  6. mute myself
  7. hide myself
  8. disconnect
  9. known issues:
  10. disconnect handling 1. firefox does not generate event

MVP-next

  1. chat-feature!
  2. cross-platform
  3. android webview app
  4. ios webview app
  5. poop-feature!
  6. send poop, display poop
  7. poop reactions: 1. auto-mute a person who floods you with poop 2. ???
  8. video processing
  9. face detection use square tiles focused on face
  10. detect emotions and color tiles accordingly (e.g. green border -- smile, red border -- angry)
  11. attach things (mustache?:)) to face landmarks 1. share attached things with others

development

this section is btw the main one at current state of being. previous were just introduction.

generic algorithm

  1. run npm run dev

  2. after successful compilation it'll say that peer and beacon are updated there will be url: http://localhost:8082/

  3. open browser, look at what's there is, try it, define what you don't like, improve it!

  4. code is in src/peer directory, less likely you would want to change src/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

improvements planned

in order of priority:

  1. increase stability

  2. increase accessibility

  3. simplicity

  4. portability

  5. add features, e.g.:

  6. mute

  7. chat