41–50 of 199 posts
Earlier quoted context omitted.
All necessary parts are there, which is why e.g. jitsi meet or Google meet work without problem. It's more like they don't care than anything else.
Slack uses Amazon Chime as backend Chime is using h264 firefox still can not encode h264 videos in real time.
Earlier quoted context omitted.
They do but who doesn't? Apple isn't different than any other tech companies. That said, yes, the global south produces for west in slave like conditions and it's sad.
It's a sad reality of society, but it doesn't have to be. I guess one of my biggest issues with modern day slavery is that the companies that exploit these poorer nations often paint a deceptive picture that everything is above board. And whats worse is that these companies have the audacity to get behind social movements. Its predatory and just another scheme to improve their bottom line and lull their customers int…
From what I've heard so far about FaceTime on non-apple devices, I'm extremely unimpressed.
Earlier quoted context omitted.
As far as I've read about Duo it seems to be AV1: https://www.xda-developers.com/google-duo-lyra-codec-better-... ...though I'm not sure whether they use it consistently.
How does this happen? AV1 encoding codec was still work in progress, and most chips don't support any hardware acceleration for this. Can we get reasonable frame rates on core CPU for av1 encoding already?
Earlier quoted context omitted.
At a guess, codecs seem the most likely explanation. Firefox has a h.264 decoder, but not an encoder I think.
Why can't firefox invoke the system dll or libraries for H.264 encode/decode? Like many video players do. Why must every browser ship its own codec or even Unicode collection is beyond me.
Earlier quoted context omitted.
If there are any (as opposed to "just" the added customer support burden), I wonder if they're the same issues that prevent Slack from allowing calls in Firefox...
As a corollary, I wonder if Slack will now implement calling functionality once Mozilla adds the necessary APIs for Apple to do its job here, which is probably very likely since I don't think Apple chose to ignore a non-Google browser on purpose.
Earlier quoted context omitted.
Slack uses Amazon Chime as backend Chime is using h264 firefox still can not encode h264 videos in real time.
Yes, so it's precisely another case of "we tested on chrome and it works", which falls under "don't care" software development best practices.
Other codecs are better, but you have to do more testing and enable those codecs only on calls where all members are using a device that supports it.
However, you are helping push the web become an increasingly centralized place, controlled by just a few entities, with interests which are very different from yours.
You may think that there is no harm in doing so. Most people use Chrome anyway. And what difference can one more web app make?
However, it is exactly this laziness by skilled developers, who are the only that understand the problem, which brought us to the current situation. There is no way to fix this problem, if the people that understand it do not take a stand.
Next time that your manager asks you if you can have that sweet feature, instead of saying "sure, we just need to drop support for Firefox", please consider trying to explain what are the consequences in the long term.
I know this isn't easy for many people, which do not feel comfortable questioning orders or plans. However, this is our responsibility. Nobody else is going to care, if we do not care.
Earlier quoted context omitted.
Slack uses Amazon Chime as backend Chime is using h264 firefox still can not encode h264 videos in real time.
Yes, so it's precisely another case of "we tested on chrome and it works", which falls under "don't care" software development best practices.