6 ms·

Setting up a Jitsi server is non-trivial; this is simple (git clone / cd talk / npm install / npm start). And, if you don't want to trust the programme, you ca

by daffy 6y ago

Setting up a Jitsi server is non-trivial; this is simple (git clone / cd talk / npm install / npm start). And, if you don't want to trust the programme, you can do this from a dedicated unpriviledged user.

d0100 6y ago
I thought so as well. Ended up rolling my own and encountering too many sync and error-handling issues. Ended up deciding to spend the week configuring jitsi, but all it took was 1 hour to install and configure the server and I was done
- dvduval 6y ago
  Same here. We use Jitsi inside our app for online learning. It works good.
- daffy 6y ago
  Was this using Ubuntu or whatever it is they recommend or ``manually''?
  - d0100 6y ago
    Ubuntu, just apt install or whatever it was The development of the frontend is a bit messy, but you'll manage
adrianoconnor 6y ago
Getting Jitsi running is actually trivial (depending on your definition of trivial). I went from zero to fully running in about 30 minutes on a fresh Ubuntu server when I wanted to check something one time. It might even be dockerized, but my memory isn't 100% on that.
- daffy 6y ago
  Maybe on Ubuntu. I'm talking about the ``manual'' installation to which everyone not using Ubuntu must resort.
swiley 6y ago
It’s always “just npm install.” IMO that’s no different than curl | sh; it’s easy to copy/paste but not simple.
sombremesa 6y ago
If you don't trust the app, don't run it. You'll be giving it access to video, voice and internet at minimum.
- deleted 6y ago
  [deleted]