[HN Gopher] Pyrite - open-source video conferencing
___________________________________________________________________
Pyrite - open-source video conferencing
Author : jvanveen
Score : 118 points
Date : 2022-02-19 16:18 UTC (6 hours ago)
(HTM) web link (garage44.org)
(TXT) w3m dump (garage44.org)
| rcarmo wrote:
| The most interesting thing for me is actually the galene server,
| but playing around with the demo server and looking at the
| documentation it seems to be a fair bit behind Jitsi in ease of
| use and deployment.
|
| (I built a one-shot template to deploy and run Jitsi on Azure -
| https://github.com/rcarmo/azure-ubuntu-jitsi - and it's been
| trivial to maintain over the past two years, for a small group of
| friends and monthly "open sessions")
|
| I'm not enamored of the Pyrite UI (again, Jitsi seems simpler),
| but I'll keep an eye on both.
| drudoo wrote:
| Not really sure what this offers compared to Jitsi. The author
| says Jitsi is complicated, but my company switched to onprem
| jitsi at the start of covid and it's been a pretty smooth ride
| (5000+ users).
| fock wrote:
| galene is a single GO-binary afaik. Jitsi needs and XMPP-server
| installed.
| jhugo wrote:
| The separate components of Jitsi make it quite clean to scale
| and customise though. A monolith doesn't seem superior except
| for the very smallest deployments where simplicity is key.
| Monotoko wrote:
| I made quite a bit of money as a freelancer at the start of
| covid setting up Jitsi servers for clients - it isn't
| easy... especially when you start to have multiple servers
| etc
| throwaway81523 wrote:
| Wait, this is written in Go? Nothing wrong with that, but why
| is it called Pyrite which evokes that snakey language?
| rgj wrote:
| " I searched where the name Galene came from and learned
| that it is a lead-containing mineral. It would only be
| logical to name this side-project after another mineral.
| Pyrite, or a fool's gold, felt to be a good description."
| detaro wrote:
| > _Pyrite is a web(RTC) client for the Galene
| videoconference server._
|
| So probably a play on the name of the parent project.
| Sean-Der wrote:
| I don't know Jitsi at all, but the things about Galene (and
| Pyrite) I have enjoyed.
|
| * Low resource requirements. You can serve lots of users off a
| Rasp Pi
|
| * Single binary + JSON Config.
|
| * Designed to be modified. Galene is API driven so you can ship
| your own custom UI. I co-ran a conference a while back and
| Galene let us give a custom experience easily. Users had no
| idea what we were using on the backend, and we customized it
| exactly to what we wanted.
|
| * Written in Go/Easy to understand. You can get into the guts
| of Galene's jitter buffer etc.. pretty easily. Great for
| learning and understanding the software you are running.
|
| * Maintainers are really accessible! Galene's developer runs a
| mailing list and you get bounce ideas of him and some other
| really smart people on it.
| craigxyz wrote:
| Are you using Jitsi meet or the lib? I've been trying to work
| with the API to integrate into a solution and it hasn't been
| pretty.
| goldbattle wrote:
| It would really help if the author had a list of "features" on
| the github project. It is a bit difficult to figure out what
| exact functionality the project supports.
|
| * https://github.com/garage44/pyrite/
| greazy wrote:
| Something that is desperately missing from video conferencing
| software is walkie-talkie-like interface and capabilities that
| allow for stop-start convos. This might seem silly but it would
| help tremendously for those in developing countries.
|
| Lots of our collaborators are in developing countries with
| terrible internet, so we end up resorting to video chat + phone
| call.
| arsin wrote:
| throwaway81523 wrote:
| Besides this vs Jitsi, I wonder if there is a tldr about how Zoom
| managed to capture so much of this space.
| crubier wrote:
| I think it's region and connection speed dependent, but for
| several years I noticed that meetings with zoom had wayyyy less
| problems with freezes, bad quality, audio drops and stuff when
| compared to all other tools.
| salmo wrote:
| This has been my experience, even now. I still prefer it to
| Teams and WebEx because of the reliability.
|
| I do like that Teams allows for a richer chat experience, but
| often just keep a Teams chat and Zoom call going when needed.
| james_in_the_uk wrote:
| I've assumed that control over the end point client native
| software allows them to focus on removing pain points. Codecs.
| NAT traversal etc.
|
| Once a critical mass of users, big corporates etc. found their
| solution easier, then they got the network effect.
| detaro wrote:
| It was free and easy to get started with, and worked.
___________________________________________________________________
(page generated 2022-02-19 23:00 UTC)