10 ms·
Yes, I would rather see some more traditional FOSS video/audio/chat/screensharing solution. With an account, contact lists, account (not device) based E2E encry
by chme 10y ago
Yes, I would rather see some more traditional FOSS video/audio/chat/screensharing solution. With an account, contact lists, account (not device) based E2E encryption* , easy to deploy server software and something that can be used from a browser (without any plugins) and native chat applications with an open standard.
* Where messages are de/encrypted readable for every device/endpoint of an account not just for the one with the active session.
- watwatwatwat 10y agoWould you pay for it? If yes build a list of competent developers, ask them if they would build it and lunch a funding campaign. Give all the money to them and donate yourself. Building software is hard, building what you asked for is even harder.
- chme 10y agoI'd rather do it the other way around. Find people with money to spend and let them pay me (and other developers) for implementing it.
- mikekchar 10y agoJust implement it. It's not hard. All the libraries you need already exist and are relatively high quality. I have done it myself (non-free system) getting on to 10 years ago. It took me less than a year by myself and I even wrote my own SIP implementation. These days you could certainly do it faster. There are a few problems, though. One is that NAT traversal will still probably mean that it will be unreliable unless you also set up a service to carry data. The other main problem is that nobody will pay you for it. There are literally hundreds of failed startups who realised how easy it is to build these things. They couldn't find a way to make money. It should be easy because if people are forced to pay for a service to carry data in order to make it reliable, you should be able to make money. Right? The problem is that people won't pay for reliability because they think that the software is buggy (see comments above re: "I tried Hello, but it was buggy. No audio, etc." Classic). Skype famously solved this problem by being evil and routing it's traffic through un-NATed users. Google solves this problem by having more bandwidth than god (and hangouts still sucks half the time). But if you ignore the "there's no way to make money at this" problem, it's a pretty fun project to write.
- aviraldg 10y agoAll of what you asked for: https://vector.im/ https://vector.im/ (E2E has landed recently!)
- chme 10y agoYes, thanks. Somebody mentioned it here before, looks good. Not sure if it can do video conferences with E2E encryption, because that could be very difficult (impossible?) or bandwidth intensive. Now I just need to convince everyone to switch ;)
- chme 10y agoOh, just one thing. Its apparently missing a desktop client, that isn't a web app. I could convince more to switch if chat managers like gajim/pidgin etc. would support it out of the box.