zlacker

>>isodev+(OP)
Thankfully nothing like this is in Jitsi Meet’s TOS: https://jitsi.org/meet-jit-si-terms-of-service/

It never ceases to amaze me how companies choose the worst software!

>>_ddzr+6c
+1 for Jitsi. They are awesome, lightweight, and just work with the least hassle.

Pretty bad that many nontechnical users are not aware of it compared to Google Meet or Teams.

>>arun-m+ed
lightweight? they are literally the only video chatting service I use that makes my laptop fans spin up.

>>Knee_P+dj
I am yet to find a modern video chat that isn't draining the battery of any laptop. From old Xeons, to fairly recent Ryzen and even M1/2 Macs.

It's a bit puzzling, actually. I don't think Skype and TeamSpeak had the same effect on computers back in the day. Just how much local processing are they doing these days? It's crazy

>>beebee+vk
It's most likely due to the fact they are all electron apps rather than they are doing "something".

>>vortic+Vn
Hardware decoding is also an issue.. as in, not being used. Old webcams used to do h.264 encoding in hardware. Encoding has since now moved to the CPU which may or may not be fine.. the next issue becomes the codec chosen.. most stuff all has h.264 decoding in hardware.. but it's not being used anymore.. instead they're trying to use vp09 or h.265 or av1 which in many cases requires CPU-based software encoding and decoding.. so the fans rev up like turbines.

I feel certain the reason this is happening is because some middle-manager terrorist in a boardroom said "use this codec it won't require as much network data usage! value for the shareholder!" without asking first whether hardware encoding is beneficial even if there's a bit more network traffic with the older codecs.

Really burns me up. I do not want to use software encoding/decoding if I have hardware support.

>>Sunspa+vG
Bandwidth is the limiting factor in a lot of circumstances, and networks are very challenging to manage. Especially with an increasing number of users on mobile connections, reducing network usage can be the right call.

But performance matters, too, of course. It's tricky to balance them.