GiHe
GiHe on Hacker News
Your question sounded like you were concerned about CPU utilization on your own computer as a broadcaster. Solving for multi-party video chat is harder. Have you tried Discord?
Answering your question properly requires more details about your platform (CPU, GPU, resolution, operating system, etc.). If your hardware can offload video encoding from the CPU, that would probably be your best strategy. I would suggest experimenting with OBS Studio to create an CPU-friendly encoded stream from your screen, then exposing that to conferencing software using something like OBS-VirtualCam on Windows or ffmpeg+v4l2loopback on Linux.
The headline says B-->A, but the article says A-->B:
"self-centered men who are argumentative, stubborn, disagreeable and unempathetic are much more likely to own a high-status car such as an Audi, BMW or Mercedes"
... and C-->B:
"conscientious men and women — people who are organized, ambitious, respectable, and often high-performing — are also frequent owners of high-status cars"
Helping friends and family install your self-signed root certificate can be less than fun, especially if they have lesser computer skills and a variety of browsers (and mobile operating systems).
My gut says that StartSSL is about as anti-NSA as they can be, but you never know ...
Prosody (
http://prosody.im/) is very efficient, especially with epoll. StartSSL (
http://www.startssl.com/) issues free server certificates for encryption. Put them on a VM in the cloud for $5-10 per month, and you have your own secure instant messenger system that supports text, voice, and even video (with the right clients).
NetXMS (www.netxms.org) may or may not fit your needs but is an open-source gem that deserves more attention
I do not know how prominent it is, but Pansenti's wearableX project is very worth a look.
I have another interesting (and reproducible) manifestation on Supermicro motherboards with two 82574L controllers. In this case, it is again true that we only experience problems on the first (as ordered by ascending MAC address) of the two interfaces.
That was the case, though I did not clearly state so above, on the Intel motherboard with one 82574L and one 82579LM.
Cross-posted at h-online.com:
I have a plurality of systems with Intel motherboards which demonstrate the same kind of problems. The motherboards in question have two Intel ethernet controllers, one of which is an 82574L.
The systems connect to two different networks. When the systems attach to one of the networks (but not the other) using the 82574L interface (but not the other), that interface dies after some unpredictable amount of time.
I have tried posting comments to the Intel engineer's blog post (and PM-ing the engineer directly), but they do not appear. In fact, there seem to be no comments at Intel's site, despite the post having nearly 6000 views (at my time of writing).
Something is not right here.